Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
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).