Status: Closed (View Workflow)
Resolution: Not a bug
Affects Version/s: Cloud 38, 5.0
Fix Version/s: None
Component/s: Synchronisation (Enterprise to Cloud)
Sprint:Platform Team Sprint 11 (Dev)
Cloud or Enterprise:Cloud and Enterprise
When syncing content between cloud and enterprise (and vice-versa) the only properties tracked are cm:name and cm:locale. All other properties and aspects in the propertiesToTrack and aspectsToTrack lists are ignored during create on the target because the node is not part of a syncSetDefinition.
This is caused by
The isNodeRefPartOfSync(nodeRef) will always return false when called during create because the node is not added to the SSD until after the properties and aspects are pulled from the remote node.
Out of the box example: Exif
If an image is added to a synced folder in cloud the exif metadata is extracted on cloud, but even though the exif aspect and its properties are set to be tracked none of the properties are actually copied from cloud to enterprise. When the node arrives at the enterprise server the metadata extractor kicks off extracting the metadata. (Some may argue that this is a good thing as it reduces the sync set size and I would agree ... in this case.)
If you add a model to the list to be tracked and add content to a tracked folder that uses that model the metadata will not be synced. Interesting to this is that the new cloud custom content model feature is not affected by this. If I add a custom content model to enterprise and cloud and then add content (via salesforce) the property from the custom content model is synced, but the properties from the tracked models are not synced.
Expected result: All properties and aspects listed in the propertiesToTrack and aspectsToTrack would be synced during create.
Aspects and properties can be add from an Amp to the lists using a format like the following:
Namespaces should be added at the root beans element
A bean is used to list the aspects and properties with a merge attribute set to true