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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
(Updated) SuiteScript numbers written to string converted to float silently.
This seems like a bug in the unary plus implementation. Have there been any recent patches to the scripting back-end in SuiteScript 2.1?
We have a map/reduce script that processes a queue of custom records (populated via CSV files from third-party logistics) and processes item fulfillments against orders. This script uses JavaScript unary plus to convert the imported line ID from string (because some 3PLs zero-pad it, some don't):
var numericLineSeq = +lineitem['custrecord_cm_ifqin_if_lineseq'];
Starting sometime on 9 Dec 2023, we show that the line IDs were being calculated as floats instead of integers, even though the incoming data format had not changed.
0