The Update record action allows you to update any record in Salesforce at any point in a flow. This action supports the majority of standard, special and custom objects associated with the connected Salesforce organisation.
Configuring the node
Select an object and a record ID to update. If the ID format is invalid or the record does not exist, the experience/s will fail.
Apply assignment rules
If you’re using Salesforce assignment rules to automatically assign owners to updated Leads or Cases, you can define how you want your rules to process by selecting one of the assignment rules options.
- Select Use default Salesforce settings to activate the rule when a record is updated, based on the default Salesforce value of
TRUE - Select Reassign using Salesforce active assignment rules to trigger the rules when a record is updated. This is the same behaviour as the current default settings, but guarantees that the rule triggers if Salesforce change their default value at a future date.
- Select Do not trigger assignment rules to prevent assignment rules from being run when a record is updated. This sets the value to
FALSE.
Update record
Select the fields you would like to update. To add more fields, click the ‘add field’ button. To remove any field, click the 3-dots menu to the right of the row and click ‘delete’. You can update as many fields as you like with either static values or merge fields from previous nodes in the flow.
When an experience runs in the Lumary Engagement Console, the flow will update only one record with the fields as configured in the node below. The update record node does not support an ‘upsert’ action.
If a value is left blank it will not be updated on the record, i.e. you cannot delete a value.
Outcome paths
Success path: the experience will continue down this path if the record is successfully updated.
Failed: the experience receives an unexpected failure from Salesforce. If this outcome path is switched OFF, the experience will end and be marked as ‘failed’ in History. If this path is switched ON the experience will continue down that path to the next configured node.
The most likely reason for an experience failing to update the record is that a required field needs to be included or the format of the field value needs to be corrected. See below for the correct Salesforce formats to use when configuring the node.
Current known limitations & workarounds
The Lumary Engagement Console is regularly releasing updates and fixes for limitations where possible and appropriate. We will continue to update the list below as more capability becomes available.
| Limitation | Workaround (if applicable) |
| Field validation: the update node currently does not support visualising system values associated with any fields (for example, picklist values). This means you must enter exactly the correct values when entering the desired update value otherwise the experience will fail. |
The format of the fields used in configuring criteria will need to adhere to the SFDC API formats: |
| Attachments, files and rich media: We do not support adding attachments or images/videos to a record at this time. | |
| Polymorphic fields: Polymorphic fields, e.g. Owner (User, Group), are not currently supported and won't be available as a field from Salesforce. | |
|
Assignment rule behaviour: As this node does not set a value for the If you rely on assignment rules to route Leads or Cases after updates (e.g. if a record status changes and should trigger reassignment), this may not happen automatically. You may observe that records created are assigned as expected, but updates do not follow your assignment rules, potentially leaving them with stale or incorrect ownership. |
If you currently use assignment rules to handle the allocation of Leads or Cases, you may need to adjust your rules to avoid incorrect assignment. Salesforce flows or apex triggers may need adjustment to handle the assignment logic correctly when the auto-assign value is set to |