---
title: "What does Workday Studio “Content is not allowed in…"
description: "Content is not allowed in prolog means the XSLT step received non-well-formed XML—often HTML, a BOM, or text before the root. Fix the input payload."
url: https://kiweely.com/guides/workday-studio-content-is-not-allowed-in-prolog
---

# 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 November 17
-   Applies to **Workday Studio XSLT and XSLT+ steps**
-   2 min read
-   Published November 17
-   By Kiweely

**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 |
| --- | --- |
| Wrong Input property | Input set to `message` when only `rootpart` or `soapbody` is XML |
| HTML or rich text in a field | Job descriptions and notes pasted from a browser into a custom object or report field |
| BOM or invisible characters | File saved with a UTF-8 BOM, or copy-paste that inserted a character before `<?xml` or the root |
| Leftover error text | A prior failure wrote status text into a field that later becomes part of the XML stream |
| Non-XML upstream step | A 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

-   [Reference: XSLT+ Step Properties](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/transform-steps/xnl1508496879525.html)
-   [Reference: XSLT Step Properties](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/transform-steps/mkd1508496404543.html)
-   [Concept: Transform Steps](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-design/transform-steps/dnf1507398621435.html)
-   [Transforming Data](https://doc.workday.com/workday-education/en-us/course-manuals/creating-integrations-using-workday-studio/transforming-data.html)

## Related guides

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

-   [### What is the best AI tool for building and testing Workday Studio integrations and Orchestrations? No single tool wins both halves. Developer Copilot for Orchestrate builds orchestrations in Workday; test vendors automate end-to-end checks; Kiweely Vine drives your installed Studio to build, run and test. Studio itself has AUnit.](https://kiweely.com/guides/ai-tools-for-workday-studio-and-orchestrations)
-   [### How to Blank Out Text Fields and Nullify Reference Values on Workday Extend Business Objects via Inbound EIB Using {empty} Leaving a spreadsheet cell blank or entering “” or null in an Inbound EIB does not clear existing field values on a Workday Extend Business Object. Learn how to use the {empty} tag, avoid the leading/trailing whitespace trap in Excel, and remove specific multi-instance values.](https://kiweely.com/guides/workday-extend-eib-clear-text-nullify-fields-empty-tag)

### More guides on Integrations and APIs

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

-   [Why does Workday RaaS time out for non-admin users but work for admins?](https://kiweely.com/guides/workday-raas-timeout-non-admin-user)
-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [How do I set an Integration System Security Group for an Integration System User?](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)

### From the blog on Integrations and APIs

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

-   [When the Answer Is Chat, a Screen, or a Running Integration](https://kiweely.com/blog/when-the-workday-job-is-chat-a-screen-or-an-integration)
-   [Personal AI Plus Shared ISU Credentials: The Compound Workday Failure Mode](https://kiweely.com/blog/personal-ai-plus-shared-isu-compound-failure)
-   [BYO API Keys on a Workday Consultant Laptop: Who Is the Controller?](https://kiweely.com/blog/byo-api-key-workday-consultant-laptop)

## 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.
