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.
Please note that on Saturday, April 18, 2026, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 15 minutes. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
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