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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Workflow instance custom fields vs. standard custom fields
Workflow that sends an email when the value of the web address field is changed.
The workflow sends the email when I use a custom field on the customer record, with the following parameters:
Workflow Summary: Trigger on - Before Record Submit
State 1
Set Field Value, Condition: Old record: Web Address != Web Address, Trigger on Before Record Submit, Set "Send Email"=T
Send Email, Condition: "Send Email"=T, Trigger on After Record Submit
This works great. Now, if instead of using a custom field on the customer record, I use an instance custom field within the workflow, the email never gets triggered. The Send Email instance custom field is set to T in the first step, but then when it's evaluated for sending the email, it's evaluated to False.