CopyStorm/Restore 5.31.4

May 15, 2015

This release contains feature enhancements and bug fixes.

Recognize Non-Insertable and Non-Updateable Tables

Previous CopyStorm/Restore versions would attempt to insert/update a Salesforce table even if the Salesforce meta data indicated that the table was not insertable/updateable. This problem occurred when attempting to restore selective system tables (that are rarely restored because they are initialized when a Sandbox is created). This version automatically skips operations that the Salesforce meta data says are not allowed and will not allow a user to select an unsupported operation via the GUI.

Fix Restore Problem with the Event Table

Previous CopyStorm/Restore versions did not know about special handling of StartDateTime, ActivityDate, and ActivityDateTime on the Event table. Basically, if StartDateTime has a non-null value then special handling must happen for ActivityDate and ActivityDateTime.

Prompt User to Save Changes

If any changes are made to a CopyStorm/Restore configuration the application will now prompt to save the changes when the application is closing.

Add Annotations to Various Table Groups

In previous versions it was difficult to distinquish between tables that are great restore candidates and tables that are populated automatically as part of a sandbox refresh. This CopyStorm version annotates tables that are not commonly restored as top level tables with a small superscript on table names.

Add Support for Custom Table Groups

This release exposes the Restore Set Editor table groups as a configuration file where a site can add their own groups or supplement the groups supplied by CopyStorm/Restore. This can be useful in isolating tables associated with packages (example: all Conga/Composer tables). See the CopyStorm
advanced configuration section on the CAPSTORM learning site.