Human Resources

Dayforce Release Notes version 2025.1.1

Version
R2025.1.1

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 in Org Setup > Jobs and Job Assignments where, in some cases, the Employment Indicator drop-down list showed only the Seasonal option.

Fixed an issue where the HR Import file took longer than expected to load.

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

Fixed an issue with the HR Import where the job log showed duplicate errors for the same employee.

Fixed an issue in the Employment > Employment Settings screen of People. Employment status records weren’t updated with an Active status change when the Request Leave of Absence form and the Return to Work form were submitted on the same day.

Fixed an issue with HR Import 2.0 where, in some cases, the import failed when you included work assignments.

Fixed an issue that could occur when you ran a mass edit in People. In some cases, the mass edit completed successfully but an error message was sent to Message Center that incorrectly stated that the background job failed.

Fixed an issue where employees' seniority dates were incorrect when they were updated by data mapping rules.

Fixed an issue in some forms that used legacy gender information where the forms caused workflows to fail.

Fixed an issue that could occur in Profile, in Personal > About Me. In some cases, the Gender section showed “null” when the employee didn’t have access to one or both of the following:

  • The Enhanced Employee Gender feature
  • The Employee Profile - Confidential Information - Gender access authorization

Now, the application behaves as follows when employees don’t have these things:

  • If the employee has gender information saved in Dayforce, the Gender section shows the employee’s gender data.
  • If the employee doesn’t have gender information saved in Dayforce, the Gender section shows, “No gender information available.”

Fixed an issue that could occur in HR Import 2.0. In some cases, the job log showed an error message that indicated that the effective from date of an employee’s Tax Identification Number was updated when, in fact, the number wasn't changed.

Fixed an issue with the RESTful API where the POST Employees call failed because gender identity XRef Codes were case sensitive. Now, gender identity XRef Codes are no longer case sensitive, as expected.

Fixed an issue with the Job Assignment and Compensation Change form where the Last modified section of the employment status record in the Employment > Employment Settings screen of People wasn’t updated correctly when the form was processed.

Fixed an issue where the Employee Pay Zone Recalc Background Job didn’t recognize postal codes that were formatted correctly.

Fixed an issue in Reporting and Analytics > Reporting where, in some cases, you couldn’t run custom reports that used the Employee Audit entity.

Fixed an issue with the New Hire form where you couldn’t submit the form if you entered 0.00 as a value in the Base Rate field. Now, you can enter 0.00 as expected.

Fixed an issue that could occur in the Work > Job Step Rates screen in People. In some cases, the date shown in the Effective From field didn't follow the correct date format of the user's language culture.