Important: Before updating a customer’s production environment, ensure that any changes are tested in a non-production or test environment.
This page provides information for customers who want to move their existing V2 reports from using legacy Gender and Gender Identity columns, filters, and custom columns to those that are specifically for Enhanced Employee Gender.
What Are V2 Reports?
V2 reports are built in Dayforce using reporting entities or topics in a WYSIWYG editor. They’re different from V1 reports, which are built in SQL and have different capabilities.
New Reporting Entities and System V2 Updates for Enhanced Employee Gender
For Enhanced Employee Gender, Dayforce has created new reporting entities and columns, and has updated existing system reports to use information from Enhanced Employee Gender data sources. For more information about the new reporting entities and system reports, see Reports and Enhanced Employee Gender.
Why Migrate to Enhanced Reporting Columns?
Customers are encouraged, but not forced, to move to the Enhanced Employee Gender reporting columns. These new columns offer more features, and are designed specifically for gender information going forward. The legacy columns can’t be used with many of the new features for Enhanced Employee Gender, including:
- Backward compatible columns lack functionality: The backward compatible legacy Gender and Gender Identity columns can operate only in backward compatibility mode. They continue to work as long as employees don’t update their records to enhanced ones, or administrators don’t configure the system to use features that are part of Enhanced Employee Gender.
- Engaging with Enhanced Employee Gender required report updates: If employees or administrators are using Enhanced Employee Gender features, they must update their reports to help ensure compatibility.
- Future features for Enhanced Employee Gender: New features will apply only to the new enhanced reporting columns. Dayforce will continue to maintain the existing legacy columns for a period of time, but future (and currently not planned) changes to Enhanced Employee Gender could cause the legacy columns to stop working.
Which Columns Have Been Updated and How?
The reporting columns for gender have been overhauled to allow for more information to be provided to reports and to include an additional column for assigned sex.
Information about the employee’s country, state, and province are now included with the employee’s assigned sex or gender identity information. This change is because gender now has a geographical context and therefore must be provided to customers.
| Legacy Gender/Gender Identity Entity and Column | Enhanced Employee Gender Entity and Column |
|---|---|
| Employee - Employee Gender | Employee Assigned Sex - Name |
| N/A | Employee Assigned Sex - Compliance Code |
| N/A | Employee Assigned Sex - Reference Code |
| Employee - Gender Identity Id | Employee Gender Identity - Name |
| N/A | Employee Gender Identity - Reference Code |
For information about how to update your existing custom reports to use these new enhanced employee gender entities and columns, see the Ad Hoc Reporting Guide.
Make Enhanced Columns Work like Legacy Columns
Many customers have exports that use a report as a base, and the report data is exported to an external system. With this in mind, the information presented in the Enhanced Employee Gender reporting columns might not match business or downstream requirements.
Below is an example custom column using the Employee Assigned Sex reporting entity with the following configuration:
- Country/state/province context has been removed.
- System assigned sex values are male and female and are presented as Male and Female.
- Custom non-binary (i.e., neither male nor female) assigned sex values are represented as Non-Binary.
- If not provided, then assigned sex values are represented as Undefined.
Configuration
- Display Name: Gender (Named this way for downstream purposes. Information is using assigned sex information in Dayforce)
- Data Type: String
- Access Authorization: Employee Profile - Confidential Information - Gender or Employee Personal Information
- Expression:
- CASE WHEN EmployeeAssignedSex.ReferenceCode LIKE '%[^MF] (%' THEN 'Non-Binary' WHEN EmployeeAssignedSex.ReferenceCode LIKE '%F (%' THEN 'Female' WHEN EmployeeAssignedSex.ReferenceCode LIKE '%M (%' OR EmployeeAssignedSex.ReferenceCode LIKE '%M (%' THEN 'Male' ELSE 'Undefined' END
Note: This is an example, and shouldn’t be used for all situations. This example doesn’t include information from gender identity, which might differ from assigned sex for the employee.