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 $300 - 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
Nasty reporting bug with quantity
Hi -
We just noticed a really nasty reporting bug. When running a report on POs, the quantity field inconsistently reports a negative quantity for some items - not all items, but only some. This consequently totally FUBARs some of our critical reports regarding the company's anticipated cash flow.
I spoke to a service rep, but the guy barely spoke english and it took him 40 minutes to understand exactly what the problem was, so I don't have too much faith in the bug report getting dealt with efficiently - in fact, the issue (100300) has already been closed but the problem still exists, so I'm not sure where to go next.
0