Okta Users Fail to Import From Workday Due to First Day of Work Settings

Workday users fail to import into Okta when administrators set the First Day Of Work attribute in the future, leave it blank, or format it incorrectly. Administrators must verify the First Day Of Work date and format on the Workday hiring event to ensure Okta imports the users successfully. When this issue occurs, the user profile is not visible in the Okta Import tab.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Workday
• Lifecycle Management
• Imports

Administrators set the First Day Of Work attribute in Workday in the future, leave it blank, or format it incorrectly for the user location. In the US, the format of the date is MM/DD/YYYY. But in some countries, the format of the date is DD/MM/YYYY.

How is the Workday user import issue resolved?

Verify the First Day Of Work attribute on the Workday hiring event to ensure the date has started and uses the correct format for the user location.

• Check whether the user's First Day Of Work has started. If the date is in the future or blank, Okta does not import the user.
• Verify that the date entered for the First Day Of Work matches the correct format for the user location. For example, if a user has a hire date of 1/1/2023 and a first day of work of 1/7/2023, but the configuration uses the DD/MM/YYYY format instead of MM/DD/YYYY, the date reflects as July 1st instead of January 7th. This formatting mismatch prevents Okta from importing the user as active.

NOTE: The First Day Of Work field is not visible in the Workday user profile. Administrators must view the hiring event to see this field.