Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Added (Backup)
Download functionality in metadata viewer
Download All Versions button for Record Versions page with CSV export
Enhanced single version download capabilities with improved graph CSV functionality
Removed (GRAX Insights)
Removed Service, Sales, and Marketing tabs in favor of continued focus on SFDC Admins
Add "To" and "From" addresses in EmailMessage viewer header
GRAX publishes two sets of release notes. One set is related to changes within the GRAX Managed Package, while the other is related to feature changes in the GRAX backend application. See the table below for more information about available release notes.
Release notes for Managed Package versions prior to 3.97 have been removed to ensure the relevance of the following list.
November 2024
October 2024
September 2024
August 2024
June 2025
May 2025
April 2025
March 2025
February 2025
January 2025
4.00
June 2023
3.99
December 2022
3.98
October 2022
3.97
July 2022
December 2024
Show per-object storage
Show Salesforce API version
Render HTML links inside EmailMessage bodies
Add ManageUsers permission to auto configuration to support monitoring storage limits
Add a button to search for a delete event from a deleted record
Allow read-only access to archives in "disconnected" mode
Improve size estimations for EmailMessage archives
Improve sync of EmailMessage replies after archives
Show activity expiration date
Add ability to purge all records from an archive activity
Show banner about initiate safety limits on first restore or seed operation
Add a new graph that shows data created and deleted or archived per day or month
Fully retired legacy indexed search
GRAX is retiring the Full Metadata Backup functionality in favor of the newly available Incremental Metadata Backup functionality. Full Metadata Backups will be retired on March 31, 2025.
GRAX has historically saved a copy of all metadata files separately as part of each metadata backup. While this design initially made working with a single instance of the backup easier, it also resulted in duplicate items taking up considerable storage space and can make changes in metadata difficult to find.
To resolve this issue, we've created a Salesforce Metadata UI (Settings > Diagnostics and Tools > Salesforce Metadata) and introduced our Incremental Metadata Backups functionality.
All of your new/changed Metadata will continue captured by GRAX, but as of March 31, 2025, unchanged files will no longer be backed up each time Metadata Backup runs. Starting in April 2025, GRAX will automatically remove duplicate metadata backups to help free up storage space. No action is required on your part.
This retirement does not impact the Metadata Backup Interval settings (Settings > General Settings > Metadata Backup Interval).
GRAX will retire Full Metadata Backups on March 31, 2025.
If you have questions or need more information, .
Data lake object picker support multiple objects
Added "Record Files" API for listing files and viewing their contents (docs)
Platform is now invite only. Upon purchasing GRAX with platform support, GRAX will send an invite email to you.
Upcoming Update to How SOQL Queries Are Processed for Auto-Archiving.
GRAX is retiring the Full Query functionality in favor of the newer, faster Query WHERE capability.
October 31st, 2025: All archives in GRAX sandbox environments will be transitioned to Query WHERE.
November 14th, 2025: All archives in GRAX production environments will be transitioned to Query WHERE.
GRAX has made significant improvements to optimize archive performance. Query WHERE provides several key benefits:
Automatically determines the optimal batch size
Delivers faster archive performance
Reduces timeout errors
You’ll continue archiving the same records as before — just faster and more efficiently.
Our team will handle the transition from Full Query to Query WHERE archives for you. No action is required on your part.
Yes, but please note that adding a LIMIT may reduce performance, as Query WHERE automatically adjusts batch size based on system conditions.
If you have any questions or would like more details, please open a support ticket with our team.
Soft delete recurring archives
Archive from search with relative dates
Global search IN operator
Give feedback in the app
Delete anomaly dashboard GA
Insights dashboards GA
Pause or un-pause all data lake objects
Support Proof Key for Code Exchange (PKCE) Extension for Salesforce auth
Added (Application)
Auto-fix for missing Integration User permissions
Enhanced permission set management with proactive correction of access issues
Added (Archive)
Archive record count details with estimated values per object over specific timeframes
Added (Data Lake)
Data Lake v2 configuration improvements with "Add New Objects" functionality
Field inclusion/exclusion capabilities for new and existing objects
Simplified object management with pause/resume functionality
New toggles were added:
Hide Show Record
Hide Show in GRAX
Hide Restore Button
Use iFrame (Faster Loading)
The LWC Data Viewer was updated to allow for control over the levels of related records that are shown in the related list. This new control is shown above, named "Child Level."
The LWC Data Viewer now has an option to use iFrame for faster loading and improved appearance. To use this new iFrame feature, it requires adding a Trusted URLs for GRAX in the Salesforce org. If you do not add the trusted site, the new iFrame toggle in the LWC settings does not allow embedding the iFrame. To be sure users are aware of this, there is a new Warning to add the Trusted URLs if one does not exist for the GRAX Application.
Enable Auto Backup is set to True for all new installations. The warning for new scheduled jobs when Enable Auto Backup is True has been removed.
The help link has been updated to navigate directly to the Support page on the GRAX documentation site.
GRAX has now released Global Search, a search tool that allows the user to find data across all of their Salesforce data backed up by GRAX. Users can filter based on system timestamp fields, record status, and even field values to discover the data they need. This technology is based natively on the underlying GRAX data format and requires no upfront indexing time besides backups themselves. All data and fields backed up by GRAX are available without additional configuration or cost.
Indexed Search, by nature, duplicated a significant portion of customer datasets into the application database. This had a number of negative impacts:
Customer databases, previously only for application metadata, grew to be very large and required significant maintenance, resources, and budget.
Indexing Salesforce records into Postgres is many times more expensive than writing that same data to S3, often doubling the TCO of GRAX.
Searching records requires forethought and configuration, as only objects that were indexed were searchable.
Search indexing ran after backups completed, meaning data was not searchable until hours after it was backed up.
New environments and GRAX applications do not have Indexed Search enabled. Existing users of indexed search are being contacted by the GRAX team to discuss a migration to Global Search and the expected impact on a case-by-case basis. Any reported issues with Indexed Search after the given date are to be met with update requests.
Transition of Search functionality does not impact other primary features of the GRAX Application.
For users of Indexed Search who use their own infrastructure, the cost of that infrastructure is expected to reduce in proportion to the amount of data indexed and search traffic. Indexed data often outweighs the rest of the database significantly, so Postgres storage utilization and required resources are expected to drop significantly. Traffic to the DB is also expected to drop, although the scale of this change is highly dependent on org size, search users/traffic, version turnover rate, and other factors.
To avoid interruptions or issues with unsupported features, change over to Global Search as early as possible. For assistance, contact GRAX Support.
GRAX support for Indexed Search ends on September 30, 2023.
If you have questions or need more information, .
GRAX is ending support for "GRAX Embedded" and the code repository at https://github.com/graxinc/grax-salesforce-embedded.
This feature empowers customers internal Salesforce development team to build custom components that reuse GRAX data in Salesforce in ways that the official GRAX components can not support. It accomplished this by providing a GitHub repository of code that customers can "fork," change and deploy into their own Salesforce environment using "Salesforce Developer Experience" (sfdx) tools.
GRAX Embedded is a "first generation" version of reference code and deployment docs provided by GRAX. It is being retired and replaced by "second generation" solutions that offer major benefits in customization, security, and long term support by GRAX and Salesforce:
Additionally all customers currently using "GRAX Embedded" can continue to use and deploy their fork of the GRAX-provided repository with no changes required.
Finally GRAX is continuing its support for first-party and fully supported ways to bring data into SFDC:
GRAX Public API
GRAX Managed Package Components
IFRAME components delivered via auto-update
LWC components delivered via managed package updates
If you need support with a maintaining or changing your custom build, please talk to GRAX Sales to discuss options.
GRAX provides many "first party" components to bring GRAX data back into Salesforce like the Search, Related Records, Restore and Email Viewer components. If these components are not currently meeting your needs, we encourage you to get in touch and let us know what you're doing. Our components are constantly improving based on your feedback and feature requests.
But it is inevitable that some use cases can only be satisfied by building new customer-specific components.
In August 2022, GRAX open-sourced some of our package and component code to help customers build their own components. Since then we have found that the grax-salesforce-embedded project mandates development, deployment, and coding practices that don't match many customers internal Salesforce development processes.
Going forward, this customization is best accomplished by GRAX providing a Public API and other modern resources that makes it easy for your own Salesforce development team to access GRAX data in any tools you build however you build them.
If you are in the vast majority of customers enjoying the GRAX Application or GRAX Managed Package directly to bring GRAX data into Salesforce, this does not affect you.
For customers that are using grax-salesforce-embedded, no action is necessary as you will always be able to continue using your checkout or fork of grax-salesforce-embedded and your deployment of it. The change is that GRAX will archive the GitHub repository and will no longer offer support for any development questions.
We recommend that you "fork" grax-salesforce-embedded to a repository that you maintain, then review any components you have in use and port them over to your standard internal Salesforce development projects and processes.
This is best accomplished by looking at the GRAX Public API and using that directly to bring data into your Lightning Web Components. You may also accomplish this by copying components from the grax-salesforce-embedded repository into your other Salesforce projects.
End Of Life for grax-salesforce-embedded is June 30, 2024.
If you have questions or need more information, .
All GRAX Hosted applications will be moved from the *.secure.grax.io domain to the *.hosted.graxapp.com domain by August 31st, 2025. For example, https://example-name-01.secure.grax.io will become https://example-name-01.hosted.graxapp.com.
This change improves performance, reliability, and availability of GRAX Hosted applications. It reduces the risk of third-party outages affecting your GRAX service and improves our ability to prevent, respond to, and resolve service issues.
On August 31st, 2025, the *.secure.grax.io domain for GRAX Hosted applications will stop serving your application. The application will only be available at the new *.hosted.graxapp.com domain.
The GRAX Managed Package for Salesforce, any consumers of the GRAX API, and any end users who directly access the GRAX application will need to be updated to use the new domain names. The old domains will not be available after August 31st, 2025.
If your GRAX application currently is accessible at https://example-name-01.secure.grax.io, it will only be available at https://example-name-01.hosted.graxapp.com once moved.
We encourage you to reach out to GRAX Support to schedule a working session for prior to August 31st. During such a session, your applications can be cut over to the new domains and we can assist you in updating your package configurations.
If you have questions or need more information, .
Sync a single record when fields have changed but system modified timestamp has not
Backup metadata in an incremental format for storage reduction
Delete tracking dashboard
Activity data download field level security improvements
Global search field filters, relationships and operator improvements
Auto-purge safety improvements around live records
Data Lake includes fields with Parquet type based on Salesforce schema
Insights dashboard pilot
Scalar API Docs generated from spec at
Postman API docs removed at
Incidents affecting multiple customers will be detailed below. This list will include security, availability, and product issues (if such events should occur). Public incident documentation will be retained for 90 days from the Start Date of each incident.
Show record and file sizes in KiB and MiB
Improvements the flow for resetting Salesforce connection around sandbox refreshes
Automatically expire activities after 7 days of inactivity
Migrate archive activities to cloud storage, reducing cost and load on the database
Prioritize one-off archives over auto archives to reduce wait times
Prioritize EmailMessage archives as they make the most impact on storage reduction
Skip deleted objects when restoring
Disable automations before restoring in non-production orgs
Warn if seeding activity requires more storage than the sandbox has
Search date picker improvements
Allow actions for partial results from a cancelled search
Add tool to test notification emails
Add notification icon and dock to view notifications
Improve dialog of configuring object relationships for archive and purge
Allow custom batch size for restores to help with Salesforce limits
Change behavior of empty field overrides from creating the object with an empty value for the field to creating the object without the field. This enables restoring OrderItem with an outdated ListPrice
Add randomized option for seeding data anonymization
Randomize strings and textareas with lorem ipusm
Prioritize override settings over anonymization
Add button that links between seed and undo activities
Add ability to purge files
New Seeding API (docs)
N/A
N/A
N/A
Auto config custom domains
Secure access for GRAX support
Missing field permission tooling improvements
Auto backup dashboard improvements
Archive search templates
Add Salesforce usage to settings panel
Data Lake V2 GA
Record counts API
API docs improvements for search
Custom domains for seeding and reconnection
Filter activities based on user
GRAX support access auto expiration
Allow any user with GRAX_Console_Admin_User permission to reset a connection around sandbox refreshes
Display org name and ID in banner to help differentiate production and sandbox environments
Improve date picker component
Retiring full metadata backups in favor of optimized incremental metadata backups
Retiring the use of all Salesforce API versions prior to API v61
Add To and From address in EmailMessage viewer header
Using the GRAX Application in Salesforce Web Tabs
Most of our customers are already using OAuth tokens to connect GRAX to their Salesforce organizations; if you use OAuth tokens you will not be impacted by this change. If you are using Username, Password and Token credentials, you will simply need to to Salesforce. Once reconnected, GRAX will resume backing up your data where it left off.
In preparation for feature retirement, GRAX is adding alerts and warnings that you will need to reconnect. Simply visit the Settings page:
A green Connected status for the Salesforce settings indicates that you are connected with OAuth and will not be impacted
a yellow Connected with issues status indicates that there is a warning on your Salesforce connection and you will need to reconnect.
Rest assured, GRAX will also be in contact with affected customers and is here to help.
If you have questions or need more information, .
GRAX is committed to providing our customers with visibility into past and upcoming feature retirements. We go through an extensive process to analyze each feature and the value it brings to the broader customer base. While we strive to be transparent into these factors, please don't hesitate to reach out to us to discuss further. We would love to understand your use case and talk about higher value alternatives.
For each item in the table below, you can click to better understand:
Specific features being retired
Rationale
How this impacts you
Recommended workaround
Timing
GRAX retired Legacy Backup and Legacy Archive and ended support for these products on December 31, 2022.
GRAX backups are now accomplished through , and archives through . These officially supported solutions are now enjoyed by virtually all GRAX customers new and old and have proven themselves as the simplest, fastest, and safest way to backup and archive data.
On September 30, 2023, GRAX will "End Of Life" (EOL) the legacy products and begin to issue automatic updates that disable them. Auto Backup will be enabled automatically and Legacy Backup schedules will be ignored. Legacy Archive jobs will stop working until they are re-created as Auto Archive jobs.
Periodic notices will be sent to any customers on legacy products leading up to the EOL date and when the automatic updates go out.
Auto Backup and Auto Archive are the backup and archive solutions officially supported by GRAX.
To provide the best data safety guarantees to all customers, all usage of unsupported Legacy Backup and Legacy Archive must be migrated to the supported products.
The vast majority of all customers have already migrated. GRAX Support is proactively communicating and working with all remaining customers on the simple migration steps.
If you are in the vast majority of customers enjoying Auto Backup and Auto Archive, this does not affect you.
For customers that are using the unsupported legacy products, we recommend you follow the easy migration steps outlined in the Legacy Backup Retirement and Legacy Archive Retirement docs before Sept 30, 2023.
The EOL updates will not negatively impact your Salesforce data or GRAX backup data.
If Auto Backup is enabled automatically, it will continue to back up everything the Legacy Backup product was backing up. Additionally it will back up your entire Salesforce org with an hourly RPO (Recovery Point Objective), without configuration or selection of objects or schedule.
If Legacy Archive is disabled automatically, GRAX will stop deleting any Salesforce data until new Auto Archive jobs are configured.
To avoid interruptions or issues with unsupported features, migrate to Auto Backup and Auto Archive as early as possible. For assistance, .
End Of Life for Legacy Backup and Legacy Archive is Sept. 30, 2023.
If you have questions or need more information, .
September 30, 2023
September 30, 2023
SFDC Package Legacy Backups
December 31, 2022
SFDC Package Legacy Archives
December 31, 2022
SFDC Package Legacy Restore
December 31, 2022
GRAX OData / External Objects
March 1, 2022
GRAX Lightning Connect
March 1, 2022
Archive: Report Filter
March 1, 2022
Rolling Date Setting
March 1, 2022
Recreate and Edit
March 1, 2022
Apex-Based Time Machine Triggers
March 1, 2022
Metadata Backup (Legacy)
December 31, 2021
Formula Field Backup
December 31, 2021
API (Legacy)
December 31, 2021
Sandbox Restore
December 31, 2021
Apex Deletes for Archive Jobs
December 31, 2021
Audit Tab
July 1, 2021
February 1st, 2026
October 1st, 2025
August 31st, 2025
March 31, 2025
September 30, 2024
June 30, 2024
The GRAX Application hosts a Scalar-powered API explorer (at /scalar) already for users who have a GRAX deployment available. This API explorer has seen good user adoption and is the primary source of API documentation for existing GRAX users. To make the experience consistent for users who may not have access to their GRAX Application, we have chosen to unify our API documentation toolset and retire the old site.
The OpenAPI specification describing the GRAX API is shared between the documentation sites, so the contents of the documentation is not changing.
If you have used the public apidocs.grax.io site to explore the GRAX API, you will need to switch to api.grax.com for all future API exploration. This new site does not feature the integrated test/request functionality of the previous site, so interactive exploration should be done from the private Scalar pages on your own GRAX Application.
GRAX will retire apidocs.grax.io on September 30, 2024, at which point the site will no longer be available.
If you have questions or need more information, .
As of April 1st, 2026, Data Lake v1 will be removed entirely from the GRAX product
GRAX has invested substantial effort into optimizing Data Lake in many ways:
No missed writes
Shorter time from backup to Data Lake write
Faster backfills
Higher object concurrency
Lower resource utilization
Easier integration with downstream tools (Athena, Glue, DuckDB, etc.)
Improved field formats/types
Many of these improvements necessitated structural changes to the Data Lake product, as well as changes to the final Parquet structure and content. Pipelines ingesting and querying Data Lake v1 Parquet will require modification to properly ingest Data Lake v2.
Data Lake v1 currently provides a user and developer experience that is less reliable, slower, and higher cost than Data Lake v2. To ensure that all users get the most value out of their GRAX application, we've decided to establish a deadline for moving over.
If you or your business depends on Data Lake v1 for analytics or other forms of downstream usage, we recommend restructuring your project to use as soon as possible. You will not be able to add new objects after October 1st, and your pipeline will halt entirely after April 1st if still using Data Lake v1.
The key differences between Data Lake v1 and v2 are:
Reduced delay from data being added in GRAX to writing to Data Lake
Increased throughput when backfilling newly enabled objects and handling large volumes of changes
Improved writing intelligence to reliably keep objects up-to-date
System improvements to remove possibilities of missed writes observed in v1
Different path structure (v2 prefix, day=YYYY-MM-DD/hr=HH to batch=444444444)
Increased max file size (10 MB for v1 to 100 MB for v2)
Addition of source__modified, grax__idseq, and grax__restoredfrom fields
Addition of typed fields for non-string values
Removal of grax__added field
To enable Data Lake v2, navigate to the Data Lake section of your GRAX Application and click on Data Lake v2. You can then begin configuring the objects you want to write to Data Lake v2.
Once the initial backfill is complete and the object shows a Current status, you can safely disable it in Data Lake v1. Be sure to enable any processing rules and triggers for Data Lake v2 data before disabling Data Lake v1 to prevent any data loss.
Data previously written with Data Lake v1 is still usable and accessible during the switch to v2 and afterwards. Data Lake v2 will duplicate the data written with v1; the v1 files are safe to delete once they are no longer being used, and v2 has finished the initial backfilling process.
When deleting, be sure to only delete files under parquet/org=X/... in your bucket. Do not delete files in other parts of the bucket.
If you have questions or need more information, .