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.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for 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. Join us
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. Join us
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
Tagged:
0