GRAX Documentation

The GRAX Documentation Hub

Welcome to the GRAX Documentation hub. You'll find comprehensive guides and walkthroughs to help you start working with GRAX as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Best Practices

πŸ“˜

GRAX TIP

To learn more about getting started with GRAX Backup: https://documentation.grax.io/docs/getting-started-with-grax-backup

GRAX Backup: Best Practices & Pro Tips

  • Running a large job & need to make sure it’s running smoothly? Configure workflow alerts for a process that has been running for greater than X hours/days to serve as a reminder to check in on it.
  • Naming a process is optional but doing so makes it easier to remember what objects are being backed up as part of the process.
  • If you run into SFDC-imposed limits, you always have the flexibility to break down jobs based on date
  • Toggling β€˜on’ Single Object Backup allows you to select different date values, not just System Modstamp

πŸ“˜

GRAX TIP

To learn more about getting started with GRAX Restore: https://documentation.grax.io/docs/getting-started-with-grax-restore

GRAX Restore: Best Practices & Pro Tips

  • 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

πŸ“˜

GRAX TIP

To learn more about getting started with GRAX Archive: https://documentation.grax.io/docs/getting-started-with-grax-archive

GRAX Archive: Best Practices & Pro Tips

  • Stagger archive jobs that involve the same objects to avoid record locking
  • Use exceptions to prevent setting off triggers, custom code, flows, & processes when deletes are done by a designated GRAX user
  • Always have a unique external ID on objects that are being archived (aside from the lookup relationship fields) to prevent orphans
  • Certain Salesforce objects cannot be archived and can block your process if selected
  • We do not recommend archiving data for 3rd party package customizations/objects unless fully validated
  • Ensure you understand all Salesforce considerations for relationships before running an archive job
  • When running an initial archive job or large archive jobs, we recommend understanding the other DML operations that may be scheduled

Updated 26 days ago

Best Practices


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.