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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Is nlapiEncrypt really SHA-1?
The NetSuite documentation says nlapiEncrypt performs a SHA-1 hash, however, when using nlapiEncrypt to hash a field value, I get a different value then what I would get using a online hash generator.
Example (hashing "1234"):
[INDENT]nlapiEncrypt gives me fcffee3dcb2083ed4da3f12e9422b2d3854b6a6a
www.fileformat.info/tool/hash.htm gives me 7110eda4d09e062aa5e4a390b0a572ac0d2c0220[/INDENT]
Am I losing my mind? Is nlapiEncrypt encoding it after the hash?
Need Help!
Thanks in advance!
0