Employee Summary Identify Active Records

Dayforce provides most of its entities/tables with a transactional lens. There are some situations where depending on how your organization processes employee status transaction such as pay increase, termination, and other changes, there could be an issue with Dayforce properly updating some types of records in some cases. This is usually based on how your Dayforce is configured to handle things such as approvals, deletes, and same day changes, just as an example.

There can be cases where there may be a two or more records for an employee that show in your target (i.e. warehouse) where the effective_end column is null for both status records for that employee.

Since DLH.io does not set the __dlh_is_active and __dlh_is_deleted columns for entities where the source system does not provide deleted or active flags in its API/database, a transformation is required to do so.

Since the date stamps of the effective_start will come through accurately, that column as well as other columns can be used to identify the latest employee status during a data sync run and allow a transformation update statement using pre-sql to update the correct record.

The following transformation pre-sql will allow you to correctly update the records prior to the data sync loading the employee status table.