The October 2025 release includes the following changed behavior.
Control access to train Adaptive AI match models
You can now control which user roles to train an Adaptive AI match model. By default, no user roles are allowed to train models.
To allow a user role to train models, assign the Adaptive AI Match Model privilege to the user role on the Security page. Users without this privilege can't view the Adaptive AI Match Model tab on the match model configuration page.
If you have users who previously had access to train these models, ensure that you update their custom user roles with the new privilege.
Previously, the following predefined user roles had the privilege to train Adaptive AI match models:
The following table lists the user interface changes to the Survivorship page:
User interface changes
Current behavior
Previous behavior
Count of fields
When you search for fields, MDM SaaS displays the count of enabled fields.
The following image shows the count of fields:
Previously, the count also included disabled fields.
Selection check box
The selection check box for fields now aligns with the selection check box of the business entity.
The following image shows the selection check box:
Previously, the selection check box was indented to the right.
Block survivorship
The block survivorship icon is modified and is aligned to the right.
The following image shows the block survivorship icon:
Previously, the block survivorship icon was aligned to the left.
Fields tree filter
You can apply a filter when you press Enter or click the search icon. MDM SaaS expands field groups that contain matching fields.
Previously, the search filtered root fields and field groups with matches but didn’t display the individual fields within the field groups.
Fields tree
When you hover over a field, the row is not highlighted.
Previously, the field was highlighted.
Field selection
You can now use the following keyboard shortcuts to select or deselect fields:
- Press SHIFT and select fields to select or clear all fields between the first and last selected fields.
- Press CTRL and then select a field or clear the selection.
Previously, you couldn’t select or clear multiple fields.
Block survivorship confirmation dialog box
After you enable block survivorship for a field group, if you select another field without applying changes, a warning message appears. The message warns you to apply your changes and indicates that the survivorship configuration of fields will reset to match the survivorship configuration of the field group.
Previously, a confirmation about applying the changes appeared, followed by a warning about resetting the survivorship of fields within the field group.
Source ranking
After you configure source ranking for a field and select the field, the source ranking list displays the rank.
Previously, the source ranking list didn’t display the rank.
Validation message
If a business entity doesn't have source ranking configuration, adding a rule to a field without such configuration triggers a single validation message. The message indicates that both the business entity and the field require source ranking configuration.
Previously, multiple validation messages appeared, one for the business entity and one for the field.
Validation messages for dynamic fields
New error messages are introduced when dynamic fields fail to load.
Previously, error messages didn’t appear.
Source rank list
The source rank list now displays the ranks in ascending order.
The following image shows a list of ranks:
Previously, the source rank list was sorted lexicographically by rank.
Multiple fields selection
When you select multiple fields, click Edit All, add survivorship configuration, and discard the survivorship configuration, the selection stays intact.
Previously, discarding survivorship configuration cleared your selection.
Dynamic fields validation message
The validation messages for dynamic fields now appear beneath their corresponding dynamic field value attributes.
When you train an Adaptive AI match model, the data access rules configured for a business entity control your access to the training data set associated with the model.
Previously, you could access the training data set associated with an Adaptive AI match model irrespective of the data access rules configured for the business entity.
The uniqueness criteria property of field groups has been removed from the general properties.
Previously, you could view uniqueness criteria as a general property of field groups, along with a message indicating that it has been moved to the Survivorship page and renamed Deduplication.
After creating match pairs, the match process now identifies related record pairs and organizes them into record pair groups. In a future release, you can view these grouped records in the Match Analysis and Explainability dashboard.
Previously, the merge process created record pair groups.
Match Analysis and Explainability dashboard
You can now control access to the Match Analysis and Explainability dashboard related to a business entity. The custom user roles with the Match Analysis and Explainability Dashboard privilege can now access the Match Analysis and Explainability dashboard related to a business entity. Additionally, ensure that these custom roles have read privileges for the records and attributes of the selected business entity.
The following image shows the read permission assigned for accessing the Match Analysis and Explainability Dashboard related to the Person business entity:
Previously, all custom user roles had access to the Match Analysis and Explainability dashboard.
For more information about configuring privileges for custom user roles to access the Match Analysis and Explainability dashboard, see Match Analysis and Explainability Dashboard.
Basic rule associations
When you configure a basic rule association on a picklist field and enable it to run even if all input fields are empty, the rule association returns the output as null if the input field value is empty.MDM SaaS considers null as the output and allows users to save the record.
Previously, if you didn't specify the input field value, the rule association returned the output as empty and didn't allow users to save the record.
The responses of the Read Master Record by Business ID and Read Master Record by SourcePKey REST APIs don’t include the survival parameter in the ruleAssociation array.
Previously, the ruleAssociation array included the survival parameter.
For more information about the Read Master Record by Business ID and Read Master Record by SourcePKey APIs, see Business entity record APIs.
Application Integration-based Enrichment and Validation
When a rule association configured for Application Integration-based enrichment or validation runs on a record, the payload that's sent to the associated process also includes fields with null values. Previously, MDM SaaS included only the fields that had values in the payload.
To improve matching accuracy, the Search Match API versions 1 and 2 now require you to specify search terms in a specific format based on their data type. If you don’t use the correct format, the API request fails. For example, if you use TRUE or False as the boolean field value, the API request fails.
Previously, the search terms didn't require any specific format.
When the total number of records processed in the stage step of an egress job is zero, MDM SaaS now skips the extract step and completes the job, thereby reducing the job runtime.
Previously, MDM SaaS continued with the extract step when the total number of records processed in the stage step was zero.
