---
title: "Why does an Orchestration JSON path put a leading space in…"
description: "A Create Values concatenation that starts with an empty string block prefixes a space onto the WID. Delete the blank block and log the resolved value."
url: https://kiweely.com/guides/workday-orchestration-json-path-leading-space-wid
---

# Why does an Orchestration JSON path put a leading space in a WID?

A Create Values concatenation with an empty String block puts a leading space on the WID so Workday rejects the reference. Delete blank blocks and inspect the resolved value before the API step.

-   **Checked** against Workday on November 17
-   Applies to **Workday Orchestrate Create Values and JSONPath**
-   2 min read
-   Published November 17
-   By Kiweely

An orchestration that builds a Worker (or other) reference can produce XML or JSON where the WID looks correct but Workday rejects it because the resolved string starts with a space. The path expression is often fine. A **Create Values** concatenation that includes an empty String block before the real binding is what inserts the whitespace.

## How Create Values builds the string

Workday’s Create Values reference exists to create key/value pairs for later steps. The documented example joins `firstName` and `lastName` with a space into `fullName`. In Orchestration Builder you stack value blocks for one key. Each block contributes to the output. An empty String block is easy to miss in the UI and still concatenates—so the next block’s WID arrives with a leading space.

JSONPath extraction itself is separate. Workday’s employee-data example binds `workerID` with `stringAtJsonPath` on `$.id` from a prior API response. Use that single binding for a WID. Do not wrap it in a multi-block concatenation that begins with a blank string.

## What the bad payload looks like

You may see a reference element whose text node has a space before the id, for example a Worker reference whose value is `3aa5550b…` instead of `3aa5550b…`. Workday treats that as an invalid id. The orchestration error often blames the reference, not the Create Values step.

## Fix steps

1.  Open the failing orchestration and find the Create Values (or equivalent) step that feeds the reference id into the API request.
2.  Inspect every concatenation block on that key. Delete blank String blocks and any block that only exists “for spacing.”
3.  Prefer one binding: the JSONPath (or prior-step) value alone, with no prefix or suffix blocks.
4.  Log or map the resolved value immediately before the API step. Whitespace will not show clearly in the expression editor; it will show in the resolved string.
5.  Compare expected vs actual payload around the id character by character, then rerun.

## JSONPath checklist while you are there

Workday’s JSONPath support table covers dot and subscript paths such as `$.data[0].descriptor` and `$.id`. Unsupported patterns include negative array indexes and filters that refer to the root. If the path returns empty and you fall back to a default string that includes spaces, you can get the same invalid WID symptom from the fallback—not from JSONPath itself.

See the companion prevention guide for a build checklist that keeps WIDs free of whitespace from the first draft of the orchestration.

## Frequently asked questions

### Why is my Worker\_Reference WID invalid even though the id looks right?

Compare the resolved value character by character. A leading or trailing space from a Create Values concatenation makes the WID fail even when the hex digits look correct.

### Does stringAtJsonPath add the space?

Workday’s JSONPath helpers return the string at the path. The usual source of a leading space is an empty concatenation block placed before that binding in Create Values.

### How should I build a full name versus a WID?

Create Values is documented for joining first and last name with a space. For WIDs and other reference ids, do not concatenate optional blank string blocks in front of the id.

## Sources checked

-   [Reference: Create Values](https://developer.workday.com/documentation/GUID-c310de5e-1e37-4ca6-bca3-52033d7ccb18/ReferenceCreateValues)
-   [Concept: JSONPath Support](https://developer.workday.com/documentation/GUID-d1c2ce08-a02e-4803-8347-207f3c3b2d30/ConceptJSONPathSupport)
-   [Example: Get And Create Workday Employee Data](https://developer.workday.com/documentation/mxj1630014392721/ExampleGetAndCreateWorkdayEmployeeData)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How do I stop Orchestrate JSONPath from corrupting WIDs with spaces? Keep WID Create Values bindings to one JSONPath block—never blank string prefixes. Use stringAtJsonPath for ids; reserve multi-block joins with spaces for display names only.](https://kiweely.com/guides/workday-json-path-wid-leading-whitespace-prevention)
-   [### “Permission Denied (S22)” in a business-process-triggered orchestration S22 is Workday’s 403 Permission Denied: the request was understood but the user it ran as lacks the security for it. In a business process orchestration, first find that user (the ISU, the service step’s run-as user or the launch user), then grant the domain the endpoint is secured by.](https://kiweely.com/guides/workday-bp-orchestration-permission-denied-s22)

### More guides on Orchestrate

[All 86 guides](https://kiweely.com/guides#orchestrate)

-   [How do I fix “WCPISU is not configured” on an Extend orchestration?](https://kiweely.com/guides/workday-extend-wcpisu-not-configured-error)
-   [Start with a Workday packaged connector before custom Studio](https://kiweely.com/guides/workday-packaged-connector-before-studio)
-   [Orchestrate is not a bulk-load replacement for Workday EIB or Studio](https://kiweely.com/guides/workday-orchestrate-not-a-bulk-load-replacement)
-   [When to use Workday Document Transformation instead of Orchestrate or Studio](https://kiweely.com/guides/workday-document-transformation-connector-when)
-   [Why Workday Orchestrate Trigger Integration will not launch an EIB](https://kiweely.com/guides/workday-trigger-integration-cannot-launch-eib)
-   [Three cases where Workday still wants Studio](https://kiweely.com/guides/workday-studio-three-cases-keep-studio)
-   [The 25-Second Synchronous Orchestrate Trap](https://kiweely.com/guides/workday-orchestrate-25-second-sync-trap)
-   [What is the best AI tool for building and testing Workday Studio integrations and Orchestrations?](https://kiweely.com/guides/ai-tools-for-workday-studio-and-orchestrations)

### From the blog on Orchestrate

[All posts](https://kiweely.com/blog)

-   [Debugging Workday Extend apps and orchestrations in kiweely](https://kiweely.com/blog/debugging-workday-extend-apps-orchestrations-kiweely)
-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
