Extend Orchestration: JSON Path Binding Inserts a Leading Space, Invalidating the WID
The error <wd:Worker_Reference>
<wd:ID wd:type="WID"> 3aa5550b7fe348b98d7b5741afc65534</wd:ID>
</wd:Worker_Reference>
which fails as WID becomes invalid.
What it means
A Create Values step in Extend's Orchestration Builder had an empty, blank "String" concatenation block placed before the real data binding. Concatenating an empty string still contributes to the output, so the resolved value picks up a leading space, and Workday rejects the WID once it no longer matches exactly.
Troubleshooting
- Open the failing orchestration in Orchestration Builder and find the Create Values (or equivalent data-binding) step that produces the field feeding the XML/JSON payload.
- Look for extra concatenation blocks stacked before the real value - especially blank "String" type blocks, which render as an easy-to-miss empty box in the UI.
- Log or inspect the actual resolved value right before it's used, not just the binding expression - a leading or trailing space won't show in the expression editor but will show in a runtime log of the resolved value.
- Compare the expected vs. generated XML/JSON payload character-by-character around the ID value to confirm whitespace, not a data issue, is the cause.
⚡ Quick fix
Delete the stray empty concatenation block from the Create Values step so the intended binding is the first (or only) element producing that field.
✓ Permanent fix
When building multi-block data bindings in Orchestration Builder, keep concatenation chains limited to blocks that contribute real content, and add a payload-logging step to new orchestrations before shipping any that assemble reference IDs from bound values.
Was this helpful?