Fixed issues

MDMN-192936

An egress job continues to run even after its associated taskflow is suspended.

CLDDI-45988

MDMN-189982

When a boolean field within a nested field group entry has an advanced rule association, saving changes to records causes the following error:

MDMN-185996

When you create basic, advanced, and DaaS rule associations in organizations created after the October 2025 release, MDM SaaS creates a predefined objective group for the business entity. The predefined objective group contains objectives with rule associations that are equivalent to the basic, advanced, and DaaS rule associations.

MDMN-184970

After you create a data enhancement rule with the Data Quality - Validation or Transformation plugins and select a rule specification from Data Quality, if you use the same rule specification and create an advanced rule association, MDM SaaS fails to save the business entity.

MDMN-184550

When you configure basic, advanced, and DaaS rule associations in organizations created after the October 2025 release, MDM SaaS creates a predefined objective group for the business entity. The predefined objective group contains objectives and rule associations that are equivalent to the basic, advanced, and DaaS rule associations.

MDMN-182944

When you run a purge job to purge all records across business entities, the index for search step runs indefinitely.

MDMN-143347

When you run an ingress job, the metrics of the index records for search step incorrectly display count of records that are indexed in the latest run. The metrics don't include the count of records that were previously indexed.

MDMN-141876

MDMN-183336

A match and merge job that uses a match model with an extended key generation level for generating match keys for candidate selection fails.

MDMN-183310

If users create records while a Generate Search Index and Match Keys job is running, the job fails.

MDMN-181866

An egress job that uses Business 360 FEP Connector to export hierarchies fails during the extract step if node names within the hierarchies exceed 75 characters.

MDMN-180203

When you run an egress job that uses Business 360 FEP Connector to export all records and two nested field groups share the same source primary key, the exported data includes only one of those nested field groups.

MDMN-176081

When users search for records in business applications, the search result don't show the field configured as the title in the search layout components page, if the field is of integer data type.

MDMN-179583

In Operational Insights, when you filter jobs, the Reference 360 usage statistics become null.

MDMN-179392

After you update the search configuration of system fields and save and index the business entity, when users search for records in business applications, the search doesn't return any records.

MDMN-176015

When you run an egress job, the extract step takes a longer time to complete even though taskflows are run successfully in Data Integration.

MDMN-174924

When a taskflow of an egress job is suspended, MDM SaaS doesn't automatically clean up backend files related to the job. However, MDM SaaS continues to run other jobs causing performance issues.

MDMN-173090

When you ingress or import records, the index for search step fails if the searchable fields contain values with special characters, such as ¶, ¦ . Subsequently, the ingress or import job fails. Additionally, the Error Records metric in the index for search step doesn't display the total number of failed records.

MDMN-169707

A Search Match API request that searches for null values fails.

MDMN-167206

While you edit a business entity, if you delete it, and then try to save the changes, an error message appears. However, the save succeeds on the second attempt.

MDMN-165821

When you purge data, the job appears failed even though the Purge BE Activity Report Index step of the job still continues to run.

MDMN-156527

If you enable a field that's disabled in a business entity, and then enable the field, MDM SaaS removes the existing privileges for the enabled field.

MDMN-137163

When you add or import values to integer data type fields through business applications and ingress jobs, MDM SaaS might reject the field values or include incorrect values. Additionally, data quality rule associations configured on these fields might return inaccurate validation results.

MDMN-173633

After you delete a field group entry in a business application and run an egress job, the exported data incorrectly shows the status of the field group entry as active.

MDMN-173621

If the source primary key of a field group contains invalid special characters, an ingress job fails during the load step.

MDMN-172993

Using the same internal ID for a root field and a field within a field group causes an error when you create a record in a business application.

MDMN-172885

MDMN-172760

When you run a match and merge job to reset matched records for a specific business entity, the job resets matched records in all business entities.

MDMN-171395

When you try to disable an advanced rule association, MDM SaaS doesn't save the rule association and displays the following error:

MDMN-171327

When you use the EQUALS filter comparator, the Search REST API doesn't return records for fields that are set as searchable.

MDMN-170849

MDMN-169582

When you delete an entry of a field group that's disabled from surviving as a block and configured with minimum or maximum survivorship rules, field values from the deleted entry might survive.

MDMN-168995

A business application doesn't automatically time out after the session idle timeout period.

MDMN-168981

On the View and Edit page of a business entity, when you select a field in one section, another field in a different section is incorrectly selected along with the selected field.

MDMN-167171

When you run an egress job to export deleted relationships, the job fails to export a relationship if any record in the relationship is deleted.

MDMN-157220

When you update the address values of existing records in real time, MDM SaaS doesn't enrich the address values. However, when you create records, MDM SaaS enriches the address values.

MDMN-157206

When you configure the highlighted field for a Page Header component, the Business ID system field doesn't appear for selection.

MDMN-148496

When you use the Create Master Record REST API to create a record for a business entity that has basic and advanced rule associations, MDM SaaS validates the field values. However, if the validations fail for both basic and advanced rule associations, MDM SaaS displays validation messages only for the basic rule association in the response.

MDMN-148242

When a record that belongs to a hierarchy is pending approval, the process hierarchies job fails. The issue occurs if the record awaiting approval has records that inherit dynamic field definitions from the record.

MDMN-140258

When you save an integrity check to validate a business entity record field, you get the following error:

MDMN-140177

When the Create Master Record API is used to create records with null picklist values, you can't find or view the records in business applications or by using the Search API.

MDMN-96376

If a data access rule has conditions on a field that isn't searchable or conditions on relationship attributes or related business entity attributes, the search requests don't work as expected for custom user roles. If more than 10000 records exist for the business entity, when a user with the custom user role searches for records, the search results page doesn't retrieve matching records.

MDMN-169072

When you run a match and merge job to match source records that contain null values, the match process doesn’t generate record pairs for records with null values. This issue occurs when declarative rules use the threshold-based merge strategy.

MDMN-169066

If you update the source system of an ingress job for the second time and save the job, an error message appears.

MDMN-166766

When you add business entities to a business application, you can select disabled URL fields as display fields.

MDMN-164565

When you update a source record by using REST APIs, the rule associations for data enrichment are triggered even though you can enrich only master records.

MDMN-167195

When you try to remove a rule association from an objective or disable an objective, Business 360 Console stops responding.

MDMN-165203

When you run an egress job to export relationships in a hierarchy using Business 360 FEP Connector, the egress job doesn't export any records.

MDMN-165109

When you set the browser locale to Japanese, you can’t configure segment matching for declarative rules that contain Boolean fields.

MDMN-165104

You can publish a match model even if the model doesn’t contain declarative rules or a completely trained ML model.

MDMN-164343

When you migrate predefined assets, the migration fails even though the corresponding licensed business application is set up in the target organization.

MDMN-163981

You can save a business entity without specifying an internal ID for its fields.

MDMN-163716

When you run an ingress job, the transform step fails intermittently because the Cloud Application Integration processes time out.

MDMN-163682

Basic rule associations for fields in a field group with multiple picklists return incorrect values when the rule associations use one of the picklists as input.

MDMN-163607

When you render a field group as a table and fields within the field group contains errors based on the rule associations, the validation messages don't appear for the fields in business applications.

MDMN-163147

After you remove a business entity of a business application and migrate assets, the import fails because the references to the business entity isn't removed.

MDMN-161206

After you ingress records that match existing records in MDM SaaS and then run a match and merge job, the job doesn’t generate record pairs for some of the matching records.

MDMN-160917

A search reindex job fails for a business entity that has more records in deleted state than the records in active state.

MDMN-160751

When you run a Search Match API request that uses a match model with a candidate filter to match records, the API returns records that don't match the filter criteria.

MDMN-160328

When you configure advanced rule associations with transformation functions on picklists and then import records that contain invalid picklist values, MDM SaaS generates invalid picklist values, which subsequently get imported.

MDMN-159699

The Create Master Record API fails to run again when the following error appears:

MDMN-159136

When you run an ingress job, MDM SaaS doesn't run the configured advanced rule associations if the mapped field name in Cloud Data Integration contains an underscore as a prefix followed by the business entity name.

MDMN-158554

When you create a reference data asset in Business 360 Console with an apostrophe (') in the display name, the asset creation page continues to load indefinitely without displaying an error message.

MDMN-158546

When you update the search configuration of a business entity and search for records using the Search REST API with a model version that's later than the current model version, the API doesn't return any results.

MDMN-158168

When you run an ingress job with a large volume of data, MDM SaaS skips the rule associations for some records. This issue occurs because of internal errors in the source and target transformations in Cloud Data Integration.

MDMN-157990

When you upgrade your organization to the latest release version and run an ingress job, the job fails at the Index for Search step with the following error:

When users submit a record after they delete a field value in a field group, the following error appears in business applications:

MDMN-155369

When Informatica deploys the latest release updates, your organization might face intermittent errors in the Cloud Application Integration processes.

When you edit records with errors on the record details page or in the workflow inbox, the validation error type incorrectly changes from Information to Others.

MDMN-152976

When you configure a decimal field with a scale of 0 and import records that contain decimal values with trailing zeros, such as 1.00 or 1,00, and run an ingress job, the job imports these values without any error. However, when you edit these records in business applications, the value incorrectly appear as 1,00 instead of its actual decimal format.

MDMN-151413

When you configure a DaaS real-time rule association on address fields and create records, MDM SaaS takes about two seconds to enrich the address values after the record is created.

MDMN-146190

When you configure basic rule associations for picklists to run even if all input fields are empty, MDM SaaS doesn't apply these rule associations to the picklist fields. If users create a record without adding values to picklists in business applications, MDM SaaS displays the following error:

MDMN-144963

The translation files don't contain any labels associated with the match and export data feature.

MDMN-141310

Custom reports that are deleted in business applications appear in Business 360 Console.

MDMN-133109

After you configure a page for each step of a custom workflow, when an approver views a create task in the Workflow Inbox, the page incorrectly shows components that aren't part of the Create page.

MDMN-130067

After you configure a DaaS rule association for real-time address verification on an address field group and map specific fields, MDM SaaS incorrectly runs the rule association on unmapped fields in the address field group. This issue occurs when you update these unmapped fields in business applications.

MDMN-65426