#Omnistudio5 discussing

@Jothish B S the standard osGenerateAndPreviewDocument component does not automatically take the response of any Integration Procedure action added earlier in the OmniScript and use it as token data. The generated document uses the JSON available to the document generation step, based on the template’s token mapping method.

Trailhead explains that document templates can use JSON input data, and that the Token Mapping Method controls how tokens are populated. It also says you can use OmniDataTransform or a custom class for that mapping. Reference: (Trailhead)

For your example token: {{Quote.QuoteNumber}} the JSON used by document generation must look like this:

{  "Quote": {    "QuoteNumber": "Q-0001",    "AccountName": "ABC Customer"  }}

If you have quote lines, the final JSON must also contain a repeatable array, for example:

{  "Quote": {    "QuoteNumber": "Q-0001",    "AccountName": "ABC Customer",    "QuoteLines": [      {        "ProductName": "Product A",        "Quantity": 2      }    ]  }}

Correction to do would be: don’t use an 

Extract Data Mapper as the final token mapper if your source is already the IP response JSON. Use a Transform Data Mapper to shape the IP response into the exact JSON structure expected by the Word template.

Also open the OmniScript preview/debug panel and check the Data JSON after the IP action runs. If the Quote node is not present at the root, or if it is nested under something like IPResult.Quote, your tokens will not resolve.

For server-side generation, Salesforce also documents an Integration Procedure pattern using DocumentServiceGateway.generateDocumentWithTokenData, which is more suitable when the IP is responsible for preparing the full token JSON. Reference: (Salesforce)

Decide the pattern:

Use standard LWC + OmniScript JSON if the IP output is stored in the OmniScript JSON exactly as the template expects.

Use server-side IP document generation if the IP should fully control token data and document generation.

The missing part is mapping the IP response into the exact token JSON consumed by document generation.

Seems like not doable. I tried setting 'UseTemplateDRData' to true but it didn't worked. When you Preview the omniscript this is shown for that lwc component. I also found only this doc for the lwc

Hi @Walter Fernandez. You can add the FlexCard to an LWC and handle the event programmatically as per https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.events_handling. See 'Attach an Event Listener Programmatically.'  The code below defines an LWC that updates the OmniScript JSON with the selected rows. Also useful: https://help.salesforce.com/s/articleView?id=sf.os_datatable_lightning_web_component_readme.htm&type=5

Update: video explanation of selectrow event handling here: https://www.youtube.com/watch?v=WnHIXSzcdKM

Update 2: see this resource for more details and sample code on this topic  https://quip.com/ftaxAqKJknkj

<template>

    <!-- Embedded Flexcard -->    

    <c-cf-test-data-table-selectable></c-cf-test-data-table-selectable>    

</template>

import { LightningElement, api, track } from 'lwc';
import { OmniscriptBaseMixin } from 'omnistudio/omniscriptBaseMixin';
export default class DatatableSelectable extends OmniscriptBaseMixin(LightningElement) {
    selectedRows=[];  
    connectedCallback(){   
        this.template.addEventListener('selectrow', evt => {   
            console.log('selectrow event', JSON.stringify(evt.detail.result)); 
            // if event's selectrow is true, add it to selectedRows; if false, it's been unchecked >> remove it       
            if (evt.detail.result.selectrow) {
                this.selectedRows.push(evt.detail.result);
            } else {
                this.selectedRows.forEach(function(item, index, object) {
                    if (item.uniqueKey === evt.detail.result.uniqueKey) {
                        object.splice(index, 1);
                    }
                })               
            }            
            this.omniApplyCallResp({"selectedRows": this.selectedRows });
        });           
    }
}

Hi @Cameron Brand, may be it is becasue of this known issue : with the Document Generation feature after following the steps in this article: https://help.salesforce.com/s/issue?id=a028c00000zjOJB

I would sugguest report so that you could get the updates on the fix  

Hope that helps  

thanl you 

The following article explain the concept of Object Field Aliases: https://help.salesforce.com/s/articleView?id=ind.object_variables_in_expression_sets.htm&type=5

It is also linked on the same trailhead module you mentioned above. If you have created the Special Dev Org for the challenge, the aliases would've been configured already. 

The this.omniNavigateTo() function triggers a page navigation event. When used inside an LWC embedded within an OmniScript, it often bubbles up and causes the entire OmniScript container to refresh or re-initialize, looking like a "reload."

Solution:

Instead of this.omniNavigateTo(), use the

1. If moving to the Next Step:

javascript
this.dispatchEvent(new CustomEvent('omninesxtstep'));

If updating data:

javascript
this.omniApplyCallResp({ "yourData": "value" });

Why it happens: omniNavigateTo is designed for PageReference navigation (like moving from Salesforce Page A to Salesforce Page B). When you call it, the framework assumes you are leaving the current context, so it reloads the component wrapper. Avoid using it for simple step transitions inside the same OmniScript. 

1. https://trailblazers.salesforce.com/profileView?u=0053A00000FTqkWQAT

 Unlocking the Per-Row Fix Use %

Index% in conditional views for row-specific logic. 

Easy Configuration: Radio: ContactType (New/Existing). 

Display in Typeahead: {%ContactType%} == "Existing".  

{%ContactType%} == "New" refers to a novel field.  

Boom! distinct rows. Now try a few entries—mix 'n match works!

Hi @Sonal .

, 

I know I am too late, but did you find any solution for this. I am stuck with a similar problem where I need to display a form multiple times on separate Steps.