After Enhanced Employee Gender is enabled, customers can keep using legacy exports. Through backward compatibility, these exports continue to work with Enhanced Employee Gender. Some configuration notes and limitations are described below.
What Are Legacy Exports?
Legacy exports are exports that are built in Dayforce using XML and XSLT languages. These exports allow customers to take information from Dayforce and export it to other systems. For example, a legacy export of HR data can take data from Dayforce and import it back into another system.
What Is Backward Compatibility?
Backward compatibility is a mechanism that allows Dayforce customers to keep using legacy gender and gender identity elements that have existed for several years. Legacy exports are no longer maintained or enhanced but to ensure that they continue to work for customers with older implementations of Dayforce, basic updates have been maintained to help ensure that they can be used as is.
This means that legacy exports will still allow data to be correctly processed using legacy XML export tags. As such, customers won’t see any changes, unless they engage with Enhanced Employee Gender.
Backward Compatibility Limitations
There are limitations on what functionality can be offered via backward compatibility. If any of the following features designed for Enhanced Employee Gender are in use, backward compatibility won’t function and legacy exports won’t show information for a particular employee.
The Display Enhanced Employee Gender Last Modification Information and Effective Dating Client Property is Enabled
The Display Enhanced Employee Gender Last Modification Information and Effective Dating client property allows for effective-dated gender records, which the legacy gender XML export tags can’t accept. Therefore, if this client property is enabled and effective-dated records exist, no information is included in the export.
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 |
Export output example
<EmployeeNumber>0001</EmployeeNumber>
<Title>Mr</Title>
<FirstName>Tom</FirstName>
<LastName>Jones</LastName>
<SIN>123456789</SIN>
<Gender>""</Gender>Modifications are made to the Gender module for a country, state, or province
After the migration, if customers change any of the following configuration for a country, state, or province, they’ll receive validation errors:
- A country, state, or province is added, and Collect Assigned Sex Information isn’t enabled.
- Note: A NULL value is exported for the employee.
- A country, state, or province is added, and Make Assigned Sex Mandatory isn’t enabled.
- Note: A NULL value is exported for the employee.
- A country, state, or province is added, and Enable Gender Identity isn’t enabled.
- Note: A NULL value is exported for the employee.
- A country, state, or province is added, and custom (i.e., not M or F) assigned sex values are added.
See Enhanced Employee Gender Administration Screen and the Compliance Framework.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0002 | Australia | Non-Binary | Male |
Export output example
<EmployeeNumber>0002</EmployeeNumber>
<Title>Mx</Title>
<FirstName>Viviane</FirstName>
<LastName>Williams</LastName>
<SIN>987654321</SIN>
<Gender>""</Gender>An Employee Has Multiple Gender Records
Enhanced Employee Gender allows employees to provide several gender records (not to be confused with assigned sex or gender identity values within the gender record) for every location they live in, work from, or want to be reported in.
If an employee has several gender records, no information is included in the legacy export because the field can only accept one value.
For more information, see “Gender Information for a Full Time or Part Time Employee - Employees outside of the United States and Canada - Multiple Countries” in Types of Confidential Information in Detail.
| Employee Number | Country | State/Province | Assigned Sex | Gender Identity |
|---|---|---|---|---|
| 0003 | United Kingdom | Male | Male | |
| 0003 | Germany | Male |
Export output example
<EmployeeNumber>0003</EmployeeNumber>
<Title>Mr</Title>
<FirstName>David</FirstName>
<LastName>James</LastName>
<SIN>987654321</SIN>
<Gender>""</Gender>Backward Compatibility and Supported Features
An employee in the United States or Canada has state or province records
Enhanced Employee Gender mandates that employees in the United States or Canada have a state or province value in their gender record. In addition, they also need to have a federal country record.
For legacy exports, Dayforce can ensure that the federal country record for the United States or Canada can be exported, however, the state and province records won’t be exported.
| Employee Number | Country | State | Assigned Sex | Gender Identity | “isFederal” Flag |
|---|---|---|---|---|---|
| 0004 | United States | NULL (blank) | Female | NULL (blank) | 1 OR 0 |
| 0004 | United States | Florida | Female | Female | NULL (Blank, not applicable) |
Export Output Example
<EmployeeNumber>0004</EmployeeNumber>
<Title>Mrs</Title>
<FirstName>Charlotte</FirstName>
<LastName>Everdean</LastName>
<SIN>7418520963</SIN>
<Gender>F</Gender>Legacy Exports and Enhanced Employee Gender
Because they’re no longer maintained or updated, legacy exports won’t see any further changes that would allow them to fully support Enhanced Employee Gender.
Customers using legacy exports must move to a modern API-based export to fully engage with Enhanced Employee Gender.