Dayforce OOTB SaaS connector aggregate "Did Not Start" Employees

[nickteeuwen]

Hi everyone,

We’re currently working on implementing a Dayforce OOTB SaaS connector and have run into an issue we can’t seem to resolve.

Specifically, we’re unable to read employees with the “Did Not Start” employee status. We’ve tried multiple variations in spelling and formatting in the account aggregation filter, but none of them seem to return any results.

Has anyone else encountered this issue before? Is this a known limitation or behavior with the connector? If so, is there a recommended way to successfully retrieve these employees?

Any insights or guidance would be greatly appreciated!

Thanks in advance.

[BBR1 (Bharani Reddy)]

@nickteeuwen

We’re currently working on implementing a Dayforce OOTB SaaS connector and have run into an issue we can’t seem to resolve.

Specifically, we’re unable to read employees with the “Did Not Start” employee status. We’ve tried multiple variations in spelling and formatting in the account aggregation filter, but none of them seem to return any results.

Has anyone else encountered this issue before? Is this a known limitation or behavior with the connector? If so, is there a recommended way to successfully retrieve these employees?

Account Attributes

This looks like a connector limitation rather than a SailPoint limitation. Because these Employee records are not returned by the Dayforce API used by the OOTB connector.

Workaround:

Pull the employee records with “Did Not Start” status into a CSV file and import these Employees with a flat file into ISC.