#DataRaptor2 debatiendo

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 :)

IF(

    AND(

        ISNOTBLANK(%LoanApp:Applicant:axisltd_Total_Net_Income__c%), 

        ISNOTBLANK(%LoanApp:Applicant:axisltd_Total_Other_Income__c%)

    ), 

    FUNCTION(

        'AxisOmniGetPicklistLabel',

        'getIncomeDetail',

        (

            %LoanApp:Applicant:axisltd_Business_Income_Source__c% + '$' + 

            %LoanApp:Applicant:axisltd_Total_Net_Income__c% + '$' + 

            %LoanApp:Applicant:axisltd_Total_Other_Income__c% + '$' + 

            %LoanApp:Applicant:axisltd_Other_Income_Source__c% + '$'

        )

    ), 

    []

)

Approach 1: Utilizing Output Parameters and Session Variables:

DataRaptor for Parent Record:

In your initial DataRaptor that creates the parent record (Object A), add an Output Parameter. Name it something like parentId.

1. Set the value of this parameter to the ID of the newly created parent record. This can be achieved using Apex code like {!record.Id} within the DataRaptor action.

Store Parent ID in Session Variable:

After the DataRaptor action that creates the parent record, use a Set Session Variable element in your OmniScript.

Set the variable name to something like parentId and its value to the output parameter from the DataRaptor ({!$Flow.parentId}). This stores the parent ID in a session variable accessible throughout the script.

DataRaptor for Child Records:

In your DataRaptor that creates child records (Object B), use the {!$Flow.parentId} session variable to reference the ID of the parent record.

Set the ParentId field on the child records being created to this session variable value.

Optional: Refresh Step Data (if needed):

If you need to display information about the newly created records in the same step, consider using a Refresh Step Data element after the DataRaptor actions. This will reload the step data with the updated information.

Approach 2: Leverage Navigation with Data Parameters:

DataRaptor for Parent Record:

Configure your initial DataRaptor to create the parent record as usual.

Navigation with Data Parameters:

After creating the parent record, use a Navigate element in your OmniScript.

In the navigation settings, choose the next step as the target step.

Set Data Parameters. Create a parameter named parentId and set its value to the ID of the newly created parent record ({!record.Id}).

Retrieve Data Parameter in Next Step:

In the next step of your OmniScript, use a Get Data Parameter element.

Set the parameter name to parentId to retrieve the ID passed from the previous step.

DataRaptor for Child Records:

In your DataRaptor that creates child records, use the {!$Flow.parentId} flow variable (populated from the Get Data Parameter element) to reference the ID of the parent record.

Set the ParentId field on the child records being created to this variable value.

Choosing the Right Approach:

Approach 1 is simpler for basic scenarios where you don't need to display information about the newly created records in the same step.

Approach 2 offers more flexibility if you need to access data from the previous step (parent ID) within the current step for display purposes.