Skip to main content
Developer Communities Admin
Community Manager
September 15, 2026

Identify Deleted Employee Skills

  • September 15, 2026
  • 4 replies
  • 2 views

Originally posted by Craig Shields on October 7, 2025 at 9:05 PM.

 

Identify Deleted Employee Skills

 

Scenario:

Dayforce Employee data is being integrated to another system using Get Employee to identify changes and Get Employee Details to synchronize the changes.

 

Problem:

This synchronization works when records are updated for example if an Employee skill is updated then the Get Employee Details (Expander: Skills) response will have a LastModifiedTimestamp for Skills.

 

If an Employee Skill is deleted in Dayforce however, as it was entered in error, Get Employees does not identify any records.

 

Please advised when records are deleted in Dayforce e.g. Employee Skill how the API can be used to identify that a change (e.g. Deletion) has occurred.

 

Regards

Craig Shields

    4 replies

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Frank Ruffolo on Oct 9, 2025, 8:06 AM.

     

    Hi Craig, I'll get back to you.

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Frank Ruffolo on Oct 15, 2025, 8:57 AM.

     

    Craig, haven't forgotten about you. Still reaching out!

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Craig Shields on Oct 23, 2025, 12:15 AM.

     

    Thanks Frank for the information

     

    Developer Communities Admin
    Community Manager
    September 15, 2026

    Originally replied by Frank Ruffolo on Oct 15, 2025, 12:39 PM.

     

    Hey Craig, here is what I learnt:

     

    If a record is deleted, it is no longer present in the database. If you make a GET Employee Details call AFTER deleting the record, then the record cannot be returned in the API response payload. The RESTful APIs cannot retrieve deleted records or otherwise provide an indication that a record has been deleted (other than the fact that the record is no longer represented in the payload). Unfortunately, the omission of the record from the payload is not necessarily indicative of a deletion, as the record may have been filtered out of the payload by other filter criteria as well.

     

    With that said, our teams are currently working on an improved version of our Event Framework that would solve this challenge. In future-state, you would be able to configure an Event Subscription in Integration Studio to consume events whenever a data change occurs to a supported entity record type. This would include record adds, edits, and deletions. Implementation of the enhanced Events functionality in progress, with a targeted roll out of the functionality in 1H 2026.