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.
Custom Field Does Not Appear on NEW Records, But Does on Existing Ones
We recently added two new custom fields to our account, Expected Release Date and Release Date Modified On:
When a user chooses a date for the Expected Release Date field, the Release Date Modified On field automatically gets its value set to the current date (this is controlled via a workflow), like so:
This all works as expected for existing records in the system. However, when making a NEW record, the Release Date Modified On field does not appear (it DOES appear after the record has been saved, however):
What would cause this to happen? I have look at both the custom field's definition and the record type's form design, and nothing is telling it NOT to appear. The field's definition instructs it to appear on the