Symptom
Following an instance sync, entities that were not included in the sync were still updated, with the “last-modified-on” and “last-modified-by” identical to the values that were intentionally included in the instance sync.
Environment
SAP SuccessFactors HXM Suite
Cause
Default behavior for MDF Data, MDF Object Definitions, and MDF Rules.
Resolution
For MDF Data, MDF Object Definitions, and MDF Rules, when a sync is triggered, the configurations are also exported from the source instance along with the dependencies.
After which, the import into the target instance takes place, whereby all the dependencies and references with full purge type are imported, meaning when a sync is triggered the concerned configuration along with dependencies and references are fully overwritten in the target.
As the MDF data that was updated unintentionally is either dependent or referenced data, this data is also updated as part of the sync.
A warning pop-up will be generated by the system in relation to dependencies. This pop-up is triggered to ask the user to select all dependencies related to the selected artifact/MDF configuration. This is to avoid unnecessary failures. However, if the user does not select the dependencies of the chosen artifact/MDF configuration, then the system will automatically selected the dependencies and references in the background to avoid failure.
Whether "Continue As-is” is chosen or "Select All Dependencies", the system will automatically choose the dependent and referenced MDF object/data while syncing. This is done to avoid failure. This warning pop up appears to ask the user to choose if they failed to select the dependent and referenced objects/data. If the user did not choose or was not aware of the dependencies then the system automatically locates and selected during the sync.
See Also
Keywords
Instance sync, synchronization, entity, entities, MDF, MDF data, MDF objects, MDF objects definitions, dependencies, references. , KBA , LOD-SF-PLT-IST , Instance Sync Tool , Problem