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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
No Limits. Just possibilities.
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 2026.1 Release Notes - This document summarizes the changes to NetSuite between 2026.1 and the previous release.

Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Try Intelligent Payment Automation – Fee Free For Your First Month

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.

Map/Reduce Unexpected Type Conversions

edited Dec 2, 2019 5:46PM in SuiteCloud / Customization 4 comments

I am building a very simple prototype Map/Reduce script just to get an idea of the data flow through each phase. I am seeing what I consider unexpected behaviour when passing data from the map phase to the reduce phase. It seems that no matter what type of data is written to the context during map, it will always come out as Strings during reduce.

Consider the following code (the module define and return object have been removed for brevity, but they are correct):

/**   * The input data is just a list of Strings.    */  function getInputData() {      return ["a", "string", "array", "for", "testing", "data"];  }    /**   * The map phase gets the length of each String from the input data and   * writes it back to the context in three different formats: Number, String,   * Object   */  function map(context) {      log.debug(arguments.callee.name, context);      context.write('numberData', context.value.length);      context.write('stringData', context.value.length.toString());      context.write('objectData', {'length' : context.value.length});  }    /**   * The reduce phase currently just logs what it receives   */  function reduce(context) {      log.debug(arguments.callee.name + ':' + context.key, context.values);  }    function summarize(summary) {      log.debug(arguments.callee.name, summary);  }

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders