WFM data does not update after Sync.HRPersonnel BOD processing

A subset of WFM data is not updated when processing Sync.HRPersonnel BODs.

Causes

  • The BOD might be changing different fields than the ones the user expects. Sync.HRPersonnel only updates fields that are considered “changed,” and not every field in the employee record.

  • On WFM, a field is considered changed only when its XML validFrom date matches the XML effective date.

    The WFM XPath configuration for validFrom can be incorrect or can target an XML element that has no validFrom attribute (for example, <Field>abc</Field>), or it can target the wrong element entirely.

  • The HR Talent (HRT) XML template might be misconfigured, such as omitting the validFrom date or setting an incorrect value.

Solution

  • Make sure the specific field to be updated is actually changed in HR Talent. For the Sync verb, only fields with changes are updated. To force a change, specify a new value in the HRT UI and save it.
  • Verify which fields are truly changed by comparing the XML validFrom date with the effective date in the BOD payload.
  • Review and correct the WFM validFrom XPath configuration so that it points to the correct XML element with a proper validFrom attribute, ensuring WFM recognizes the field as updated.
  • If the BOD XML itself is generated incorrectly (for example, an incorrect date in validFrom), review and fix the HRT XML templates.
  • To synchronize all current values for an employee without changing each field individually, send a Show.HRPersonnel BOD.
  • For detailed XPath configuration patterns and examples, see the HRPersonnel XPath guide in the Infor HR Talent Integrations Library (Cloud and On-premises) and select Infor-to-Infor Integrations > HR Talent to WFM integration.

Notes

  • The three most frequent root causes are: (1) not understanding that only changed fields are updated for Sync verb, (2) incorrect WFM XPath configuration, and (3) incorrect HRT templates.
  • You are responsible for your own custom XPath configuration — always inspect the XML and verify that validFrom and effective dates match.
  • When an employee is synced for the first time, all fields are updated even if no values changed (the "first sync" scenario).