Salesforce Facts by Abhishek

Suppose we want a particular step in OmniScript to be visible only during the forward navigation and it should not visible during previous button click. To implement this, we can use one flag variable and two set values elements and the same flag can be used in the conditional view of the particular step. The first set value would set the flag to true and next one will set the flag to false. In this example. we are using the flag variable showStep2 to show the step2 only during forward navigation. Attached is the screenshot.

Suppose we have a requirement in Omnistudio where the user needs to enter some data in the Omniscript to create an Sobject record and also would upload one or more files to attach to the same record. For file input, there is a Content Parent ID attribute which can be populated, but in this case the parent record is not created yet. In order to achieve this, we can create a Data Raptor Load to create the Sobject record and then using Linked mapping we can map the LinkedEntityId and the ContentDocumentIds can be passed from the JSON node. In this example, the user creates an account record and at the same time, uploads and attaches one or multiple files to the created record. Reference:  https://help.salesforce.com/s/articleView?id=xcloud.os_upload_files_and_images_in_omniscripts_23397.htm&type=5 Attached are the screenshots.

The SOQL LIKE operator can be applied to multiple strings. For this, we can construct a set/list with the values and use that in the SOQL query. This avoids writing LIKE operator for each of the values. Reference:  https://salesforcelynx.medium.com/how-to-use-like-keyword-once-for-multiple-string-comparison-in-a-soql-823020345a3e

There's a known issue while using equals to NULL filter in Data Mapper Extract. To fix this, we need to add a not equals to operator. In this example, we are fetching contacts without AccountId populated. Attached are the screenshots.

If we are using the Select input of Sobject source in Omniscript, there is no point & click option to configure the default value. We can make use of the 'Edit Properties As JSON' option to set the default value. In this example, we are selecting an account from the typeahead block in the previous step and in the current step, setting the default value of the Active picklist in the JSON as:  "defaultValue": "%AccountInfo:SearchAccount-Block:Active__c%" Attached are the screenshots.

Data Raptor Turbo extract adds a parent node in the response JSON. So, while using it with Type Ahead block the parent node needs to be specified in the Response JSON Path to get the desired output. Reference:  https://help.salesforce.com/s/articleView?id=000394510&type=1