After Enhanced Employee Gender is enabled, customers can keep using V1 reports with legacy gender and gender identity information. Through backward compatibility, these reports continue to work with Enhanced Employee Gender. Some configuration notes and limitations are described below.
What Are V1 Reports?
V1 reports are older reports that were built by Dayforce employees for customers. These reports can’t be edited by customers, and customers have to contact Dayforce to update them. These reports are written in Microsoft SQL rather than built in an editor, which means that an editor must be familiar with SQL and the Dayforce database structure.
What Is Backward Compatibility?
With backward compatibility, customers can keep using existing gender and gender identity elements with the new Enhanced Employee Gender functionality.
For V1 reports, backward compatibility means that customers can continue using Dayforce without changes to their experience. This means that the legacy gender and gender identity database fields used in V1 reports still allow data from the new table structure to be retrieved by reports. Customers won’t see any change if they use a V1 report, unless they engage with Enhanced Employee Gender.
Backward Compatibility Limitations
Backward compatibility has some limitations. With certain configurations, backward compatibility doesn’t work and V1 reports return no data. If this happens, either the V1 report needs to be updated by Dayforce, or a new V2 version of the report needs to be built to replace it.
The limitations are described below, with examples of the data shown in reports in each situation.
Display Enhanced Employee Gender Last Modification Information and Effective Dating client property is enabled
When the Display Enhanced Employee Gender Last Modification Information and Effective Dating client property is enabled, effective dated gender records can be assigned to employees. The legacy gender and gender identity tokens can’t accept this data, so if the client property enabled, the reports won’t retrieve any data.
See Enabling the Display Enhanced Gender Last Modification and Effective Dating Client Property.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity | Effective From | Effective To |
|---|---|---|---|---|---|---|
| 0001 | United Kingdom | Male | Male | 01/01/1990 | 01/01/2022 | |
| 0001 | United Kingdom | Female | Female | 01/01/2022 |
| Employee Number | Gender [Legacy Field Name] | Gender Identity |
|---|---|---|
| 0001 |
An employee has multiple gender records
With Enhanced Employee Gender, employees can have a gender record for each location they live in, work from, or want to be reported in. However, the fields can accept only one record, so if an employee has multiple gender records, the report won’t retrieve any data.
See Confidential Information Updates.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0002 | United Kingdom | Male | Male | |
| 0002 | Germany | Male |
| Employee Number | Gender [Legacy Field Name] | Gender Identity |
|---|---|---|
| 0002 |
An employee in the United States or Canada has state or province gender records
With Enhanced Employee Gender, an employee in the United States or Canada must have a state or province value assigned to their gender records. They also have a country gender record. V1 reports can show only one value, so if the employee has multiple records, the report won’t provide any data.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0003 | United States | Male | ||
| 0003 | United States | Florida | Male | Male |
| Employee Number | Gender [Legacy Field Name] | Gender Identity |
|---|---|---|
| 0003 |
Backward Compatibility and Supported Features
Unlike other backward-compatible features, V1 reports can use some Enhanced Employee Gender features.
Modifications are made to the Gender module for a Country, State, or Province
After the migration, you can change any of the following settings in HR Admin > Employee Gender Admin > Gender and V1 reports will continue to return data:
- Clear the Collect Assigned Sex Information checkbox
- Clear the Make Assigned Sex Mandatory checkbox
- Clear the Gender Identity checkbox
- Add a country, state, or province with custom assigned sex values (not system M or F)
- Add a country, state, or province with custom gender identity values (not system M or F)
See Enhanced Employee Gender Administration Screen and the Compliance Framework.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0004 | Australia | Non-Binary | Non-Binary |
| Employee Number | Gender [Legacy Field Name] | Gender Identity |
|---|---|---|
| 0004 | Non-Binary | Non-Binary |
Legacy Exports and Enhanced Employee Gender
Customers who want to keep using V1 reports with all of the features of Enhanced Employee Gender need to do one of the following:
- Convert the V1 report into a V2 report. This might not be possible if the report is particularly complex and relies heavily on SQL functions.
- Update the V1 report to use Enhanced Employee Gender tables and columns. This is an untested solution, and might not function as expected.
- Convert the report into an API-based export. Many V1 reports are used as exports, rather than reports. This would likely be the best method for V1 reports that are being used as exports.