Discussions
Check out Oracle NetSuite upcoming events and conferences here
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.
Don't miss out on our Pop Quiz You only have until September 13, 2024, 3 PM ET to comment your answers and earn rewards! Click here for more details.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Get ready to take on exciting new challenges and become the next SuiteMaster of the Month!
Join the largest gathering of the NetSuite Community at SuiteWorld in Las Vegas, September 9-12! Discover cutting-edge innovations, attend insightful sessions, network with industry leaders, and elevate your business to new heights. Register here!
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