#Omnistudio9 diskutieren mit

Hi Rakesh - the root issue is that the window online/offline events (and navigator.onLine) are inherently unreliable, and Linux Chrome is the worst case. Chromium marks the browser 'online' whenever there is any network interface with an IP - even a virtual or IPv6 adapter with no real internet - and it often never fires the offline event on Linux. So on that one Ubuntu user's machine the events genuinely will not fire; it is a documented Chromium limitation, not your code. 

So do not gate your OmniScript logic on those events. Two robust patterns instead: 

1. Handle the failure at the call, not before it. Wrap the DataRaptor IP remote action so that when it fails (network error or timeout) you catch it and show your friendly 'you are offline' message plus a real retry - rather than trying to predict offline up front. In OmniScript, use the element's error handling / a Set Errors plus conditional navigation so the hard error banner never shows. 

2. If you want a proactive signal, run a lightweight heartbeat - a periodic fetch to a tiny known endpoint with a short timeout - and treat a failed or timed-out fetch as offline. That actually tests reachability, which the browser events do not. 

navigator.onLine is fine as a hint (if it says false, you are definitely offline), but never as the source of truth. Catching the actual remote-action failure is what fixes the ungraceful error for everyone, including that Ubuntu user. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

@Vijay Sadhu

, 

Check the official article below; it will help you, 

If the JSON is being updated correctly, then the issue is likely related to the OmniScript UI not re-rendering after the LWC updates the data.

A few things I'd check:

•  Make sure the data is being updated through omniApplyCallResp() or another supported OmniScript API. 
•  Verify whether the read-only fields are bound directly to the updated JSON node. 
•  Some OmniScript elements don't automatically refresh when data changes outside their lifecycle. In those cases, navigating to the next step and back often confirms whether it's a rendering issue rather than a data issue. 
•  If you're using a custom LWC, you may need to trigger a refresh/re-render after updating the OmniScript data. 

If the values appear correctly in the OmniScript JSON but not on screen, focus on how those specific read-only fields are being rendered and whether they're re-evaluating their data source after the update.

Hi, 

Transform the value before passing to DataRaptor

Option A — Formula Element in OmniScript Add a Formula element after the Time picker:

%timeField% & ":00.000Z"

This turns 14:00 → 14:00:00.000Z. Map this formula output to DataRaptor, not the raw picker value. 

Option B — SetValues / DataJSON manipulation Use a SetValues element to construct the correct string:

json

{
  "transformedTime": "{timeField}:00.000Z"
}

Use a Transform action in an Integration Procedure to append :00.000Z before the Load step hits Salesforce. 

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