CopyStorm/Restore 7.37.4
Release Date: 30-Sep-2016
This is minor feature and bug fix release.
Boost the Speed of Tracking Database Operations
An improvement in how tracking database descriptors are cached will often given a dramatic bump in tracker database related performance — especially for smaller restores.
Add a Feature that Will Estimate the Size a Restore in Megabytes
The CopyStorm/Restore “Restore” tab contains a new button for estimating the size of the restore in megabytes.
Always Store Passwords in an Encrypted Format
CopyStorm/Restore now always stores passwords in an encrypted form even when a CopyStorm/Restore configuration file is saved in XML format. If a user wants to store a plain-text password, a configuration file can be modified manually in an editor. Any existing configuration files are uneffected and will continue to work.
Update Graphics Components to Adapt to 4K Displays
A number of the graphics components were displaying too small on 4K monitors. Graphics components now adjust to 4K and larger displays.
Fix an OpportunityTeamMember Sorting Bug
With larger Opportunity Teams, the code would send a query longer than 20,000 characters to Salesforce (the max is 20,000).
Fix a Partner Sorting Bug
The code that sorts Partner records was assuming that all partners had a non-null role. If a partner record had a null record then the code would generated a null pointer exception.
Add Support for Clearing Tracker Database Exceptions
When constructing a restore set it is useful to clear exceptions that have already been resolved. The Exception Viewer dialog not supports this feature.
Silently Skip Partner Records that Are Created as a Side-Effect
When a Partner record is created on an Account or Opportunity Salesforce create related Partner records on the associated Account. Previous versions of CopyStorm/Restore did not know about all cases and would unnecessarily attempt to create Partner records and generated exceptions. Though this behavior did not effect the restore, it did put unnecesary exceptions into the tracker database.
Fix a Bug that Prevented Partner Records from being Restored
Previously, if a Partner record reference an Account or Opportunity that was not part of the restore set BUT was already in the target Salesforce, CopyStorm/Restore would refuse to restore the record and record an exception.
Prefix Errors from the Salesforce API with [Salesforce API]
When a validation rule or APEX code caused an INSERT or UPDATE to fail it could be difficult that the error message came from Salesforce. In this version, errors from INSERT/UPDATE operations are prefixed with the string [Salesforce API].
Fix a Bug Restoring OpportunitySplits
Previous versions generate a lot of unnecessary exceptions when restoring Opportunity Splits. The core issue was a automatic side effects that happen when Opportunity Splits are enabled for a Salesforce Organization and an Opportunity is first created. The current CopyStorm/Restore now knows about Salesforce’s peculiar behavior and adjusts accordingly.
Always Restore Attachments after All Other Tables
Though polymorphic tables were restored at the end in previous versions, Attachments were restore too early (before Tasks). Attachments are now restored after all other table types.
Improve the Exception Message When a Salesforce Insert or Update Fails
The “1-line” exception message header now contains the text of the error returned from Salesforce on an insert or update failure.
Record the Reason for a Salesforce Insert or Update Failure with Each Record
When a record is skipped because of a Salesforce insert or update failure, the reason is now stored with the appropriate record. This means that clicking on the “Skipped” status in the Tracker Database Viewer will now display the failure reason on a per record basis.
Refactor the Skipped Record Viewer to Support Many New Features
A refactored Skipped Record Viewer supports classification of skipped reaons, searching/filtering, and the removal of reasons that are no longer of interest. These features are most useful for Salesforce migration projects when the “data or rule were not quite right” in a first pass and a restore needs to be attempted again.