Skip to content
KiweelyKiweelyKiweely

What does Workday Studio “Content is not allowed in prolog” mean?

Content is not allowed in prolog means XSLT received non-well-formed XML—HTML, a BOM, or text before the root. Point Input at real XML and sanitize rich text before building the document.

  • Checked against Workday on
  • Applies to Workday Studio XSLT and XSLT+ steps
  • 2 min read
  • Published
  • By Kiweely
On this page

Content is not allowed in prolog in a Workday Studio integration means the XML parser rejected the document before XSLT ran. Something appears before the root element—or the payload is not XML at all. The XSLT stylesheet is often fine; the input is not.

What the XSLT step needs

Workday’s transform documentation states that the XSLT and XSLT+ steps transform an XML document with an XSL stylesheet. XSLT+ reads the selected Input (message, soapbody, attachment, rootpart, or variable), applies the stylesheet at Url, and writes to the selected Output.

If Input points at JSON, CSV, HTML, or a message part that already mixed text with XML, the processor never reaches your templates. The prolog error is the parser’s way of saying the first bytes are not a legal XML start.

Common causes in Studio assemblies

Cause What to check
CauseWrong Input property What to checkInput set to message when only rootpart or soapbody is XML
CauseHTML or rich text in a field What to checkJob descriptions and notes pasted from a browser into a custom object or report field
CauseBOM or invisible characters What to checkFile saved with a UTF-8 BOM, or copy-paste that inserted a character before <?xml or the root
CauseLeftover error text What to checkA prior failure wrote status text into a field that later becomes part of the XML stream
CauseNon-XML upstream step What to checkA previous step emitted text or JSON into the variable you pass to XSLT+

Fix steps

  1. Capture the exact bytes the XSLT+ step receives (assembly log or a write of that variable/message part). Open them in a text editor that shows invisible characters.
  2. Confirm the document starts with optional whitespace only, then either an XML declaration or the root element—no HTML tags, no status sentences, no BOM.
  3. Set the XSLT+ Input property to the part that holds the XML (rootpart or soapbody when appropriate).
  4. Sanitize rich-text fields before they are inserted into XML: strip tags or escape them so the document stays well-formed.
  5. Clear leftover error or status fields on the source record so a previous failure cannot poison the next run’s payload.
  6. Run the same stylesheet against a clean sample in a standalone XML tool. If that works, the Studio input path—not the XSLT—is at fault.

Workday recommends XSLT+ over the older XSLT step because XSLT+ supports XSLT 1.0 through 3.0. Switching processors does not fix a non-XML input.

Kiweely Vine can work with Studio projects on your computer when you are diagnosing an assembly, but the payload must still be well-formed XML for XSLT+ to run.

Frequently asked questions

Is Content is not allowed in prolog an XSLT bug?

Usually not. It is an XML parse failure on the input. The stylesheet never runs until the input document parses.

Which Studio Input setting should I use?

Set XSLT+ Input to the message part that actually holds XML—commonly rootpart or soapbody for SOAP—not a part that holds JSON, CSV, or mixed text.

Can HTML in a job description field cause this?

Yes. Rich text embedded into an XML document without proper escaping produces content the XML parser rejects before XSLT runs. Strip or escape markup before building the XML.

Sources checked

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.