24R3.1 Maintenance Releases

The items listed below were added in the 24R3.1 release cycle and contain maintenance items from the 24R3.1 release and future releases as they become available. These items consist of corrections and enhancements to existing functionality.

March 7, 2025

Release 24R3.1.3

Category Description
Workflow In some situations, address DCRS submitted from Vault CRM that resulted in a merge failed to update with the following error: Failed to update Vault CRM objects.
Vault CRM When Vault CRM is configured to not delete invalid addresses, on HCP accounts where addresses were invalidated with no state populated, some addresses were updated with null license information leading to sample ineligibility in CRM.

February 14, 2025

Release 24R3.1.2

Vault CRM Bridge Record Limit

To optimize Vault CRM Bridge jobs, the number of account records in each job will be limited to load data in smaller batches.

Records that have the oldest update time are exported first. The next time the bridge job runs, the next batch of records are exported, and so on.

The account record limit is applied by default to all Vault CRM bridge jobs.

  • Default record limit - 300,000 records
  • United States record limit - 150,0000 records

Parent HCO records

Parent HCOs are included in addition to the records that are exported.

For example, if the 150,000 record limit for a US Vault CRM bridge job is reached, the related parent HCOs are then added, so the job might upsert 200,000 account records to Vault CRM.

Target subscription updates

The record limit is automatically set on the target subscription configuration used by the Vault CRM bridge. Only the maximum number of records will be included in the export files.

The following target subscription settings will be ignored for Vault CRM bridge jobs:

  • Full Data Extract - The target subscription will always be run as a delta extract.
  • Apply Record Limit - Any limit defined for this setting for delta extracts will be overridden by the limits set for the Vault CRM bridge.

Job details

The target subscription job details page displays the Record Limit.

Vault CRM Bridge updates

The new Record Limit displays in the Network Data section on Multi-Country bridge configurations; it does not display on child bridge configurations.

Click the tooltip to review the record limit details.

Subsequent Vault CRM bridge jobs

When the record limit is reached, the records that are exported in the next scheduled (or manually run) Vault CRM bridge job are determined using one of these settings in the following order:

  1. Vault CRM bridge setting - The value defined for the Data Revision Value setting.
  2. Target subscription – The Delta Tag End on the last run job record is used to find the record to start with on the next job.
Impact to existing Vault CRM bridge jobs
Delta bridge jobs

If the target subscription is set to export a delta, the record limit will be enforced on existing jobs. When the limit is reached, the next scheduled (or manually run) job will start where the last bridge job left off.

Full bridge Jobs

The record limit will be enforced on target subscriptions that are set to export a full job. The Full Data Extract export setting is now ignored.

To start over and reload all the data:

  1. Instead of setting the target subscription to full export, set the Data Revision Value setting to 0 on the Vault CRM bridge.

    This setting overrides the Delta Tag End on the last target subscription job.

    The bridge job will start and export all records up to the limit.

  2. After starting the first bridge job, clear the 0 value from the Revision Data Value setting.

    Important: If the 0 value is not cleared, the next bridge job will send the first set of records again.

  3. Continue running the bridge jobs until the record limit is no longer hit.