Does anyone have any idea why the versions for this form are not in order? There seems to be no logic in how they are sorted. I don't think we've seen this on any other forms. We're using TM 5.1.10.
Sorry, I don't know where that screenshot disappeared to.
The first Maestro version is 9.0. 4.0 and 5.0 are definitely Composer.
We are renaming the default Maestro version numbers because we want to stick to the versioning format we already have in TM.
We have published other Maestro versions to forms with lots of Composer versions and have not seen this issue with those.
I believe it's an issue in TM when you have form versions from Maestro and Composer. In my case, product team renamed the versions in the way showed in the picture attached. Please, have a look. All versions but the last one are from Composer, last one Maestro. Old version 1 was renamed to 0.01... till old version 19 renamed to 0.19 and 20 to 0.2
Thanks Julio. I can try renaming them, but I still don't get why they don't show in order when logically they should if you look at the version numbers, which are consistent.
It's especially strange that 4.0 and 5.0, both Composer versions, appear above some of the Maestro versions, and 9.1 and 9.2, both Maestro versions are not grouped together.
Did this happen after TM update? Has TM been updated or always 5.1.10?
It seems like form version has changed its internal type (Ie from long to string) or something like that, then form versions table can't manage the order... Only guessing... I'm sure hosting team can give us a clue why this is happening...
Yes, it was upgraded from 4.3 a few months ago.
Interesting comment about the internal type. It's not a big issue. Just confusing.
And I would love to find out what the difference is between this form and other forms that aren't affected.
There was a defect found in the product in the logic how version "numbers" are compared between each other. This is being fixed in the latest 17.10.x and 18.4 TM versions. I'll forward this link to the product team so they can review the latest fix and make sure it resolves Lin's problem as well.
We may not upgrade to that TM version for a while, but it's good to know there is a fix planned.
Could you please add a screenshot?
Are the different form versions coming form Maestro or Composer?
Are you using the new versioning notation?