Lookup Cache - Hmmm

All, I have a question on the Lookup Cache vs Statis Mapping

IU started another discuss and this aligns closer with the Issue.

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

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?

I