I have a workflow that is triggered by a field change, and updates a long text field with some new data (and then appends the previous contents of the field):
This will trigger and perform correctly if a user sets the 'Stop' field to ticked, and adds their details to the Credit Limit History field as expected.
I have a separate monthly process that ticks the 'Stop' field for a range of Customers via Mass Update. It also ticks another field to send notification emails (See below)
The Workflow above is set to all contexts and all Triggers, but is not triggered when the Stop field is updated via Mass Update.
- Is there any way to get this workflow to be triggered when the field is updated via Mass Update?
I have another workflow (also running on all contexts and triggers) that is activated by the Monthly stop process when the 'send email' box is ticked. This performs a number of actions (sends an email, sets a date field to the date it was sent etc).
I have tried to add in a Workflow step to update the Credit Limit History field (similar to above) - but it kept setting the field to 'Invalid Expression'.
After testing I have proved I can use a workflow step similar to the above to set the field to some specific text and this will work OK. But whenever I try to reference another Customer field (e.g. the custom date field or the existing text in the Credit Limit History field) then it returns this 'Invalid Expression' error.
- I assume this is something relating to the context under which the mass update is running - and it doesn't have access to the current customer fields in order to process the formula?
- Is there any way to overcome this?