> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.7.4-monthly-release-notes.md). # Backup & Archive (v4.7.4) - Monthly Release Notes {% hint style="info" %} #### Release Details - Backup & Archive - v4.7.4 - June 11, 2026 This article is intended for Salesforce administrators, compliance officers, and IT teams responsible for managing Salesforce backups and data governance. **Release Type** * Monthly * Applies to Flosum-hosted and self-hosted **Prerequisites** * A registered and configured Flosum Cloud Apps tenant * Appropriate Flosum user permissions (SystemAdministrator or equivalent) {% endhint %} ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FPL2eaOdTi7VscAjFymsv%2FSummary2-Small-Icon.svg?alt=media\&token=a14ffcd6-66df-43ec-aafc-61364d19c7cd) Summary This article documents the monthly release for **Backup & Archive (v4.7.4)**. This release migrates the underlying file storage format from CSV to Parquet for faster operations, and adds **Configurable Fields** for Backup & Archive Salesforce Package components, a new **Data Hold** policy, enhanced ContentDocument support in Restore, the option to disable automation during archives, and support for nested SOQL subqueries in archive filters. ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Parquet File Format Migration from CSV **What Changed** Backup & Archive is migrating its underlying file storage format from CSV to Parquet. All core functionality, including Backup, Restore, Export, Search, and Archive, now reads and writes Parquet. The transition is gradual. Each organization within a tenant continues to read from its existing CSV files until its data is fully migrated, after which it automatically switches to Parquet. No action is required from administrators to start or manage the migration. **Why It Was Done** * **Faster operations.** Parquet's columnar storage lets the system read only the data it needs instead of scanning entire files, which speeds up Backup and Restore operations. * **Foundation for new features.** Parquet is a prerequisite for the new Configurable Fields capability, which cannot be built on the CSV format. **Availability & Rollout** This change is not immediately visible to customers after the release. Migration of existing data runs in the background, region by region. Customers begin benefiting from the new format only after their tenant's data is fully migrated. **What the User Will Notice** Once migration is complete for their tenant, users can expect: * Faster Backup and Restore operations. * No change to how they interact with the application, because the format switch is fully transparent. ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Configurable Fields **for Backup & Archive Salesforce Package** **What Changed** A new **Configurable Fields** setting has been added to the Backup & Archive Salesforce Package in the Salesforce org. It lets Salesforce administrators control which columns appear in the Backup & Archive Package components (**Backup History**, **Related Archives**, and **Time Machine**) on a per-object basis. Previously, these components displayed a fixed set of default columns (Record ID, Status, Name, Owner, Last Modified Date, Last Version) with no option to customize them. **How It Works** Administrators configure fields once in **Settings → Configurable Fields** by selecting an object and choosing which fields appear as columns across all Backup & Archive Package components for that object. A few rules apply: * **Record ID**, **Status**, and **Last Version** are fixed anchor columns that are always present, regardless of configuration. * Up to **5 additional fields** can be configured per object. * Objects without a custom configuration fall back to the default column set. * Once configured, the customization applies consistently across all three components (Backup History, Related Archives, and Time Machine) without requiring any code. **What the User Will Notice** * Backup History, Related Archives, and Time Machine tables display columns relevant to each specific object and team workflow, rather than generic defaults. * Administrators configure fields in one place, and the change is reflected immediately everywhere records are listed across the Backup & Archive Package. * Objects that have not yet been configured continue to display the standard default view, so there is no disruption during a gradual rollout. **Availability** To adopt the new version of the package, customers must remove the existing version and then install it in **B\&A Organization Settings**. The new package version uses a namespace, so old components must be removed first to avoid conflicts. Customers must also update the Connected App in **Global Settings**. Follow the instructions here: * [Enable Access to Flosum Backup & Archive Data](/global-settings/security/connected-apps/enable-access-to-flosum-backup-and-archive-data.md) At the **Edit and Configure the App** step, change the callback URL as follows: ``` Old Callback URL: https:///apex/userPoolCallbackUrl New Callback URL: https:///apex/FpPkB__userPoolCallbackUrl ``` * See step: [Callback URL](https://docs.flosum.com/global-settings/security/connected-apps/enable-access-to-flosum-backup-and-archive-data#callback-url) {% hint style="info" %} Configurable Fields becomes available to an organization only after its data has been fully migrated to Parquet format. Until migration is complete, this feature is not visible. {% endhint %} ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FgG2A2IRhOXknRFbAGToW%2FNew-Feature-Icon2-Small.svg?alt=media\&token=76ce09b1-243a-482d-97e4-ccc4cbc94d67) Data Hold **What Changed** A new **Hold Policy** tab has been added to **Organization Settings**. It lets administrators define rules that prevent specific backed-up and archived records from being permanently deleted, whether by an automated Retention Policy or a manual Purge operation. **How It Works** Administrators create a hold by navigating to **Organization Settings > Data Hold** and defining: * **Which objects the hold applies to**: Only objects that have already been backed up and archived are available, with a limit of up to 5 objects per org. * **Which records are protected**: using filters by Record ID or Record Name. Each hold can be activated or deactivated at any time. While a hold is active, no version of a matching record, including future versions, can be deleted by a Retention Policy or Purge. **What the User Will Notice** * A new Hold Policy tab is available in Organization Settings. * Records covered by an active hold are protected from deletion regardless of any Retention Policy rules or manual Purge actions. The hold always takes precedence. * Future versions of a held record are protected automatically, not just the versions that existed when the hold was created. {% hint style="info" %} #### Required Permission Access to Hold Policy, including creating, editing, and deleting holds, requires the SystemAdministrator role or a role with the Backup & Archive **App Settings** permission for the organization. Users without this permission cannot view or modify any hold configuration. See the following article for more details: * [Backup & Archive Permissions](/global-settings/user-management/flosum-cloud-app-permissions/backup-and-archive-permissions.md) {% endhint %} See the following article for detailed instructions on using Data Holds. * [Changing Data Hold Settings](/backup-and-archive/settings/organization-settings/changing-data-hold-settings.md) ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Enhanced ContentDocument Restore Processing **What Changed** Content Documents (files) can now be processed as child objects during Restore, using the same reliable approach already used in the Archive flow. This improvement enables: * Proper handling of parent-child relationships for Content Documents. * Consistent retrieval and processing of related file records. **What the User Will Notice** Existing functionality remains unchanged. Users who work with records that include attached files will benefit from more complete and consistent processing during Restore. ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Disable Automation During an Archive **What Changed** Archive Templates now include a configuration option to disable automation processes during archive execution. Previously available only in Restore templates, this setting now extends to Archive. **How It Works** Within the Archive Template settings, a new section lets users select which automation processes to disable when the template runs. The selected configuration is saved as part of the template and applied automatically at execution time. Disabling automation during an archive prevents processes, such as triggers, from running when records are deleted. See the following article for detailed instructions on disabling automations during an archive job. * [Creating a Templated Archive](/backup-and-archive/backup-and-archive/archives/creating-a-templated-archive.md#optional-disable-automation-processes) ### ![](https://3248471126-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKdKbUdYCYQswKDxgzTfY%2Fuploads%2FFX1KImFkBpbzYgGoBLl6%2FEnhance-Icon-Small.svg?alt=media\&token=6211adf4-19a2-458d-92fc-54b77a2a635a) Nested Query Filter for Archive **What Changed** Archive template filters now support nested SOQL queries (subqueries). Previously, subqueries passed validation but were not applied correctly during record count and job execution. **What the User Will Notice** * Subqueries defined in Archive template filters are now correctly applied at all stages: validation, count, and execution. * There are no changes to how filters are written or configured. **Example** ```sql SELECT Id FROM Order WHERE CreatedDate < LAST_N_MONTHS:24 AND Id NOT IN ( SELECT Order__c FROM Case WHERE Order__c != null ) ``` {% hint style="warning" %} Note that `LIMIT` is not supported in these subqueries. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/release-notes/backup-and-archive/monthly-releases/backup-and-archive-v4.7.4-monthly-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.