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
Statement Advanced PDF template no longer works - 'record' is undefined
Since the 2014.2 update Individual Statements will no longer print with a customised template.
When trying to print many errors are shown on the screen saying that 'record is undefined'. How can 'record' be undefined??
If you print with the system default template it is fine, and the system default uses record to source all data in the template.
I confirmed this error by customising the default template (which copies the template markup) and saving it without making any changes. Printing using this newly created template also fails with the same error.
Is anyone else experiencing this? Has anyone else found a workaround?
0