Human Resources

Dayforce Release Notes version 2025.1.0

Version
R2025.1.0
ft:lastEdition
2025-04-02

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 with some system forms, such as Contact Details and Address, where the employee’s status and employee number wouldn’t be shown in the form’s header as expected.

Fixed an issue with the Direct Deposit form where you were unable to open a completed form when it contained incorrect Dayforce Wallet information.

Fixed an issue that could occur in Work > Job Step Rates in People. In some cases, when you manually added a job step rate, an incorrect rate was shown in the Rate column for that entry.

Fixed an issue that could occur when you used the application in Polskie (Poland). In some cases, when you saved a value that used Polish-specific characters in the County field of the Address dialog box in any screen, the application replaced the special characters with regular letters. For example, Łęczycki was incorrectly replaced with Leczycki.

Fixed an issue that could occur when you imported a work assignment that had the same effective date and location as an existing work assignment but a different job. In some cases, if the job assignment didn’t exist already, the application set the work location to the site level instead of rejecting the update and showing an error message in the HR Import debug log as expected.

Fixed an issue that could cause the application to try to process HR Import files a second time. As a result, you could receive an error notification that the import was unsuccessful, even though it was processed successfully the first time.

Fixed an issue that could occur with employee data mapping when you had a rule configured that mapped the User Org Visibility and Management value and a separate rule configured that mapped the User Org Visibility value. In some cases, if both rules used the same qualifier, the mapping values were overridden based on the order in which the rules were applied.

Now, if you want to map both values at the same time, the rule with the User Org Visibility value must be placed above the rule with the User Org Visibility and Management value. For more information about the importance of rule ordering, see Rule Ordering Overview in the Dayforce Implementation Guide.

Fixed an issue that could occur in People, in the Work > Management Assignments screen. In some cases, the Managed Employees section didn’t show a checkmark in the Terminated column for terminated employees, incorrectly making it seem like the employee was still active in Dayforce.

Fixed an issue with the RESTful API where the PATCH Work Assignments call failed when you tried to promote an active secondary work assignment with the OriginalIsPrimary tag.

Fixed an issue where, in some cases, forms didn’t include accurate pay zone information for employees.

Fixed an issue in the Employment > Letters screen of People where the download icon wasn’t shown on the screen.

Fixed an issue with the Direct Deposit form where the submitter could remove an attachment from the Supporting Documents section when the form was awaiting approval. In this case, the link to the attachment wasn’t removed from the form, and an error message was shown if any user attempted to open the attachment. Now, the Remove button isn’t visible when the form is pending approval.

Fixed an issue that could occur when you tried to rehire employees using the HR Recruiting Import. In some cases, the import failed with an error and didn’t rehire the employees as expected.

Fixed an issue with the HR Import where deleting direct deposit records for terminated employees caused the import to fail with an error about missing SSN numbers. Now, you can delete direct deposit records for terminated employees using HR Import, as expected.

Fixed an issue where importing employee badges using System Admin > HR Import failed even though importing the file using SFTP was successful.

Fixed an issue that could occur in People when you used the application in Deutsch (Deutschland). In some cases, error messages in the Work > Management Assignments screen weren’t translated to German.

Fixed an issue with the New Hire form when you selected anything but English in the Numeric Culture drop-down list in the User Properties section of the Security Settings screen in People. Previously, you couldn’t submit the form if you entered a decimal value in the Base Rate field. Now, both decimal and comma values are accepted (for example, 7.25 or 7,25).

Improved query performance to fix an issue where the Workflow Processor background job prevented other background processes and queries from running.