Issue | Description |
|---|---|
MDMN-197547 | When you import a business entity, the import job fails if another business entity with the same name exists in a different folder. |
MDMN-195089 | When you ingress the same records with business IDs multiple times, the match process changes the match and merge status of those records from CONSOLIDATION INDEXED to MATCH INDEXED. The status change happens even if the records have no updates. |
MDMN-192936 | An egress job continues to run even after its associated taskflow is suspended. |
CLDDI-45988 MDMN-190170 | If your organization uses the JWT authentication type, when you start the mapping creation process in Business 360 Console, Data Integration doesn't automatically map the fields between the source and target transformations. |
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: Failed to execte DQ rule. This issue occurs when multiple field group entries exist and they contain nested field groups with the same internal ID. |
MDMN-188300 | When you create a match model with Japan as the default population and include Product_Description or Product_Name field types in the candidate selection criteria, the match process doesn't generate match keys. |
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. If you try to delete the business entity, MDM SaaS doesn't allow you to delete the business entity because of dependent rule associations. You can't delete business entities that contain rule associations equivalent to 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. However, if you create an advanced rule association first and then create a data enhancement rule with the same rule specification, the issue doesn't occur. |
MDMN-184885 | An import job fails if a business entity name contains special characters, such as apostrophes (') or accented letters, such as á. |
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. If you import the predefined objective group into another organization, the migration fails on the first attempt. |
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 | An advanced rule association for a field in a field group doesn't run on empty input fields even though the rule is set to run on empty input fields. This issue occurs when the input field doesn't contain a value in any of the field group entries. |
Issue | Description |
|---|---|
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. This issue occurs only if you update privileges for another field in the same business entity before enabling the disabled 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. This issue occurs when the integer value contains more than eight digits. |
Issue | Description |
|---|---|
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 | When you run an egress job that uses Business 360 FEP Connector, the exported data doesn't contain any value for the nested field groups with names in the following format: Level<number>_<field group name>_<parentId>. |
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: Map the applied fields to an input or output rule specification field. This issue occurs when the field configured for the advanced rule association is mapped to an output field of the rule specification. |
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 | Configure a field with an advanced rule association that uses a rule specification field for the error message. If a field value fails validation, you get the rule association name instead of the error message. |
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. Workaround: Before you run a process hierarchies job, ensure that no record has pending changes awaiting approval. |
MDMN-140258 | When you save an integrity check to validate a business entity record field, you get the following error: Error saving the integrity check rule. Workaround: Close the Add Integrity Check dialog box and refresh the Data Quality tab. |
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. |
Issue | Description |
|---|---|
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. |
Issue | Description |
|---|---|
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: Retryable transaction timeout. |
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. This issue occurs when business entity names start with numeric values or special characters. |
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: Cannot index the records. Recreate the indexes for the Person business entity and try again. This issue occurs because the upgrade action internally changes the business entity to the REINDEX_REQUIRED state, which requires you to reindex the records. |
MDMN-157129 MDMN-162367 | When users submit a record after they delete a field value in a field group, the following error appears in business applications: Failed executing RuleAssociation:'<Rule_Internal_ID>'. This issue occurs when you configure advanced rule associations for fields in a field group and enable the rules to run even if all input fields are empty. |
MDMN-155369 | When Informatica deploys the latest release updates, your organization might face intermittent errors in the Cloud Application Integration processes. |
MDMN-154117 MDMN-153835 | 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: Something went wrong when we tried to render this panel. |
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 | The Merge API can't merge master records that have more than 1000 source records. |
Issue | Description |
|---|---|
MDMN-200681 | After you migrate assets, if you delete a rule association in the source organization and reimport the assets into the target organization, the previously imported rule association that uses Enrichment and Validation Orchestrator is retained in the target organization. You can't delete the business entity because the deleted rule association that's retained is dependent on the business entity. Workaround: Manually delete the rule association that uses Enrichment and Validation Orchestrator, and then delete the business entity. |
MDMN-194652 | When you ingress records with field values that exceed the maximum field length, the ingress job rejects the records. |
Issue | Description |
|---|---|
MDMN-193353 | When you use the Search REST API with the AND operator to search for records with multiple field group entries, MDM SaaS returns inaccurate results. For example, consider a record that contains two entries for the address field group, such as home and office. The city value of the home address is Bangalore and the street value is 36th avenue, BT road. The city value of the office address is Chennai and the street value is St.Thomas Mount. If you perform a search with the condition city = Chennai AND street = 36th Avenue, BT road , MDM SaaS incorrectly treats the criteria as a valid match and returns the record. However, the city and street values don't exactly match the condition, and belong to different field group entries. |
MDMN-189921 | When you pull a renamed asset from the source control repository, the pull operation fails. |
MDMN-188532 | After a record fails validation by a rule association, disabling the rule association doesn't change the record’s invalid status, even though the related validation errors aren't displayed. |
MDMN-187519 | After you run a file import job, the load step might show incorrect values in the sub-metrics. This issue occurs when the POD runs on Oracle Cloud Infrastructure. |
MDMN-186818 | When you enable the option to reject records that fail validation for an objective, MDM SaaS doesn't display localized error messages even after you update the translation file with them. |
MDMN-186699 | When a purge job runs, the job permanently deletes records, search, and report indexes of the specified business entity during the Purge Records step. However, the job details page incorrectly displays two obsolete steps, Index for Search and Purge BE Activity Report, without any metrics. |
MDMN-186460 | When an objective is triggered on a master record, the list of source records that's sent to a plugin also includes the internal source records associated with relationships. Workaround: Ignore the internal source records associated with relationships. Ensure that your business logic doesn't process those source records. |
MDMN-185836 | When enrichment and validation rule associations run on a field that a user doesn't have access to, MDM SaaS fails to save the record with the enriched data. |
MDMN-185557 | When a user edits a record and applies changes to a section, all objectives associated with all fields in the section run instead of only those associated with the changed fields. |
MDMN-185422 | DaaS rule associations for real-time address verifications run even when users apply changes to a section instead of running only when users submit records. |
MDMN-185404 | The translation file doesn't include key-value pairs for objective names, so you can't localize them. |
MDMN-185095 | When you open a custom asset and edit its properties by updating the location, the asset is not moved to the new specified location. |
MDMN-184956 | When you configure rule associations in objective groups that are equivalent to basic and advanced rule associations and don't enable rule associations to run even if all input fields are empty, MDM SaaS runs rule associations. However, the Data Quality Status tab in business applications incorrectly displays the status of the rule association as Success. |
MDMN-181443 | When you run an egress job to export records in a hierarchy, the exported data incorrectly includes deleted records even though the record state indicator is set to active. |
MDMN-180846 | When you configure a source system and associate code lists to picklists for a business entity that's checked out, MDM SaaS saves the source system configuration. However, if you undo checkout on the business entity, MDM SaaS removes the latest configuration of the source system. Workaround: To retain the configuration of the source system, ensure that you check in the business entity. |
MDMN-175253 | When users export search results that belong to a business entity with error remediation enabled, the exported data incorrectly includes a blank column named _id column. |
MDMN-173052 | The Rejected Records report that you download from the load step of an ingress or file import job doesn't include reasons for validation failures of records. |
Issue | Description |
|---|---|
MDMN-180169 | After a user updates a record in a business application, the user is able to submit the record with validation errors even though an associated objective is configured to reject records that fail validation. |
MDMN-177655 | When you configure a dynamic pool, if you undo a change, subsequent changes that you make aren’t saved. |
Issue | Description |
|---|---|
MDMN-168990 | When you download a match output report, the download might fail, or the downloaded report might not contain the maximum number of 150,000 record pairs. |
MDMN-168554 | If you create a record through the business entity record API using the internal ID of a deleted business entity, the API creates the record instead of displaying an error. |
MDMN-166521 | An Update Source Record or Update Source Record Field API request doesn't trigger an approval workflow even though the updated fields were configured to trigger a workflow. |
Issue | Description |
|---|---|
MDMN-156256 | In Operational Insights, the usage summary metrics don't include the count of source and master records that are in MATCH DIRTY status for merge history activity report. |
MDMN-156176 | Validation errors might not appear when you view a record but appear when you edit the same record. This issue occurs with records that fail validations during the ingress or import process because of advanced rule associations for fields that depend on the values of other fields. |
MDMN-144529 MDMN-155578 | After you restore a master record, the master records count isn't updated in the MDM SaaS usage statistics that you can view in Operational Insights. Workaround: Contact Informatica Global Customer Support. |
Issue | Description |
|---|---|
MDMN-156186 | After you merge two source records and run an egress job to export the incremental data, the exported data doesn’t display the updated business ID of the master record for the source records. |
MDMN-155261 | Operational Insights might display an incorrect number of users in an organization. The user count doesn't include users assigned to user groups. |
MDMN-131168 | On the View and Edit page, the tip text field appears editable for a root field even though you select the Hide label option. |
Issue | Description |
|---|---|
MDMN-157663 | When you search for records with the Search REST API, the request takes a longer time to retrieve a response. |
MDMN-155380 | When you merge records that belong to a business entity with deduplication criteria configured for a field group, the nested field group entires are incorrectly highlighted on the Source Records page. |
MDMN-155127 | When a user with the update privilege edits an empty field, the following message appears: Failed to update the record Workaround: Assign the create privilege to the user. |
MDMN-154414 | After you enable error remediation for a business entity, add a basic or advanced data quality rule association to a field in a nested field group. When you enter an invalid value in the field, the validation error appears. However, after you apply the changes, the validation error disappears. |
MDMN-153443 | After you update an Application Integration process that you use in a data enrichment configuration, the changes aren't automatically reflected in the rule association and the data enhancement rule assets. |
MDMN-152949 | After a DaaS rule association validates a record that you added or updated, a warning message appears for incorrect addresses, although error remediation is disabled for the business entity. |
MDMN-152511 MDMN-152509 | When you export all the deleted records in a hierarchy, the exported data contains inaccurate results. |
MDMN-152443 | When you run an egress job to export a hierarchy that contains less than 1000 records, the exported data might contain duplicate records. |
MDMN-151068 | After you disable error remediation for a business entity, if business users export search results, the exported data incorrectly includes additional columns, such as field group ID, severity, and error message. Workaround: Ignore the additional columns. |
MDMN-151915 | After you purge data and disable the error remediation property for a business entity, business users still see validation errors and error type filters in a saved search. Workaround: Ignore the filter values because they don't impact the search results. |
MDMN-150933 | When you create an egress job to export master records and the identifier details of the associated source records, the Assets section incorrectly displays the option to select the record type. |
MDMN-150872 | When users select values for business entity record fields and submit records for approval, business applications might display the following error: Can't send the changes for approval because no user is authorized to approve these changes. The issue occurs when all approvers assigned to a custom user role are denied access to records based on the conditions set in a data access rule. |
MDMN-150328 | When you create a record through business entity record APIs, the response payload differs depending on whether error remediation is enabled or disabled for the business entity. |
MDMN-144892 | You can't delete or disable objective groups that you create for data enrichment. |
Issue | Description |
|---|---|
MDMN-150252 | When you associate a multi-step approval workflow with a custom View and Edit page of a new or a purged business entity, submitting records for approval fails. The following error message appears: Can't START the already STARTING record. |
MDMN-147450 | When you configure a picklist with a code list from Reference 360 that contains multiple code values with identical codes, the filters in business applications don't display all the picklist values. Additionally, the search results count incorrectly includes all records that contain duplicate code values. |
MDMN-147447 | When you search for records in business applications, the filters display the old picklist values instead of the updated values. |
Issue | Description |
|---|---|
MDMN-147911 | When you import a report to an organization, the imported report doesn't appear on the Reports page of business applications. Workaround. Export the Report Set asset from one organization, and then import the Report Set asset to another organization for the reports to appear in business applications. |
MDMN-144467 | After you import a business entity with fields that are enabled for multilingual search, business users can't search for records in their preferred language. This issue occurs if you configure an additional search language in the target organization after you import the business entity and don't reindex the business entity records. Workaround: To search for records in the preferred language, perform one of the following tasks:
|
MDMN-144327 | After you create a record and run an automated merge job, the metrics for the merge process event show the count of both ingressed and automatically merged records. |
MDMN-144009 | A calculated field of a record might not contain the correct value after a record that contributes to the value is deleted. The issue occurs if the deleted record is related to the record with the calculated field through a business entity record attribute. |
MDMN-142225 | When you use a PATCH request to update field groups by passing invalid data as an object and not an array, the trust scores are downgraded incorrectly. |
Issue | Description |
|---|---|
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. |
Issue | Description |
|---|---|
MDMN-137821 | After you update the search configuration, if users run a saved search that contains fields that are no longer searchable, they get the following error: Search API service failed. Workaround: Users must remove the non-searchable fields from their saved searches. |
MDMN-137389 | In Operational Insights, when you view the ingress job metrics, the number of imported records appears inconsistent between the job instance and performance details panels. |
MDMN-137149 | When you add a record-level data access rule for a custom user role with approval privileges, the user can't view the title of the workflow task in the business application. Workaround: Modify the record-level data access rule to an attribute-level data access rule, or delete the data access rule. |
MDMN-136856 | When you create a record that has the same custom business ID as another record, the created record appears as an updated record in the workflow task. The issue occurs when you use the Create Master Record API to create a record that must go through the approval workflow. |
MDMN-136631 MDMN-136187 | When you configure the properties of business entity fields, you can't view all the validation messages because the validation panel doesn't have a scroll bar. |
Issue | Description |
|---|---|
MDMN-135421 | When you import or export data that contains date fields to and from MDM SaaS, the system decrements the dates prior to 1582 by 10 days. |
MDMN-135207 | When a source primary key in a REST API request URL contains the caret character (^), the API request fails. |
MDMN-131460 | Users with the Product 360 Read Only and Supplier 360 Read Only user roles can't view the Hierarchy tab of a record even though they can view the Hierarchies page in a business application. Workaround: Create a custom user role with read-only privilege for the Hierarchy Component on the Security page and assign the custom user role to users. |
MDMN-129899 | When you download the match output report of a match and merge job, the record pairs count in the report might not be the same as the count that appears on Business 360 Console. The issue occurs if another match and merge job runs after the match and merge job for which you downloaded the report. Workaround: To view the correct match report output, download the report immediately after the job completes. |
Issue | Description |
|---|---|
MDMN-123482 | When you export hierarchies and relationships that belong to a specific source system by using Business FEP Connector, the egress job exports hierarchies and relationships from all the source systems. |
MDMN-122466 | On the Explore page, when you view the dependencies of a business entity and open a job definition from the Used By tab, the job definition page doesn't display the information correctly. Workaround: To view the correct information, open the job definition from the Explore page. |
MDMN-103113 | When you import a predefined business entity to an organization from where you exported the business entity and provide a custom project path, the predefined Data Quality assets are saved in both the default and custom projects. Workaround: To avoid duplication of the predefined Data Quality assets, don't enter the custom project path when you import a predefined business entity. |
Issue | Description |
|---|---|
MDMN-121153 | If business entities have only numeric fields, the search operation using the search box might fail in business applications. The search operation fails when users enter a search value other than integers in the search box. |
MDMN-121151 | When you add an integrity check based on a business entity attribute, business entity record fields appear as attribute options in the Add Integrity Check dialog box. The issue occurs if there are at least three business entities and each business entity has a business entity record field relationship with another business entity. |
Issue | Description |
|---|---|
MDMN-117835 | In Operational Insights, when you filter the ingress job metrics based on the hierarchy or relationship asset type, the metrics don't appear. |
Issue | Description |
|---|---|
MDMN-120863 | When you filter by job types on the My Jobs page, the following issues occur:
|
MDMN-115737 | Users with custom user roles can't delete business events. |
MDMN-116700 | The data access rules with conditions on relationship attributes and related business entity attributes don't work as expected. These rules incorrectly authorize users to view records when conditions apply to multiple field groups or multiple related records. |
MDMN-102490 | In Operational Insights, the usage summary for MDM SaaS doesn't refresh. Workaround: After you initiate the summary refresh, wait for the estimated refresh time. You can then refresh the Overview page to view the latest usage summary. |
MDMN-96242 | If different state codes have the same values, the real-time address verification doesn't validate and populate values for the state fields because Reference 360 stores unique values for the code fields. |
Issue | Description |
|---|---|
MDMN-114699 MDMN-140891 | When a dependent picklist field in a record contains a null or an invalid value, you can't save any changes to the record. On the Record Details page, the Submit button appears disabled. Workaround: On the Record Details page, select a valid value for the dependent picklist field and submit the changes. |
MDMN-110693 | If data access rule names contain special characters or characters of languages other than English, you can't open the rules from the user role details page or the rules list page. |
MDMN-110460 | When you view the details of MDM SaaS jobs in the Operational Insights service, the data is inconsistent between the job instance and performance details panels. |
MDMN-109916 | When you view the performance details of MDM SaaS jobs in the Operational Insights service, the time taken for the jobs to complete appears inconsistent. The inconsistency appears on the job instance and performance details panels. Also, the performance details panel displays the end date and time of jobs that are running. |
MDMN-106929 | When you use the Create Master Record API to create a record without specifying required field values, the record is created without validation errors. |
Issue | Description |
|---|---|
MDMN-113525 | After users delete a value of a field in a field group that has uniqueness criteria configured, users can continue to see a value for the field. This issue occurs when you have another duplicate entry for the field group. |
Issue | Description |
|---|---|
MDMN-138014 MDMN-111793 | If you search for job instances after applying a filter on the My Jobs page, the search request incorrectly applies to all job instances. Also, you can't use job statuses as search criteria for finding job schedules. |
MDMN-105575 | You can't configure data access rules or revoke read privilege to restrict access to record names for custom user roles. The record name appears in the title and description of tasks listed in the workflow inbox. The issue occurs if you configure the record name as the title and description for business events. |
MDMN-102953 | When you import a business entity that has DaaS rule associations and integrity checks along with its dependent objects into another organization, the import process fails. The issue occurs when you override the existing assets during the import process. Workaround: Import the business entity, and then the dependent objects without overriding any existing assets. |
Issue | Description |
|---|---|
MDMN-98400 | When you download translation files, some translations in the files might not apply to your business applications. Workaround: Ignore the translations that aren't applicable. |
Issue | Description |
|---|---|
MDMN-94729 | When you run an ingress job to import data with integer fields, and if the value of an integer field exceeds the maximum limit of 2147483647, the ingress job fails. Workaround: Use text fields instead of integer fields if the value of an integer field exceeds the maximum limit and run the job again. |
Issue | Description |
|---|---|
MDMN-100733 | In an organization that uses real-time address enrichment, when the users edit any address on the Workflow Inbox page, the business application doesn't enrich the address of the records in real time. |
MDMN-93837 | When you run egress jobs to export large number of hierarchy records, if the hierarchy data has duplicate relationships, the number of exported records varies in each run of the egress job. |
Issue | Description |
|---|---|
MDMN-91206 | On the My Jobs page, the status of completed egress jobs might incorrectly appear as running. |
MDMN-90345 | You can't export a large number of records if the size of each record exceeds 2.5 MB for more than 1000 records in the data that you export. The egress job might fail with an out-of-memory error. |
Issue | Description |
|---|---|
MDMN-87977 | When you export a report from one organization and import the report to another organization, the imported report doesn't appear on the Reports page in Customer 360. Workaround. Export the Report Set asset from one organization and import the Report Set asset to another organization for the reports to appear in Customer 360. |
MDMN-81951 MDMN-81950 | When Informatica Global Customer Support users access your organization after you grant access, the Add, Delete, and Edit buttons appear enabled. However, the users can't save changes to the assets. |
Issue | Description |
|---|---|
MDMN-83666 | When you export data from a business entity that contains nested field groups, you cannot identify the parent field group for each child field group in the exported data. Workaround: To identify the parent field group, manually refer to multiple files in the exported data and then associate the parentId value of the child field group with the sourcePkey value of the parent field group. |
MDMN-81285 | When you enable source control in Administrator, the following processes might fail:
|
Issue | Description |
|---|---|
MDMN-79435 | You aren't warned when you manually merge records that belong to different populations. |
MDMN-78101 | Even though users with custom user roles aren't assigned the Business360ProcessExecutor role in Administrator, these users can access the option to create hierarchies in the business applications. When these users try to create a hierarchy, the following error occurs: Cannot create the hierarchy <hierarchy name>. Workaround: To enable users with a custom user role to create hierarchies, assign the privileges for creating hierarchies on the Security page and the Business360ProcessExecutor role in Administrator. |
Issue | Description |
|---|---|
MDMN-71954 | For a custom user role, the read privileges that you assign for a hierarchy and its associated relationships and business entities do not work as expected. When a user with the custom user role tries to view the hierarchy record in the business application at a specific point in time, the user gets the following errors: Authorization cannot be granted. Cannot find history data for this hierarchy at given point in time. |
Issue | Description |
|---|---|
MDMN-71748 | If you enable the delete privilege for a business entity on the Security page, the delete and cut icons for the custom fields are not enabled on the Attributes tab of that business entity as expected. |
Issue | Description |
|---|---|
MDMN-71008 MDMN-68427 | If you import an egress job that exports hierarchy or relationship data to a target organization, the import job fails with the following error: Metadata object with id: <hierarchy name>/<relationship name> was not found! Workaround: Create an egress job in the target organization and add the associated taskflow that exports hierarchy or relationship data. |
Issue | Description |
|---|---|
MDMN-68378 | When you run an ingress job to import more than 300,000 records into a data model that contains more than 20 field groups, the ingress job fails. Workaround: Use a taskflow that contains mappings with individual source object for each field group. |
MDMN-68091 | After you select a taskflow in an egress job, the Record Type and Source System columns do not appear as lists. Workaround: Click the Record Type and Source System column values to view them as lists and select the required option. |
MDMN-67134 | On the My Jobs page, the search box on the Job Instances tab fails to retrieve the job instances if you use a job type value as the search text. The search box on the Job Schedules tab fails to retrieve the job schedules if you use a status as the search text. Workaround: To find job instances and job schedules based on the job type or status values, use the filter option. |
Issue | Description |
|---|---|
MDMN-64722 | The search box in a custom page does not work as expected when you configure the following user interface elements:
|
MDMN-64290 | When you add a taskflow to an export job, the complete names of source systems might not appear due to space constraints. Workaround: Hover over a source system name to view its complete name. |
Issue | Description |
|---|---|
MDMN-56720 | A custom user role with the read privilege to access the Match tab of a business entity can perform edit and delete tasks on the Match tab. |
MDMN-56464 | The attribute names that you can use in the REST API requests are case sensitive. (August 2021) |
MDMN-53702 | For a custom user role, if you assign the create and read privileges to the attributes of a predefined business entity, the create privilege does not work as expected. When the user creates custom fields and saves the business entity, the following error occurs: Metadata authorization error. Workaround: Assign the update privilege for the business entity attributes in addition to the create and read privileges. |
MDMN-53519 | When you run an ingress job that processes records with multiple value fields, and both updates and deletes are part of the process, the process deletes records but ignores updates to the records. |
MDMN-50082 | You can't delete custom smart fields even when they don't contain dependencies. |
MDMN-49897 | You can't delete fields and field groups of custom business entities that were previously used in custom pages. |
Issue | Description |
|---|---|
MDMN-58420 | When you create a business entity field with display name ending with colon (:), the field label does not appear in Customer 360. |
MDMN-47638 | When you render the Alternate Names field group as a card in a custom page, the page validation does not work as expected. |
Issue | Description |
|---|---|
MDMN-38312 | When you configure a custom page, if you add a custom field group that does not allow multiple instances, the field group do not work as expected in Customer 360. |
MDMN-38216 | If you configure fields to allow multiple values, the fields do not appear in Customer 360. Workaround: Delete the multiple value fields, and then create the fields again as single value fields. |
MDMN-37147 | When you manually stop or pause a running job, the job status might not update in the My Jobs page. |