The Create record action allows you to create 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 the object you want to create the record on from the Object drop-down list.
Apply assignment rules
If you’re using Salesforce assignment rules to automatically assign owners to new 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 created, based on the default Salesforce value of
TRUE - Select Reassign using Salesforce active assignment rules to trigger the rules when a record is created. 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 created. This sets the value to
FALSE.
Create record
Select the fields you would like to be created. 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.
Required fields are shown in the dropdown list with an asterisk (*). Confirm which fields are required for object creation in your SFDC org and configure as required, as the record may not be created, and the experience will fail.
When an experience runs in the 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 created.
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 create the record is that a required field is not 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
Lumary 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 creating or 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. |