Configure Namespace with Both Salesforce Industry and Omnistudio Packages Installed

If you install the Salesforce Industry package and then install the Omnistudio package, some of the components of the Omniscripts are installed with the Salesforce Industry package namespace.

1. Find the namespace for your Omnistudio package in your org.
   1. From Setup, in the Quick Find box, enter Installed Packages , and then select Installed Packages.
   2. On the Installed Packages page, select the Omnistudio package, and note the Namespace Prefix value.
2. Update client-side Omniscripts.
   1. From the App Launcher, find and select Omniscripts.
   2. Search for the docGenerationSample/fndSingleDocxLwc Omniscript.
   3. Expand the Omniscript, and click the active version of the Omniscript.
   4. Select PickTemplate.
      
   5. In Lightning Web Component Name, replace the namespace with the Omnistudio package namespace.
      For example, if the Lightning Web Component Name value is <namespace>__<component> and the Omnistudio package namespace is omnistudio, then the updated Lightning Web Component Name value must be omnistudio__<component>.
   6. Activate the Omniscript.
   7. Similarly, update the docGenerationSample/fndMultiDocxLwc and docGenerationSample/fndMultiPDFConvertLwc Omniscripts.
3. Update server-side Omniscript.
   1. From the App Launcher, find and select Omniscripts.
   2. Search for the docGenerationSample/fndsingleDocxServersideLwc Omniscript.
   3. Expand the Omniscript, and click the active version of the Omniscript.
   4. Click Deactivate Version.
   5. Select PickTemplate.
   6. In Lightning Web Component Name, replace the namespace with the Omnistudio package namespace.
   7. Select ServerSideDocGeneration, and then click the link icon next to the Integration Procedure field on the INTEGRATION PROCEDURE ACTION PROPERTIES panel.
      
   8. Replace the namespace in the Remote Class value with the Omnistudio package namespace.
      
   9. Click Activate Version and close the tab.
   10. Similarly, update these integration procedure actions:

       • Integration procedure action: ServerSideDocGenerationWithTokenData and remote action: generateDocumentWithTokenDataService.

       • Integration procedure action: ServerSidePdfGeneration and remote action: generateDocumentServicePDF.