CopyStorm/Restore 7.37.6

Release Date: 11-Mar-2017

This is minor feature and bug fix release.

Restore Salesforce Meta Data

This release includes a preview of a feature for restoring Salesforce Meta Data. It is labeled as a Preview because not all meta data types are supported — though we think you will find that nearly all of the important meta data types are already in place. For details see this article.

Fix a Bug Mapping Users for a Migration

When a migration map contained a mapping from a backup user to an inactive target Salesforce user the mapping code was ignoring the mapping. The same was true for Group and Profile definitions (just unusual to encounter). This problem would rarely occur outside of the context of a migration from a Salesforce instance to an unrelated Salesforce instance.

Restore Inactive Users to Non-Audit Fields

Inactive User Ids cannot be used in audit fields for an insert/update operation without elevated permissions. Previous versions of CopyStorm/Restore were treating non-audit field with UserIds that same as audit field. This error has been corrected.

Fix a Mapping Bug with Long External Ids

When the average length of an external id was 16 or more and there were 1000 or more to map a query too long for Salesforce to handle was generated.

Unreferenced By Reference Table Not Always Removed

When a parent table was removed from a restore set, all related “by reference” tables were not always removed.

Automatically Exclude Converted Lead Records

Salesforce does not support restoring converted leads. Previous versions would report an exception on each converted lead; now they are simply ignored and never selected as restore candidates.

Restore NULL Value Fields

Previous versions would not restore the value of a field if the value in the backup was NULL.

Upgrade Performance for Multi-Column Record Matching

The form of the SOQL query sent to Salesforce when record matching by multiple columns has changed to allow the Salesforces Oracle back-end a better chance of generating an efficient query plan. The only thing a customer may notice is better performance on multi-column record matching. We discovered the Salesforce performance issue in a case where multi-column matching was being used on a table with 22 million records (on tables with 100,000s of records the performance issue would not be noticed because latency with Salesforce is the overriding performance metric).

Fix a NPE Bug When Enabling Workflows

CopyStorm/Restore was throwing a NPE when a workflow in the list of flows to disable/enable did not exist in the target Salesforce.