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
Rev Rec Schedules - line order changed
Last Friday we noticed a glitch that appears to be impacting most of our Revenue Recognition Schedules. In the past, the schedule lines have always been in chronological order. Now, we're finding that some months are reversed (e.g. Aug and Sep), or, the entire list is out of sequence. This is widespread throughout our production account but has not affected Sandbox.
This is challenging for Finance as there are a number of projects right now which require viewing / editing / copying RR Schedules, and this makes it more difficult.
If you are experiencing the same problem, please submit a case and ask to have it linked to Defect #219303, an S-3.
0