Post-DataPack Migration Steps

Perform these steps after the DataPack migration is complete. This section applies to Salesforce orgs released before Winter '24.

Note When migrating from managed package components to standard at run time components, manually activate your scripts to prevent errors in the CPQ_ChangeToOrder Omniscript or other standard processes. If a custom Omniscript nests a standard script but remains turn off, the runtime process fails.

After the DataPack migration and activation of all components, add your changes to the current components with these steps.

1. Clone the new migrated components and add all your changes.
2. When modifying the response format for Integration Procedures (IPs) that use Standard Cart APIs, the data structure shifts to a JSONResult format.
3. Here are the names for the IPs:
   • CPQ_GetAssetViewerLineItems
   • CPQ_SubmitDiscountsForApproval
   • CPQ_SubmitOrder
   • MultiService_CheckoutOrder
   • CPQ_UpdateCartItem
   • CPQGetCarttems
   • CPQDeletedItemFromCartIP
   • getCartProducts IP: getProducts, getPromotions remote actions
4. To restore the original data format, update your IP by using these steps:
   1. Identify the Remote Action step within the IP that calls the Standard Cart API.
   2. In the Additional Input section for that step, add an entry for convertJSONResultToJSON and set it to true.
   3. Preview the step to verify that the response format matches your requirements.
   4. Save and activate the IP.

   When by using the standard Omnistudio Runtime and standard cart API if you encounter the error: Apex Type unsupported in JSON: Schema.SObjectType, add convertJSONResultToJSON setting to the IP and set its value to true. Conversely, if switching to the classic API, remove convertJSONResultToJSON or set its value to false.