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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
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