Spanning Backup for Salesforce Feature Retrospective
What’s New in Spanning Backup for Salesforce?
Here at Spanning, we’re constantly innovating to give you the best product experience possible. To do this, we release feature updates as soon as they are complete and tested instead of waiting for lengthy release windows or service packs. Sometimes, that means you might lose track of some of our latest and greatest changes. Let’s take a peek at some of the new capabilities we’ve added to Spanning Backup for Salesforce.
Bulk API v2
Under special circumstances, an environment might be so large or the rate of change so significant that the normal REST API capacity is not enough to keep up. In these rare cases, Spanning can utilize Bulk API methods instead to process large batches of data for backup.
- Bulk queries are metered separately and differently from REST queries
- Bulk queries are measured and limited by the hour
- The Bulk API v2 optimizations significantly reduce the total number of BULK API calls that Spanning requires to back up a large environment or delta
For more information on Spanning’s use of REST and BULK APIs, check out page 9 of our Admin Guide.
Improved Restore – Support for Repairing Lookup Relationships
When a record is deleted, like an Account for example, all its child records (Contacts, Opportunities, etc.) will also be deleted. This cascading deletion can be catastrophic for an organization. Fortunately, Spanning allows you to recover a deleted parent record and all its child records with a single restore. A relationship of this type is known in Salesforce as a “Master-Detail” relationship.
Sometimes, a Salesforce record may rely on information contained in other records. This information is usually obtained through what is known as a “Lookup Relationship.” Lookup relationships rely heavily on the Salesforce data model and the Salesforce Record ID to be used successfully. In the example below, Mr. Andrew K’s contact record has an ID of: 0035d00006QmhKuAAJ. This ID is vital to keep track of complex lookup relationships between records.
When a record is deleted, this relationship “breaks.” Not only will you have lost your contact, but you will have also potentially impacted other records that were relying on the information contained within.
This should be no problem with Spanning, right? Well, not exactly. When a record is restored via the API, a brand-new record ID is generated. So, Mr. Andrew K (0035d00006QmhKuAAJ) and Mr. Andrew K (0035d00006QmhKuAAX) are effectively two different people in your system. We share your frustration, and our engineering team has come up with an incredible solution to work around this problem. With just one click, you can now automatically update and repair any broken relationships in Salesforce to point to the newly restored record. This means that you can update every record that’s looking for Mr. Andrew K to reflect his new address: (0035d00006QmhKuAAX).
Summary of Changes for Relationship Restore
- “Restore Child Objects” is now “Restore Master-Detail Relationships.” The feature’s behavior remains unchanged.
- “Repair Lookup Relationships” enables the new functionality highlighted above.
For more information on relationships in Salesforce, I highly recommend you check out this resource.
Stay Tuned for More
We aren’t done yet! We’ve got more coming your way in 2021. We’re hard at work on features that will give you better control over your data and I look forward to sharing more updates regarding our data retention options in the future.