I’m working on an Integration Studio inbound file for Employee Demographics, specifically for Work Assignment updates.

Originally replied by Lexi Woodward on Jul 6, 2026, 10:38 AM.

My apologies for the delay! I was out of the office for a couple weeks.

There is a POST Job Assignment endpoint, though it only accepts a single position at a time (DDN - POST Job Assignments <link stripped through migration>). You can configure an integration through Integration Studio with batches of 1 with this API as an endpoint to add new positions to Dayforce. Please review the information regarding the end point on the DDN and documentation for the "Send as API Request" transmission options in the Integration Studio Help Guide.

Originally replied by Kanak Johari on Aug 12, 2026, 2:40 PM.

Hi @Brenda Sutton​,  I am reaching out to you for a clarification. I am currently working on outbound files through Integration Studio.

I need to configure an outbound file for the Pay Calendar and Leave Balances. I created a custom report that is fetching dates such as Period Start Date and Period End Date in the format yyyy-MM-dd.

However, when I use this report in the outbound integration, the date fields are also configured as Date/Time with the format yyyy-MM-dd. After running the integration, the destination CSV file is changing the date format to dd-MM-yyyy, irrespective of the format configured in Integration Studio.

Report Date format -

Integration Studio configuration -

Destination File Format -

I have tried different date formats in the Integration Studio mapping, including formats such as yyyyMMddTHHmmss and other formats starting with yyyy as well as custom formats but the destination file continues to return the dates in a ddMMyyyy/dd-MM-yyyy type of format only.

I also tried creating a formatting expression in the custom report. The report output displays the dates correctly in the required format, but once the data is passed through the outbound integration, the date format is being converted again.

This seems to be happening with outbound integrations whenever I use a date field.

Could you please confirm whether this is the standard behavior in Integration Studio, or if I am missing any configuration that would allow the date to remain in the specified yyyy-MM-dd format in the final CSV file?

Your guidance would be greatly appreciated.

Originally replied by Brenda Sutton on Aug 12, 2026, 5:00 PM.

@Kanak Johari​ , have you confirmed the output? Meaning, the raw CSV file outside of Excel (for example, Notepad or VS Code). Integration Studio supports destination date formatting, including yyyy-MM-dd, so a Date/Time destination field configured with that format should serialize accordingly. Excel can automatically interpret CSV values as dates and display them using your regional settings. I'd check that first before changing anything. Let me know!

Originally replied by Kanak Johari on Aug 13, 2026, 1:58 AM.

Hi @Brenda Sutton​ , If I open the destination file using Notepad, the date is displayed in the correct yyyy-mm-dd format. However, when I open the same file in CSV/Excel, the date is being interpreted as dd-mm-yyyy.

Destination file in Notepad -

I have created 9 outbound files for the payroll exports using the same Custom Report and the same configuration. However, when opened in CSV/Excel, all of them are interpreting the date as dd-mm-yyyy, instead of the required yyyy-mm-dd format.

I also checked the Excel settings, and the automatic conversion of data setting is disabled.

I have checked the configuration and everything looks correct, but I’m not sure what else I could be missing. Could you please help me identify what might be causing this?

Thanks!

Originally replied by Brenda Sutton on Aug 13, 2026, 7:28 AM.

@Kanak Johari Thanks for confirming. Since the raw CSV shows the dates correctly in yyyy-MM-dd format, Integration Studio is producing the expected output. What you're seeing when opening the CSV in Excel is Excel interpreting the values as dates and displaying them according to its date/locale formatting. This does not change the actual values contained in the CSV file itself.

I personally wouldn't recommend making any changes to the Integration Studio configuration before confirming with the receiving platform because this feels like a simple display issue once the file is opened. Adding in @Lexi Woodward to see if she has another thought. Maybe we can even use this as a discussion topic on todays webinar! 😂 Hope you'll be there! @Pranaw Sharma​ 

Originally replied by Kanak Johari on Aug 13, 2026, 11:00 AM.

Hi @Brenda Sutton​ , thanks for the clarification. Since I attended the webinar, I was able to get some additional clarity on the topic.

Just one question — would it be possible to have a demo of the “Event Driven HR Changes” connector? I tried building it myself but kept running into errors.

If possible, it would be really helpful to see a demo of how to configure and use this connector. Thanks!

Originally replied by Brenda Sutton on Aug 17, 2026, 2:01 PM.

Hi @Kanak Johari​ I submitted your request to the team as part of my recap of the session...totally forget to respond. I saw your request come thru in my email notification.😁

Originally replied by Kanak Johari on Sept 24, 2026, 8:15 AM.

Hi @Brenda Sutton , Hope you are doing great. I am configuring an Build my own (Inbound File) integration using Dayforce Pay Entry Import and am looking for suggestions on how to handle the deduction code dynamically based on an employee’s Pay Group.

The vendor is not providing the employee’s Pay Group or Deduction Code, as they do not store or maintain this information in their system. Both the Pay Group and Deduction Code are specific to our Dayforce payroll configuration.

Since Pay Group is not available in the inbound file, I am using: AutoDetectPayDataPayGroup = true to allow Dayforce to determine the appropriate Pay Group for the employee during the Pay Entry Import.

The challenge is with PRDeductionXrefCode. We have different deduction codes depending on the employee’s Pay Group:

Pay Group 100 -> Deduction Xref Code 5090

Pay Group 200 -> Deduction Xref Code 5091

Since the vendor does not maintain Pay Group or Dayforce Deduction Code information, they are unable to provide either value in the inbound file.

My understanding is that AutoDetectPayDataPayGroup is a Boolean (true/false). Although Dayforce uses this setting to determine the employee’s Pay Group during the import, I am not sure whether the Pay Group identified by the auto-detection process can then be referenced within the IDL mapping to derive

PRDeductionXrefCode.

Looking for suggestions on the following:

1. Is there a way to reference the Pay Group identified through AutoDetectPayDataPayGroup within the same Pay Entry Import/IDL mapping?
2. Is there any other recommended Dayforce configuration or integration approach that would allow PRDeductionXrefCode to be determined based on the employee’s Pay Group?

Our preference is to manage this logic within Dayforce, since the vendor does not store the employee’s Pay Group or Dayforce Deduction Code and therefore cannot provide these values in the inbound file.

Any suggestions or alternative approaches would be greatly appreciated. Thanks !

Originally replied by Kanak Johari on Sept 30, 2026, 8:08 AM.

Hi @Brenda Sutton , Hope you are doing great. Following up on the question above. Any suggestions or alternative approaches you could recommend would be greatly appreciated. Thanks!

Originally replied by Brenda Sutton on Sept 30, 2026, 8:30 AM.

@Kanak Johari  SORRY! Thought I had tagged @Lexi Woodward  and @Shruti Srinivason  on this one. I think it's fairly complex and may also be a great one to show quickly on our upcoming Webinar!