Error "This choice creates a conflict" for Users on the Okta Application Import Tab

When running user imports from an application into Okta, the Imports tab displays a conflict error for users who do not yet exist in Okta.

This choice creates a conflict.

This occurs because an existing record already claims the incoming user's unique identifier, or the custom Okta expression used for the Okta username format contains an error. Resolve this issue by clearing attribute collisions in the Okta directory and correcting the Okta Expression Language (OEL) expression.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Expression Language (OEL)
• Provisioning

This error occurs because an existing record, frequently a deactivated account, already claims the incoming user's unique identifier (username or email). Alternatively, the custom Okta expression used for the Okta username format under Provisioning > To Okta contains an error. For example, the expression contains malformed syntax or references an application user profile that does not yet exist, such as okta_org2org.userName. Because Okta cannot properly evaluate this expression, the Imports tab displays the error for a large number of users.

How is the application import conflict error resolved?

Resolve the conflict error by searching the Okta directory to clear attribute collisions and reviewing the Okta Expression Language (OEL) expression for the Okta username format.

1. Navigate to Directory > People in the Okta Admin Console and search for the specific username or email to ensure an existing record does not already claim the incoming user's unique identifier.
   NOTE: Ensure the filter includes users with a Deactivated status.
2. Delete the conflicting account or edit the profile to change the email or username if Okta finds a match. This frees up the attribute for the new import.
3. Review the OEL expression used for the Okta username format for any errors. If the expression contains direct references to the application variable name (such as okta_org2org.userName), change the expression to refer directly to the application user profile, such as appuser.userName. Direct references to the application variable name fail because the application user profile does not yet exist.
4. Preview the modified OEL expression with an existing user to ensure Okta evaluates it properly without errors.
   NOTE: Test any new or modified OEL expressions in an Okta Preview or non-production environment to avoid potential issues.