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
browser xml error on executing script via workflow
I am trying to setup a button on documents to print to our label printer.
Using a revised version of clintm@cfh.ca's instructions (revised because our office uses Chrome not IE and his instructions use the activeX commands) I created a button on the required transactions. This button works fine however these custom buttons only appear when in edit mode and it would be preferable to have them in view as well.
So I created a workflow that adds a button, when the button is clicked it moves the workflow to the next state where the custom action is executed on entry (this executes the same function, script and library script as the custom button) before returning to the initial state (after submit or blank).
0