Dear All,
We are experiencing a critical production issue with the Customer Financials Flow within our Salesforce-NetSuite IO integration, requiring immediate attention.
The flow is failing under the following conditions:
Export Type: All or with a Limit: The flow fails with the error: "Script Execution Time Exceeded."
Export Type: Delta: The flow fails with the error: "Failed to run saved search because Search error: Parentheses are unbalanced."
The search filters being used are:
filters [[["custentity_celigo_sfio_sf_id","isnotempty",""],"AND",["transaction.posting","is","T"],"AND",["max(transaction.trandate)","onorafter","startoflastfiscalyear"]],"AND",[["lastmodifieddate","onorafter","31/05/2025 6:30 pm"]]]
Has anyone encountered similar errors or have any insights into resolving these issues? Any suggestions would be greatly appreciated.
It seems you are using a group in your filter but it looks like it is not set properly.:
Seems like the lastmodifieddate is in a apart group. Looks like a overnesting..
Can you share a screenshot of the filter?
Hi Nuri,
Find below the Screenshots of NetSuite Saved Search Filters and Results.
Could you also provide some screenshots of your Celigo export along with any additional criteria you're using?
Hi Nuri,
It's an IA flow, currently I have not set any Filters on the flow.
Even in IA settings(For Customer Financials); Only Saved Search is selected.
Interesting. Its a bit difficult as I cannot see everything from here however could you try duplicating the saved search in NS and stripping it down to a minimal version, just one or two default fields, no filters or extra settings and see if that works?
@Goutham_Pothugalla Is it possible that you had previously used expressions in your saved search? I've run into an issue previously where simply unchecking the "Use expressions" box but not actually removing the parentheses can cause issues when removing filters from the search criteria since it now has unbalanced (hidden) parentheses.
Hi @friendoftuesday,
Yes, I’ve tried this and noticed that the filters didn’t have parentheses earlier.
Appreciate the suggestion—thanks again!
Hi Nuri,
Thanks for pointing out the things to check. I’ve tried this—while the flow is able to pick up records using default or standard fields, it doesn’t seem to work when using summary fields.
Appreciate your help!
I’m currently working on this with support, and if we find a solution, I’ll be sure to keep you posted—it might be helpful for similar use cases in the future.
Also, feel free to let me know if there’s anything else you’d like me to look into.
Great to hear! Sometimes it helps to go step by step and reduce things to a minimal test case, especially when working with these kinds of saved searches.
