Studio Splitter XPath Fails: Could Not Find Mapping for Prefix
What it means
A Splitter or other XPath-driven step in Studio fails because the XPath expression references a namespace prefix, such as ws, that is not registered in that step's namespace mapping table. Workday Core Connector output typically uses the ws prefix for its worker namespace, but a Splitter's default namespace map does not include it automatically.
Troubleshooting
- Open the failing step's XPath Explorer or namespace mapping panel and list every prefix currently registered.
- Compare that list against every prefix actually used in the XPath expression string, such as ws in /ws:Worker_Sync/ws:Worker.
- Confirm the exact namespace URI the missing prefix should map to by inspecting the raw XML the upstream step produced, since guessing the URI produces a different but equally confusing failure.
- Add the missing prefix-to-URI mapping to the step's namespace table and re-run against the same sample payload to confirm the expression now resolves.
Add the missing namespace prefix, such as ws, and its matching URI to the failing step's namespace mapping table.
When building any XPath expression against Core Connector or web service output, copy the namespace declarations directly from a sample response into the step's mapping table first, rather than typing prefixes from memory, so every prefix used in an expression is guaranteed to already be registered.