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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week! You only have until tomorrow, November 14, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Workflows misbehave due to lack of record joins
When workflows are running that rely on record joins, such as where there is criteria that looks at a field value of a parent record - in some cases these joins aren't available so the workflows misbehave, or rather the behave differently depending on the context.
For example, if a script is using record.submitFields() to update a record, which triggers some Before Record Submit workflow execution, the joins are not available, the values are always null.
However, if the UI is updating a record, the joins are available and the workflow behaves as expected.
Within the workflow, is it possible to ensure the joins are always loaded/usable - or to easily detect the joins have not been loaded and to abort?
0