In the current scenario, when importing Dynamic Roles, the existing records are flushed out and replaced with the records that are being loaded while using the incremental load operation. This means that Incremental operation behaves as a Full Purge while importing Dynamic Roles.
Environment: EMPLOYEE CENTRAL: Import
Reproducing the Issue
In this scenario, the import acts like a Full Purge import and not as an Incremental import.
Dynamic Role is not an Effective Dated Entity currently. This is the reason for the unexpected behavior (as most Foundation Objects are Effective Dated).
The expectation for Dynamic Role imports is that the system would add records to the list of existing records when importing using Incremental mode
The expectation here is that the system should not replace the existing records when incremental load operation is performed.
Engineering are currently planning a solution, which will be added to the Product Roadmap for Employee Central, and Product Management will evaluate this for the 1605 release (this is not yet confirmed, please continue to monitor release information for any changes to this behaviour).
The solution being developed can be tracked by #ECT-34353 till resolution.
Until then, when wanting to import Dynamic Role updates, you must ensure you export the Dynamic Role that you wish to update, by using the Foundation Objects ad hoc report, and then copy all rows related to the Dynamic Role you wish to update to a Dynamic Role import template. Then make the corrections to the Dynamic Role as needed and re-import the Dynamic Role.
As noted here - the import will always behave as Full Purge for that Dynamic Role - so please ensure you follow the short process as outlined above when updating Dynamic Roles via import.
Incremental Import, Dynamic Role, Full Purge, Import , KBA , LOD-SF-EC , Employee Central , Problem
|Incremental load behaves as full purge in dynamic role FO.docx|