Home > New Features and Improvements from Previous Versions > AvePoint Cloud Backup for Salesforce® October 2024
Export to PDFRelease Date for the Commercial Environment: October 13, 2024
Release Date for the U.S. Government Environment: October 20, 2024
Private Preview: Cloud Backup for Salesforce® now supports integration with Tableau and Power BI. In Data service, you can create data services to connect your Salesforce backup data to these platforms for further analysis.
You can now select specific related records for restore or sandbox seeding, instead of restoring or seeding all parent or child records.
Pre-restore or pre-seeding can now be run, allowing you to review job recommendations in the Job monitor before the actual restore or sandbox seeding. This enables you to adjust settings as needed, ensuring a smoother and error-free process.
Enhanced permission control now allows administrators to define the object scope for users to run the Discover job in Settings > Account management.
On the Job details page, you can now run a Compare job on records based on Discover job results, rather than just viewing and restoring them.
In Settings > General, you can now configure the External ID of objects within the organization as the unique identifier in the restore process if the corresponding Record ID does not exist in the destination organization.
You can now configure whether data cleanup requires administrator approval for each organization in Settings > General. Once enabled, the approval process cannot be disabled.
To back up a large number of records (more than 2000 by default), you can choose to use the Bulk API 2.0 for better performance. For more information and to enable this feature, contact the AvePoint support team.
When you click the Record ID to view job details in the Discover job results, the Related records tab has been added to display child object records.
When creating a sandbox seeding template to seed specific objects to sandbox organizations, you can choose to Use the original user information in the destination organization. Once enabled, users in the destination organization will be generated based on the source organization's user data during the initial template setup.
When restoring metadata to another organization, you can choose to Apply the namespace of the destination organization to the restored metadata. Once enabled, the restore process will initially ignore the metadata namespace. After the restore, the namespace of the destination organization will automatically apply to the restored metadata.