Hi Jared,

Apologies for the delayed response, and thank you again for your feature request regarding the Ceridian Dayforce connector.

I’m pleased to share that we now support Employee_Property as an independent table, which includes all required fields. Before we proceed with supporting custom-defined elements, I’d like to confirm whether there are any fields still missing in your destination.

If so, please note that in Ceridian Dayforce, certain fields will not populate via the API unless they are explicitly enabled or selected within your Dayforce environment. We’ve seen this occur in several cases.

Could you please confirm whether the relevant fields have been enabled on your side? If possible, please also share a list of the missing fields so I can verify whether they should be available via the API once properly configured.

Additionally, to better understand your use case and ensure we’re aligned on next steps, I’d appreciate the opportunity to connect. Please feel free to schedule a time using my calendar here: Google Calendar

Thanks,
Sisan