In modernization projects, you can now use an interactive user interface to review and map objects between the MDM Hub and MDM SaaS. You no longer need to generate mapping files to manually map fields.
You can continue to edit or modify manual mapping files for existing modernization projects that aren't completed.
The modernization projects now include the following enhancements:
•You can create a consolidated summary of modernization progress across selected modernization projects. The summary shows key metrics on a read-only page, such as the number of objects modernized, in progress, pending, and excluded from modernization.
•You can now archive modernization projects to accommodate more active projects. However, archived projects are read-only and you can't move them to the active state again.
When master records belong to multiple populations, you can now specify the population parameter in the Search Match API version 2 to search within a specific population. For example, if your customer data includes the Chinese, Japanese, and US populations, specify Chinese as the population parameter to return master records that match the Chinese population.
To search by population, the master records must have population names:
•For master records created after the April 2026 release, MDM SaaS automatically assigns population names to master records based on the populations of their source records.
•For records created before the April 2026 release, use the Migrate API to add population names to master records.
After you assign populations to master records, run the Generate Search Indexes or Match Keys job to generate match keys based on the assigned population.
To enhance search accuracy, MDM SaaS now returns more relevant results. When you search for records, you might notice changes in your search results. For example, a search for a record with the first name Benjamin also returns records with the first names Ben and Benny.
Reset organization
You can reset your organization to its default, newly provisioned state. A reset permanently deletes all data, assets, configurations, jobs, and job schedules in MDM SaaS. Consider a reset when configurations or extensive customizations make a development or QA organization difficult to manage, and starting over is simpler than fixing it. To enable reset for your organization, contact Informatica Global Customer Support.
When you run an ingress job, you can update individual fields in a target record instead of replacing the entire record. The update applies only to the fields in the source system that are mapped to the target fields. Other fields remain unchanged. You can also control how the update handles empty values in mapped fields. When a mapped field is empty in the source system, you can overwrite the target value with null or leave it unchanged.
Note:
This functionality is available only after you migrate your rule associations to use Enrichment and Validation Orchestrator in organizations created before the October 2025 release.
You can now create folders within a dynamic pool to group dynamic fields by topic or purpose. You can add dynamic fields to folders at any level and drag them to rearrange their order. When you design your custom page layout, you can add these folders to the fields component on the page.
For more information about dynamic pools, see Dynamic pools.
Enrichment and Validation Orchestrator
Enrichment and Validation Orchestrator includes the following new features and enhancements:
Error messages in Application Integration-based plugins
The Application Integration-based plugins for validation and cleansing can now return error messages for the fields that fail validation. If you configure the rule associations to show these messages, those fields display the error messages. As a result, you can now show specific reasons for validation failures instead of a generic message.
Non-anonymous process authentication
If you enable a data enhancement rule to use a process with non-anonymous access, your organization can now use the session ID authentication type in addition to the JWT authentication type.
Empty field handling
You can now choose to run objectives on empty fields in lenient mode or controlled mode.
In the lenient mode, an objective runs when sibling fields at different levels, such as root fields and field groups, are updated. You can map business entity fields to input fields that mirror the field structure of a business entity. When input fields of an objective are empty and their sibling fields change, the objective can run on empty fields even if those fields belong to different levels.
In the controlled mode, an objective runs only when sibling fields at the same level, such as a single field group or a nested field group, are updated. Use controlled mode when you want control over which fields an objective can run on when its input fields are empty.
REST API
Business 360 REST API includes the following new resource:
Hierarchy API
Use the hierarchy REST API to create, update, delete, and filter hierarchies. You can add, retrieve, and delete parent and child records. You can move records within a hierarchy or across hierarchies. You can also retrieve the exact location of a specific record in a hierarchy by returning all paths from the parent record to the child record. Additionally, you can find a list of hierarchies that a record is part of based on its business ID.
For more information about the REST APIs to manage hierarchies, see Hierarchy API.
MDM Extension for Databricks
Use MDM Extension for Databricks to publish master data for the customer, supplier, product, and location domains from MDM SaaS to Databricks Data + AI Platform. You can use the published data for integrated analytics, machine learning, and agentic AI applications. With trusted master data, you can improve customer segmentation, strengthen supplier and supply chain risk management, and optimize retail and product performance.