HR Import 2.0 and Backward Compatibility

After Enhanced Employee Gender is enabled, customers can continue to import gender data to the legacy gender and gender identity fields using the HR Import. Through backward compatibility, the import continues to work with Enhanced Employee Gender. Some configuration notes and limitations are described below.

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 the HR Import, backward compatibility means that customers can continue using it without changes to their experience. The legacy gender and gender identity tokens are still in the Employee entity on the HR Import, and they import the records into the new Enhanced Employee Gender record for the employee.

Backward Compatibility Limitations

Backward compatibility has some limitations. With certain configurations, backward compatibility doesn’t work and you receive validation errors during the import. If this happens, you must update your Dayforce configuration to use Enhanced Employee Gender. The limitations are described below.

Display Enhanced Employee Gender Last Modification Information and Effective Dating client property is enabled

If 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 effective dated records, so Enhanced Employee Gender isn’t backward compatible with this client property enabled.

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

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 tokens can’t accept 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.

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 tokens can accept only one record, so multiple gender records aren’t backward compatible. If employees have multiple gender records, validation fails during the import.

See Confidential Information Updates.

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. In this case, validation doesn’t fail, but backward compatibility can update only the country gender record. State or province records are ignored, and only the country record is updated.

The following tables illustrate how an employee’s gender record is updated with backward compatibility.

And the following backward-compatible record is imported for the employee:

• Gender: Female

See Federal Event.

Example Data

To use backward compatibility HR Import 2.0 with backward compatibility, customers can keep using the legacy gender or gender identity entities they already use.

<?xml version="1.0" encoding="UTF-8"?>
<EmployeeImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Employee>
    <XRefCode>123456</XRefCode>
    <EmployeeNumber>123456</EmployeeNumber>
    <FirstName>Employee</FirstName>
    <LastName>Employee</LastName>
    <Gender>M</Gender>
    <GenderIdentityXrefCode>MALE</GenderIdentityXrefCode>
  </Employee>  

Other Resources

• For more information about using Enhanced Employee Gender with HR Import 2.0, see Updated in HR Import 2.0.
• For customers who want to use all of the functionality of Enhanced Employee Gender with HR Import 2.0, see Migrate HR Import 2.0.