An OData PATCH to update an Employee/Person's first or last name returns a successful 200 response, but the change never actually shows up in the employee record — even after a screen refresh. The same integration's employee-creation calls work fine. What's going on?

All FAQ questions / Integrations and APIs

Answer

A 200 response doesn't guarantee the specific fields you sent were actually the ones the target projection persists — some Person/Employee attributes need to go through a more specific, dedicated service (for example, one purpose-built for person data like a PersEntity-style service) rather than a more general employee-handling projection, which can silently accept the call without applying every field. If an update seems to succeed but doesn't stick, trying the equivalent call against the entity's more specific/dedicated projection is worth testing before assuming it's a permissions or caching issue.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Integrations and APIs questions