Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Invoice Group Saved Search Performance when including Transaction Fields
I am having significant performance issues with Invoice Group Saved Searches when I include Transaction fields...
This is the simple search I am running:
As you would expect, running this search opens the results in approx. 2-3 seconds:
That particular Invoice Group contains 4 Invoices, which are relatively small (1, 2 or 3 lines on each).
If I include the Transaction field to show the items:
Then the search takes slightly longer, maybe 3-5 seconds:
And this performance is consistent as you add in other fields from the Transaction subtable - up to a point.
After various testing (where I thought a specific field may be causing performance issues), I now believe that there is simply a threshold of the number of Transaction Fields that can be included before there is a dramatic drop in performance. I think it is 13 (but I'm not 100% sure) - but once you go past this, the Search then takes over