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
Set field value to {tranid} after submit
We use a custom field that stores a common ID number across all elements of a transaction beginning with the sales order. This ID number is just a copy of the sales order ID number with the "PRFM" abbreviation (we call our sales orders proformas...) replaced with "CTG". Initially this was done by creating a sales order, saving it so that it's ID number would be generated and then opening it again and literally copying and pasting the number into our custom ID field and saving again. This is obviously not ideal.
I have now managed to set up a workflow that "on update" uses a "set field value" with the formula: REPLACE({tranid}, 'PRFM', 'CTG'}, but this still requires the sales order to be edited and saved again to seed the custom ID field so that it will carry through to the subsequent forms. I haven't figured out a way to do this "on create" without simply getting the value "To Be Generated" even if I use "set field value" after submit. Does anyone know of a way to pull the {tranid}, after it is generated, to our custom field without having