Edit Job Requisition EIB Fails Restriction Check on a Field the Load Never Touches
What it means
An Edit Job Requisition EIB fails validation against a field it isn't even changing, and only on requisitions where that field already has a value. The EIB's initiating ISU is missing an unconstrained security grant on the business process policy step securing that field, so Workday blocks the whole transaction the moment the field is populated, even though the load's payload never references it.
Troubleshooting
- Confirm the pattern: does the error only happen on requisitions that already have a value in the field named in the error, and never on requisitions where it is empty? That is the signature of this issue rather than a mapping problem in the load itself.
- Check whether the field named in the error is secured to the same domain as a field the EIB is actually changing, Workday validates everything visible on the transaction step, not just the fields present in the load's payload.
- Open the initiating ISU's security group and check its grant on the relevant business process policy (for example Job Requisition Change) for the domain securing that field, specifically whether it is constrained or unconstrained.
- Add an unconstrained grant for the ISU's security group on that policy step and re-run the same failing record to confirm the fix.
Add the EIB's initiating ISU's security group as an unconstrained grant on the relevant business process policy step, then re-run the failing records.
When scoping ISU security for an inbound EIB, grant unconstrained access on the target business process policy for every domain the transaction touches, not only the domains for fields present in the load, since Workday validates the whole transaction step rather than only the changed fields.