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.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for 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. Join us
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. Join us
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