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
MAsked credit cards ...... again
The ability to confirm the numbers of a customers stored CCs is Extremely Important for our daily operations.
So after we suddenly found them masked without so much as a warning... we researched what we had to do ... and over the course of 5 business days were able to obtain, sign, and return the "Credit card authorization" form which then unmasked the credit card numbers through-out our netsuite system.
After that initial inconvenience had been resolved (while we endured 5 business days of chaos)
it has been done to us yet again .. and again without so much as a warning.
This time, we have logged 3 calls to our sales rep about the issue (the same one that handled it the first time) ,
0