Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Behavior of Map/Reduce script when it yields?
The documentation seems to provide no details beyond that yielding is handled for you. However, I have noticed odd behavior. For example, I counter I have as a global variable that gets incremented in my map stage will get reset whenever the script yields.
So when the script yields, do I loose everything in memory? Or am I running a poor test or misunderstanding something?
If I'm right, what's the best way to deal with this? The best I can think of is to check how much governance is left and try to save everything to the cache or a custom record and resume it when the script starts again. That sounds like a terrible thing to have to do however.
0