3779946 - odata upsert returns success but custom picklist field not updated on job application - SAP successfactors recruiting

Updating a custom picklist field on JobApplication via OData API returns a success response, but the field value remains unchanged in the UI.

 SAP SuccessFactors Recruiting

1. Perform an OData upsert on the JobApplication entity to set a custom picklist field using a picklist option ID.
2. Receive a success response from the API.
3. Open the application in the UI and observe that the field still shows the previous value.

An onSave business rule associated to the field with the JobApplication overwrote the value provided by the OData API, reverting or overriding the intended update.

1. Review business rules configured for the JobApplication, focusing on onSave rules that reference the affected custom picklist field.
2. Identify any rule logic that sets or overwrites the field value during save.
3. Adjust the rule logic to respect external (API) updates, or disable the conflicting rule if it is not required.
4. Re-run the OData upsert to update the field with the intended picklist option ID.
5. Verify in the UI that the field reflects the updated value and that history records align with the change.

• Refer to: KBA 2883239 - How to update the Application Status via Integration Center/OData API - Recruiting Management

odata, upsert, jobapplication, picklist, custom field, value not updating, success response, no change in ui, business rule, onsave, recruiting management, integration, api overwrite, field overwritten, rcm api , KBA , LOD-SF-RCM-API , Webservices & APIs , Problem