Human Resources

Dayforce Release Notes version 2025.1.1, Patch 2

Version
R2025.1.1 Patch 2
Release Date
06/24/2025
ft:lastEdition
2025-10-28

Note: The items in this section are generic, and don't apply to a specific country. Items that are specific to a particular region, if available, are listed in their respective sections.

IDDescription

Fixed an issue that could occur when you ran the HR Export background job in System Admin > Background Jobs. In some cases, the HR export failed to return data for the emp_genderidentity_xref token.

Fixed an issue where the HR Import completed successfully but the job log showed errors.

Fixed an issue with the Direct Deposit form where International Bank Account Number (IBAN) entries from the following countries were reported as invalid when you submitted the form:

  • Albania
  • Andorra
  • Azerbaijan
  • Bosnia and Herzegovina
  • Croatia
  • Czechia
  • Georgia
  • Gibraltar
  • Greenland
  • Iceland
  • Kazakhstan
  • Liechtenstein
  • Moldova
  • Monaco
  • Montenegro
  • San Marino
  • Serbia
  • Switzerland
  • Vatican City State

Fixed an issue where HR Import 2.0 failed with an error when the following was true:

  • The HR Import Auto Generates Config Data client property was enabled.
  • The import file contained more than 100 employees.
  • The import file contained new configuration data (such as a new department or pay class).
  • The same type of configuration data was provided in the first batch of 100 employees and the second batch of employees, but with with different values.

Now, HR Import 2.0 completes successfully when these conditions are true, as expected.

Fixed an issue with the Direct Deposit form where you couldn’t approve or edit the form for employees in the Pre-Start status from the Message Center.

Fixed an issue that could occur in Hub where the My Team widget generated an error and stopped working when the Hub landing screen loaded. Also, when you clicked View Hierarchy the widget didn’t load the data.

Fixed an issue with the Job Assignment Change form where the form could falsely detect an assignment overlap and prevent submission. The issue occurred if you end-dated a primary work assignment and started the same assignment as a secondary assignment that had a start date after the end date of the primary assignment.

Fixed an issue in Profile, in Personal > About Me where, in some cases, if you updated your primary address, your gender value could be changed.

Fixed an issue that could occur with HR Import 2.0 when the Allow a client to transition a Secondary WorkAssignment to a Primary WorkAssignment client property was enabled. In some cases, the import failed with an error about duplicate work assignments even though duplicate work assignments were permitted and no work assignments were being imported.

Fixed an issue with Data Mapping 2.0 where past-dated active records weren’t updated by data mapping rules when the Apply Data Mapping Historically checkbox was cleared. Now, past-dated active records are updated when the Apply Data Mapping Historically checkbox is cleared, as expected.