# How to Avoid Having a Lookup Replace Record Context **URL:** \ **Category:** Integrator.io\ **Tags:** lookup, salesforce\ **Created:** [January 2, 2026, 12:04am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972 "2026-01-02T00:04:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mark\_Salamon1](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@Mark\_Salamon1](https://connective.celigo.com/u/Mark_Salamon1)\ **Post date:** [January 2, 2026, 12:04am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/1 "2026-01-02T00:04:58Z")
Here is my flow: Salesforce Export → NetSuite Import1 (with response mapping of errors to ns\_errors) –\> Salesforce Lookup (using complex SOQL to retrieve multiple records related to the SF record, but these are NOT in a related list), which makes the data available via results mapping –\> NetSuite Import2 –\> Salesforce Import to write back the new NS ID (If Succeed) –\> Salesforce Import (If Fail) I only want NetSuite Import2 to run if NetSuite Import1 succeeds. I am trying to use an Input Filter based on ns\_errors, but ns\_errors is no longer available because the intervening lookup has replaced the record context. How can I overcome this? I only want the lookup to enrich the data from the original record not replace it. I also want the final SF Imports to be triggered conditionally based on ns\_errors. ---
**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\ **Post date:** [January 5, 2026, 5:43am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/2 "2026-01-05T05:43:48Z")
I'm not sure what you mean by this "because the intervening lookup has replaced the record context". The lookup wouldn't override anything on the original record unless your response mapping for the lookup is the a field that already exists on the source record. For example, if you response mapped data to ns\_errors, then that would override ns\_errors on your source record. ---
**Author:** ![Mark\_Salamon1](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@Mark\_Salamon1](https://connective.celigo.com/u/Mark_Salamon1)\ **Post date:** [January 5, 2026, 12:16pm UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/3 "2026-01-05T12:16:54Z")
I would agree that’s what should happen. But whether it’s an input filter or branching, ns\_errors is no longer available after the lookups. ☹ ---
**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\ **Post date:** [January 6, 2026, 1:31am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/4 "2026-01-06T01:31:18Z")
Are you seeing it disappear while previewing data or during runtime as well? ---
**Author:** ![Mark\_Salamon1](https://avatars.discourse-cdn.com/v4/letter/m/b5ac83/32.png) [@Mark\_Salamon1](https://connective.celigo.com/u/Mark_Salamon1)\ **Post date:** [January 6, 2026, 4:53am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/5 "2026-01-06T04:53:58Z")
when building the flow, the errors I have defined are not available either as input filters or as branching conditions. they are only available for the step that directly follows the step where the errors were defined in the response mapping. ---
**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\ **Post date:** [January 6, 2026, 4:55am UTC](https://connective.celigo.com/t/how-to-avoid-having-a-lookup-replace-record-context/5972/6 "2026-01-06T04:55:22Z")
Can you share your flow zip?