An attribute mapped from Workday to Okta is not being updated, or the value shown is null.

• Workday
• Provisioning
• Mappings

If a newly added attribute (or any attribute) is not being populated in Okta from Workday, must ensure that the attribute we are trying to bring in is populated in both the JSON and XML custom reports (those reports will also have to be defined in the WD integration tab in Okta).

For older Workday instances utilizing existing Custom Reports add the attribute in the JSON and XML custom reports, as specified in the Creating a custom report in the Workday section of the Workday Provisioning article.

For newer Workday instances where field overrides are used in the Workday integration instead of custom reports, ensure the custom attribute in question is added to the Workday field override configuration. Field overrides have now replaced Custom Reports, and field overrides must be used for all new Workday integrations.

Lastly, please ensure that the service account used for the Workday Okta integration has enough permissions to view the custom attribute. If the Workday service account does not have appropriate permissions to view the values of this custom attribute, it may be imported as null from Workday into Okta.