Custom Integration Field Override Service Fails: Entered Information Does Not Meet Restrictions
What it means
When you add a Custom Integration Field Override Service to a PECI configuration so a field only sent on change (like Job Profile or Company) shows up on every extract, Workday validates the field and value pair you enter against the restrictions defined for that integration attribute. If the value or field reference doesn't match what the attribute expects, Workday rejects the row with a generic restriction error instead of naming the specific mismatch.
Troubleshooting
- Open the Custom Integration Field Override Service row that failed and confirm which Integration Attribute field is selected.
- Check whether the Field Override references the same object type the attribute expects, for example a Position reference where a Text value is expected, or vice versa.
- Re-enter the override using the exact reference type and business object the underlying Integration Attribute definition requires, not just a value that looks correct on the surface.
- If the restriction still fires with a seemingly valid value, check whether the field has a picklist or validation domain configured elsewhere in the Integration System that narrows what's accepted.
Remove the offending Custom Integration Field Override Service row, save the integration, and confirm it launches successfully before re-adding the override with a corrected reference type.
Document the exact object type and reference format each Integration Attribute expects before configuring field overrides, and test new overrides on a single worker in Sandbox before adding them to a production PECI or PICOF configuration.