28
The delete option is disabled on the employment history form.
All the time users accidently create employees in the wrong legal entity.
It is easy to create their employment in the correct legal entity afterwards, but it is impossible to remove the employment record from the wrong legal entity.
The workaround is to end the employment after only i.e. 1 minute in the wrong legal entity - but it would be much nicer if the records could be deleted.
NB! This should be enabled in Talent core HR as well as in the HR module of D365FO, please. ALL customers I've worked with, are requesting this.
Category: General
STATUS DETAILS
Under Review
Ideas Administrator

Thank you for your suggestion. We’re considering this functionality for a future release. This posting is provided “as is” with no warranties, and confers no rights.

Comments

M

I see that a new delete button has been added to the employment, which is great. But, it is useless if the corresponding CDS record is not also deleted and then repopulates the employment on the Worker record. I have had this issue with deleting workers as well. Deletes to CDS need to occur for entities that are synced to CDS. Should be a basic part of the release of the functionality.

Category: General

M

My organization also has had this challenge and we feel that it would be a great option even if it was only available for System Administrators to be able to perform.

Category: General

M

Learning point: the employment records can be deleted via CDS!
But... I still opt that there should be a delete button in the employment history form, as this will be a much safer way to delete than finding the relevant record in the long list of employment records in Excel, risking deleting an employment record of another worker.
@Microsoft Product Group: please make sure, that the pressing this new delete button in the employment history form also deletes the corresponding record in CDS!
I've just learned, together with Microsoft Support, that when employment records are deleted from Core HR (by Microsoft support), they re-appear shortly after, because they did not get deleted from CDS. Incident #119052323001002

Category: General