We’ve updated our Salesforce integration, fixed several bugs, and added new features to the connector! You can now:
Update the most recent record, when dealing with duplicates.
This was one of our most requested features! It’s especially important when dealing with duplicate records in Salesforce. Before, if the connector ran into duplicate records, you could only create a new record (and therefore keep adding dupes). Now, you can simply pick the most recent record found and update that one.
Update multiple records using repeatable sections.
FormAssembly has always been able to create multiple records in Salesforce using repeated sections, but now you can also update ’em.
Implement smarter handling of update-or-create scenarios.
You can set a connector to update a Salesforce record, or create a record if there isn’t an existing record to update. So, you’ll use the same field mapping for both creating and updating.
But sometimes the information needed to create a record isn’t the same as the info needed to update a record — which means the field mapping might fail when trying to update, because Salesforce won’t let FormAssembly update the field (the field is read-only after it’s created).
Now, however, the Salesforce Connector is smart enough to figure out which field can be updated and which cannot. In most cases, it’ll be easier and faster to set up a connector!
Access the latest objects and fields in Salesforce.
Until now, the most recent Salesforce changes weren’t available in FormAssembly because we were using an older version of the API. We’re now caught up, which means you can now access various Chatter and feed-related objects. For more details, see the Salesforce Release Notes.
We’ve also improved the UI a bit:
- Invalid or obsolete field mappings are highlighted. If you set up a connector and then make changes to the form, any invalid and outdated field mappings will be highlighted in red, and new fields will be in green.
Here, for example, we’ve deleted the “First Name” field:
Screenshot of a Field Mapping in the Salesforce Connector
- The Connector Log shows which object is responsible for each log entry. For example, if an error is triggered by object 1.1, you’ll see “1.1” at the beginning of the log entry.