You are here:
Omnistudio Document Generation Troubleshooting Reference
Use this table to identify common issues with Omnistudio Document Generation, what they mean, and how to fix them.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, Unlimited, and Developer Editions |
| Issue | What It Means | How to Fix It |
|---|---|---|
| We couldn't generate the document. <recordId> + Invalid XML pseudo-attribute 'version' value ' | An RTB_ token in the .docx template is wrapped inside a text box, which generates invalid XML and prevents the document from being created. | Open the .docx template in Microsoft Word, locate the RTB_ tokens, remove any surrounding text boxes, and place the token directly in the document body. Save and try again. If the issue persists, contact your Salesforce admin. |
| We couldn't generate the document. Could not generate document: Scope parser execution failed. Try again or ask your Salesforce admin for help. | The tokenData passed to DocGen contains a null value within a nested array or object. DocGen can’t process null values in nested token data structures. The issue isn’t caused by JSON payload size. This error can occur even if document generation previously worked. | Inspect the tokenData passed to the document generation call, identify any null values in nested arrays or objects, and remove or replace them with empty string before trying again. If the issue persists, contact your Salesforce admin. |
| Access to XMLHttpRequest at 'https://<orgname>--omnistudio.sandbox.vf.force.com/resource/<resourceId>/omnistudio__vlocity_core_assets/latest/vlocity_core_assets.js' from origin 'https://<orgname>.sandbox.lightning.force.com/' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | The Omnistudio sandbox Visualforce page origin isn’t listed in the org's CORS allowlist, blocking the browser from completing the request. | In Salesforce Setup, open CORS, click New, and add the blocked origin URL. For example, https://<orgname>--omnistudio.sandbox.vf.force.com). Save and perform a hard browser refresh 3–4 times. If the issue persists, contact your Salesforce admin. |
Did this article solve your issue?
Let us know so we can improve!
