Okta Attribute Value Fails to Synchronize From Workday

When administrators map an attribute from Workday to Okta, the attribute does not update or displays a null value. This occurs when the attribute is missing from the JSON and XML custom reports or field overrides, or when the service account lacks the required permissions. Administrators must add the attribute to the custom reports or field overrides and verify the service account permissions to resolve the synchronization issue.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Workday
• Provisioning
• Mappings

The attribute is missing from the JSON and XML custom reports or field overrides, or the Workday service account lacks the required permissions to view the custom attribute.

How is the Workday attribute synchronization issue resolved?

Administrators must verify the Workday configuration and service account permissions to ensure Okta synchronizes the attribute correctly.

• For older Workday instances utilizing existing custom reports, add the attribute in the JSON and XML custom reports. Review the Creating a custom report in the Workday documentation for specific instructions.
• For newer Workday instances utilizing field overrides instead of custom reports, add the custom attribute to the Workday field override configuration. Field overrides replace custom reports, and administrators must use them for all new Workday integrations. Review the field overrides documentation for more details.
• Verify that the service account used for the Workday Okta integration possesses sufficient permissions to view the custom attribute. If the Workday service account lacks the appropriate permissions to view the values of the custom attribute, Okta imports the value as null from Workday.