Skip to main content
Question

PersonnelFileHandling: PATCH CompanyPersonSet returns 200 OK but does not update the employee’

  • Oct 28, 2026 8:29 AM UTC
  • 0 replies
  • 5 views

Forum|alt.badge.img+2

Hello,

I am trying to update an employee’s information using the IFS REST/OData API. The PATCH request returns HTTP 200 OK, but the response still contains the previous name, and the Employee File screen does not reflect the requested change.

I am testing directly in Postman before implementing the update in Boomi.

PATCH https://<ifs-host>/int/ifsapplications/projection/v1/PersonnelFileHandling.svc/CompanyPersonSet(CompanyId='<company>',EmpNo='<emp_no>')


IFS product/version: 
 


 

Steps performed:

  1. Retrieve the entity using GET. through
     https://<ifs-host>/int/ifsapplications/projection/v1/EmployeesHandling.svc/CompanyPersons
     
  2. Extract its @odata.etag.
     
  3. Send a PATCH to the same entity, using that value in the If-Match header.


    Headers:

    Content-Type: application/json
    If-Match: W/"<etag-from-get>"
     

    The API documentation lists FirstName in the update request schema and marks Operator, TimeClockUser, and DirectSub as required.

    Request body:

    {

      "Operator": "<operator-value>",

      "TimeClockUser": "false",

      "DirectSub": false,

      "FirstName": "UpdatedName"

    }

    Actual result:

    The response returns 200 OK, but includes:

     

    {
     

    "Operator": "<operator-value>",

      "TimeClockUser": "false",

      "DirectSub": false,

      "FirstName": "OriginalName"

    }
     

  4. The Employee File screen also continues to display the original data .

    Expected result:

    The data should be updated, or the API should return an error explaining why the modification cannot be applied.

    Questions:

    - Should changes be performed through a different projection or entity.

    -Is an additional action required to persist this change?


    Thank you for your help.