EIB Put Compensation Eligibility Rule: Invalid Instance From Mismatched WID Columns
What it means
Building a Put Compensation Eligibility Rule EIB, the same WID got pasted into both the Source External Field column and the Target Instance+ column of a condition row. Workday reads the Source External Field column as which business object type the condition filters on and the Target Instance+ column as the actual filter value, so putting the same WID in both makes the row treat the business object type itself as if it were the value, and the load rejects it as an invalid instance.
Troubleshooting
- Open the failing condition row and compare the Source External Field and Target Instance+ columns: if they hold the same WID, that is the signature of this error.
- Confirm what the Source External Field column should actually reference: the business object type driving the filter (for example Country of Location, Compensation), not the specific value being filtered on.
- Look up the correct WID for that business object type definition itself (not the value's WID) and put it in the Source External Field column.
- Leave the Target Instance+ column holding the actual filter value's WID unchanged.
- Test the fix on a single row before reloading the full batch, since this kind of copy paste mistake tends to repeat across every row in a bulk condition load.
Correct the Source External Field column to hold the WID of the condition's business object type, keep the Target Instance+ column as the actual filter value's WID, then reload the row.
When building or copying eligibility rule EIB templates for bulk condition loads, keep the two WID columns visibly distinct in the working spreadsheet (object type WID vs value WID) and add a sanity check row or formula that flags any row where the two columns match, since that combination is never valid.