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
Bug in SS nlobjResponse SuiteScript Server Pages Corrupts Inline Image Output
We are converting some external SuiteLets to the new SuiteScript Server pages. The architecture is quite nice. We submitted case #2027267 about output to the client that is corrupt.
Basically, we are streaming an image file that uses <img src='data:image/png;base64,...' It works perfect in Suitelets. We are finding that right after we output the data, NetSuite is removing the element that says 'data: in the stream and it now looks like img src='image/png;base64,...'
I am wondering if others are seeing some weird things with the nlobjResponse object messing up information in ths response.write method call.
0