Discussions
Here are some examples to get your creative juices flowing.
"Did I pay vendor John Doe last month?"
"Take me to my largest sales order for this month."
"What invoices haven't been paid yet?"
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?