I have found a bug or at least to me some unexpected behaviour of the use of DisableVersionSync="true" when using the Catalog Import. We are using commerce.13.16.x, but since the latest commerce tag in the forum is commerce.13.15.x I have tagged the post with this.
If DisableVersionSync is enabled in appsettings the related entries in the [ecfVersionProperty] are not updated when using the Catalog Import. Only the [CatalogContentProperty] table is updated.
The consequence of this is that the ContentLoader/ContentRepository, if no specific version is requested, returns the latest data. The Catalog UI however shows the latest data from the [ecfVersionProperty] table and hence it does not show the latest data to the editor.
What is even more unfortunate is that it has the "unintended" consequence that if an update is made on a single property through the Catalog UI, the property values in the [CatalogContentProperty] table are updated with all of the latest values from the [ecfVersionProperty] thereby overriding the latest data for all properties.
Steps to reproduce1. Set DisableVersionSync="true"2. Import a catalog.xml with variation entries.3. Do a property update in the Catalog UI on a variation.4. Import the catalog.xml again.5. See that in the Commerce Manager the value of the updated property has been updated to the value in the catalog.xml.6. See that in the Catalog UI the value of the updated property has not been updated.7. Update another property on the variantion in the Catalog UI.8. See that in the Commerce Manager the value of the originally updated property has been updated to the value which is was updated to through the Catalog UI in step 3.