V2 Reports and Backward Compatibility

Enhanced Employee Gender Playbook
Version
R2025.1.0
V2 Reports and Backward Compatibility

After Enhanced Employee Gender is enabled, customers can keep using V2 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 V2 Reports?

V2 reports are built in Dayforce using reporting entities or topics in a WYSIWYG editor. Not to be confused with V1 reports, V2 reports are built in SQL outside of Dayforce and have different limitations and features.

See Reports and Enhanced Employee Gender.

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 V2 reports, backward compatibility means that customers can continue using Dayforce without changes to their experience. The legacy gender and gender identity fields are still in the Employee entity in V2 reports but they return data from the new table structure in reports.

The following topics and entities were updated to support backward compatibility:

  • Employee Entity: Employee Gender and Employee Gender Identity ID fields
  • Gender Identity Entity: Name and Reference Code fields.

Backward Compatibility Limitations

Backward compatibility has some limitations. With certain configurations, backward compatibility doesn’t work and V2 reports return no data for the legacy gender and gender identity fields. If this happens, you have to use the Enhanced Employee Gender report topics to retrieve gender information.

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 fields can’t show this data.

See Enabling the Display Enhanced Gender Last Modification and Effective Dating Client Property.

Employee Data Example

Employee data example
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 States   Female Female 01/01/2022  
Report output example
Employee Number Gender [Legacy Field Name] Gender Identity
0001    

The Gender module is configured for a country, state, or province

After the migration, if you change any of the following settings for a country, state, or province in HR Admin > Employee Gender Admin > Gender, backward compatibility doesn’t work and you’ll receive validation errors because the legacy fields can’t display this data:

  • The Collect Assigned Sex Information checkbox is cleared.
  • The Make Assigned Sex Mandatory checkbox is cleared.
  • The Gender Identity checkbox is cleared.
  • You add custom-assigned sex values (not system M or F) for a country, state, or province.
  • See Enhanced Employee Gender Administration Screen and the Compliance Framework.
    • Employee data example
    Employee Number Country State/Province Assigned Sex Gender Identity
    0002 Australia   Non-Binary Male
    Report output example
    Employee Number Gender [Legacy Field Name] Gender Identity
    0002    

    One or more employees have 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 topic can’t show any data.

    Note: If more than one employee has multiple gender records, backwards compatibility no longer functions and report topics can't show any data.

    See Confidential Information Updates.

    Employee data example
    Employee Number Country State/Province Assigned Sex Gender Identity
    0003 United Kingdom   Male Male
    0003 Germany   Male  
    Report output example
    Employee Number Gender [Legacy Field Name] Gender Identity
    0003 (Employee with enhanced record)    
    0005 (Employee with legacy record)    
    0006 (Employee with legacy record)    
    0007 (Employee with legacy record)    

    One or more employees in the United States or Canada have 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. If the employee has state or province records, none of their information is included in the report.

    Note: If more than one employee has a state or province record, backwards compatibility no longer functions and report topics can't show any data.

    See Federal Event.

    Employee data example
    Employee Country State Assigned Sex Gender Identity “isFederal” Flag
    0004 United States NULL (blank) Male NULL (blank) 1 OR 0
    0004 United States Florida Male Female NULL (Blank, not applicable)
    Report output example
    Employee Number Gender [Legacy Field Name] Gender Identity
    0004 (Employee with state or province records)    
    0008 (Employee without state or province records)    
    0009 (Employee without state or province records)    
    0010 (Employee without state or province records)    

    System V2 Reports and Enhanced Employee Gender

    System V2 reports are packaged with Dayforce and maintained by Dayforce. System V2 reports have been updated to use the new Enhanced Employee Gender reporting entities.

    See Reports and Enhanced Employee Gender.