Restoring data using GRAX is incredibly easy to do with a few clicks, but your Salesforce Admin/Team will need to prepare the environment to ensure all considerations are taken into account.
Use GRAX Restore to restore a record back into Salesforce from the last time it was backed up. Here are some of the different ways and places within the GRAX Salesforce app that you can call the GRAX Restore functionality:
Restore via Search Tab
Search & Restore
Granular Restore Using Custom Hierarchy
Search & filter your GRAX data, then choose to restore individual records or restore all.
Toggle ‘On’ for ‘Restoring Parent Record and Children,’ then choose the child objects within the hierarchy that you want restored.
Restore via Record Details Page
Embed a ‘Search/Restore’ component on the record details page to provide you the ability to search and restore.
Customize your restore options by clicking ‘Restore Options’ under the GRAX ‘Search’ tab and toggling the switches to:
Restoring Parent Records Only
Restore Parent Record Only
Restores Parent and All Child Records
Only Inserting Records
Restore will Insert Records Only
Restore Updates Records
Assign Record Owners
Assigns Records to Active Users Only
Assigns Records to Active and Inactive Users
To see the restore job status & details, check out the ‘Restore Logs’ tab, located under ‘Logs’.
- Click on the sub-tab search
- Select the Table or SFDC object you want to restore
- Select the Fields to be displayed
- Enter any Filter Criteria to limit returned results
- Click Retrieve
- Click Restore Options & toggle the Settings switches
- Use the Checkboxes & the Restore button to restore record(s) or use Quick Restore for any search result
- A pop-up with the Restore Job ID will appear that you can use to track your restore job under Logs
- Be sure to validate all custom apex code/triggers present on any objects that you will be restoring
- Make sure any user needing to use restore functionality has the proper permissions and access to data
- Any changes to required fields could cause issues if incoming restored data does not meet criteria
- We do not recommend restoring data for 3rd party package customizations/objects unless fully validated
- GRAX restore will run as the integration user as specified within setup and configuration, meaning that this user will need to be set with the proper permissions/access
- Validation/triggers can block data inserts sometimes, but you can work around this by setting the user as exempt from these rules or by temporarily disabling the validation/triggers
- We highly recommend that GRAX is integrated into your existing change management process
- For complex SFDC environments, we recommend setting up policies and procedures specifically for the restore process
Now that you’ve mastered the basics, you can keep expanding your knowledge & mastery with our Knowledge Base:
Updated 6 months ago