An Okta to NetSuite provisioning failure occurs when the NetSuite System for Cross-domain Identity Management (SCIM) server rejects an invalid field value during a user provisioning job.

The following error appears during the provisioning attempt:

Push user's profile to external application FAILURE: You have entered an Invalid Field Value <invalidFieldValue> for the following field: <fieldName>

• Okta Identity Engine (OIE)
• Okta Classic Engine
• NetSuite
• Okta Integration Network (OIN)
• Provisioning

The NetSuite SCIM server rejects the invalid field value during the SCIM user provisioning job. The value fails the NetSuite input field validation steps during the SCIM Application Programming Interface (API) request.

How is the invalid field value error resolved?

Verify the Okta to NetSuite mapping configuration, correct the invalid attribute field value, and retry the failed task.

1. Navigate to the Okta Admin Console and verify the Okta to NetSuite mapping configuration.
2. Ensure the mapping passes a valid application attribute field value from the referenced Okta user profile field to the NetSuite target application user field.
3. Navigate to Dashboard and select Tasks.
4. Retry the failed task for the NetSuite application.

NOTE: If the referenced Okta user field does not contain a valid value, check the Okta profile source to ensure it syncs the correct application attribute value into the Okta user profile.

Related References

• How to Map an Attribute From Okta to an Application
• Attribute-Level Sourcing
• Okta Expression Language
• How to Retry Failed Tasks for a Specific Application