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
How to improve Map/Reduce (In)Efficiency on Transaction Lines?
I understand the basic concept of the Map/Reduce script to take all the elements (results) from the Search in the Map stage and process them individually (so that the script actions can be paused / resumed as required by other NetSuite processes).
My particular script is taking a search of multiple transactions, and then multiple (but not all) lines on each transaction.
In this scenario, the Map/Reduce logic does not make sense as the script appears to be loading and saving the transaction for each line result (which is hugely inefficient and slow).
Is there any way to use a Map/Reduce but configure it to 'group' all lines in a transaction into a single action so that the record is only loaded and saved once?