Property order inconsistency

[ssougnez]

Hello,

The following situation occurred twice to me:

• I have a document type in production
• In dev, I add a property to this document type and change the order of this property to locate it below an existing one.
• I deployed the new version in production and run uSync
• The property does not get added at the location I set. The first time it occurred to me, the property was not at the end of the list, but neither at the correct location. The second time it occurred, the property was the last available property. Note that I'm using the latest stable version of uSync.

It's also worth nothing that I had a look at the XML file used by uSync (so I guess the serialized version of the structure) and there is a "sortOrder" (I think) field with the correct value. It just seems that this property is not (well) used during the import.

[KevinJump]

Hi,

we might need a little more info to get to the bottom of this, I can't recreate it 😞

The sort order is used when a doctype is reimported and it is updated (and it does move document type properties around in the UI) - it could be an issue with sort orders and inheritance of properties from other locations?

When you have a composition with an item with a sort order of 1, and then a child item also ends up with a sort order of 1, the actual order they appear on the screen can be unpredictable between installations, but the sort order will be stored as best as we can.