Failed to generate criteria.3.searchValue from template: {{{record.Field}}}. Details: "Field" not defined in undefined - 1:3

Integrator.io
1

I have created a Saved Search in NS to a look up on a field we were getting in the Payload for adding a record to the Journal Object. We have a Field Called TXName however NS need to the have the value Id entered. We have to do a look up in Celigo and I am getting the following error

Failed to generate criteria.3.searchValue from template: {{{record.trxName}}}. Details: "trxName" not defined in undefined - 1:3.

I did a global search on NS for the Name, and it is not showing up … Is this a data issues where it is in the souce file /system but has not been entered into the NS Journal

You can see in the payload the value is not Null

"externalid": "xxxxx",
"date": "10/31/2025",
"memo": "OCT Q4 2025 SIDISTRIBUTION 49 Actual",
"approver": "xxxx",
"subsidiary": "49",
"ftType": "Invoice",
"lines": [
{
"customerName": "Blue Owl Capital",
"debit": "2083333.33",
"fundAssetClass": "Actual",
"fundEstimate": "2",
"trxName": "FTR-YQM-25-Q4",
"memo": "Private Equity - Arrears",
"customer": "8006"
},

Can some one help on this I have a ticker open but trying all avenues for help

Lookup Cache - Hmmm
2

This issue above is related to the Design we designed our Look up to be at the header level nut the Searched search is at the line item, and we have two field that we need to do this with. we are thinking that Lookup cache is the best path because this could put a load on the Interface and process. The fact that they are at the line, and just this one transaction has 120 some odd is not good. If we had 10 invoices with 120 lines, each requiring two separate calls into NetSuite, it would completely bog down the system and would take hours to complete the process

Can we automate the updated to Lookup Cache or does that have to be manually. For example, create flow that on change would update the cache? Also, if you have any other suggestion on how to resolve the issues we are having?

3

Having a flow that listens for a record in NetSuite and pushes to lookup cache is a perfect idea for this. You could also make it a listener and batch flow so you can schedule syncs to it and rely on real-time updates to it.

Once you do that, you'd then need to perform the lookup to the lookup cache with a transformation 2.0 step on the export of your regular flow, or do a lookup step to the lookup cache where you then map the response to the results.

Since NetSuite doesn't currently support mapper 2.0, you can't use the lookup cache directly there in the mapper.

Lookup Cache - Hmmm