Loading

Net Zero Cloud: SASB Generate Document URL opens with error or 'form is not generated'

Publish Date: May 26, 2026
Description

Customers using Disclosure and Compliance Hub (DCH) in Net Zero Cloud may experience an issue where selecting the Generate Document button for a SASB disclosure successfully generates a document URL, but opening the URL results in an error instead of displaying the related template. In some cases, even after completing the SASB report setup in Disclosure and Compliance Hub, creating a SASB disclosure record and submitting the required details may fail to generate the expected form, resulting in an error page instead.

The exact error returned by the underlying flow is "This error occurred when the flow tried to create records: INVALID_INPUT: The content version Id is invalid or was deleted. An example for a valid JSON string format in the Request Text is {"templateContentVersionId": "068xx0000000x00xxx", "title":"NewDocTitle"}.".

This issue can occur when the Net Zero Cloud Disclosures for SASB managed package is installed but the required SASB OmniScript is not activated, the appropriate SASB DocGen template static resource (DOCX) for the relevant sector has not been uploaded, the user does not have the required DocGen Designer or OmniStudio permissions, or the disclosure definition version is not associated with the disclosure record.

This issue affects Enterprise, Performance, Unlimited, and Developer Editions using the Net Zero Cloud Growth license in Lightning Experience, and impacts users generating SASB disclosure documents through Disclosure and Compliance Hub (DCH), the Net Zero Cloud feature used to create and generate ESG reports such as GRI, CDP, SASB, and ESRS.

 
Resolution

Resolve the SASB Generate Document failure by completing each of the following sections in order.

Cause 1: Missing or incomplete SASB managed package install
1. Confirm the Net Zero Cloud Disclosures for SASB managed package is installed by navigating to Setup > Apps > Packaging > Installed Packages and verifying the SASB package is listed.
2. Switch to Salesforce Classic, navigate to Setup > Develop > Omni Processes (or App Launcher > Omni Processes), and search for the package OmniScripts (for example, names starting with SASB). If they are inactive, activate them.
3. In Files on each SASB Omni Process record, click Upload Files and upload the DOCX file from the SASBDocumentTemplateStaticResource folder for each of the four sectors: Financials Sector, Technology and Communications Sector, Services Sector, and Consumer Goods Sector. Switch back to Lightning Experience.

Cause 2: Missing user permission sets
1. Navigate to Setup > Users > Permission Sets.
2. Assign the following permission sets to every user generating SASB disclosures: Disclosure and Compliance Hub User, Omnistudio Admin (or Omnistudio User plus DocGen Designer), and DocGen Designer.
3. Open the SASB DocGen template record, click Related, and add the user under the template's user access list so the user is authorized to use the DocGen template.

Cause 3: SASB OmniScript or DocGen template not activated
1. From the App Launcher, find and select Omnistudio Designer.
2. Open the SASB OmniScript referenced by the disclosure definition version and click Activate Version.
3. From the App Launcher, find and select Document Template Designer, open the SASB DocGen template, and click Activate.

Cause 4: Disclosure record missing the Generate Document button or wrong button used
1. Navigate to Setup > Object Manager > Disclosure [Disclosure__c] > Page Layouts > Disclosure Layout > Mobile & Lightning Actions.
2. Drag the Generate Document action (provided by the SASB installer) to the Salesforce Mobile and Lightning Experience Actions section. For SASB packages always use Generate Document, not Generate Document (V2). If the Net Zero Cloud Disclosures for ESRS package is also installed in the org, use the Generate Document button provided by the ESRS installer for all packages.
3. Save the page layout.

Cause 5: Disclosure definition version not linked
1. From the App Launcher, find and select Disclosures and Compliance Hub and open the failing SASB disclosure record.
2. Confirm the Disclosure Definition is set to the correct Salesforce Template for SASB sector (Financials, Consumer Goods, Services, or Technology and Communications) and that the Disclosure Definition Version field is populated. If empty, edit the record and select the active version, then save.
3. Refresh the disclosure record. The disclosure document URL takes a few seconds to appear; if it does not appear, refresh the page again.

Confirm the issue is resolved by opening the SASB disclosure record, clicking Generate Document from the actions menu, waiting for the disclosure document URL to populate, and opening the URL to verify the SASB DOCX template loads without the "INVALID_INPUT: The content version Id is invalid or was deleted" error or the "form is not generated" error.

Knowledge Article Number

005385134

 
Loading
Salesforce Help | Article