Release Notes > Known Limitations
  

Known Limitations

The tables in this section describe known issues for Multidomain MDM SaaS. Not all monthly releases include known issues.

July 2024 known issues

Issue
Description
MDMN-145562
If your organization processes records that contain validation errors and you update and save any field in a record through the user interface, the existing fields with validation errors appear valid. However, the field values remain invalid.
MDMN-144010
After you validate records that were merged in real-time and unmerge them, they display an incorrect match rule and outcome.
MDMN-143230
After you edit an address of a record on the Workflow Inbox page and save the record, the record doesn't display the updated address.
Workaround: To view the updated address, refresh the page.
MDMN-143195
MDMN-143252
When you select a dimension, measure, and filter to create a report, the lookup values appear incorrectly with empty spaces in the drop-down list.
MDMN-142786
When you create a record through an approval workflow, the record isn't visible in the merge history activity report.

May 2024 known issues

Issue
Description
MDMN-114809
When you edit a table row in a record section, you can't select values or move your cursor inside the fields of the row by using the arrow keys on your keyboard.
Workaround: Exit edit mode and try to edit the row again.

April 2024 known issues

Issue
Description
MDMN-140112
When you merge or unmerge records, you can't view the field group values of records that don't contribute to the master record. The issue also occurs when you review the records in a merge task.
MDMN-139056
To update field values in nested field group entries, you might select Update record sections as the import type. If you don't map the operation type field for the root field, the file import job updates the field values. However, instead of the exact count of the input rows, the job displays the count as 0.
MDMN-138576
When you open a merge task and preview merged records, source records that aren't part of the merge task don't appear.
MDMN-137821
When you run a saved search, you might get the following error:
Search API service failed.
Workaround: Contact your administrator.
MDMN-137503
When you create standard reports and apply any date field as a filter, the report data might appear inconsistent.
MDMN-137109
When you run an import job, MDM SaaS ignores the values for the fields named as Message Type even though the job succeeds.
Workaround: Ensure that you don't use Message Type as a column name in the CSV file.
MDMN-136640
When you drill down to the second level of a drill-down report that has only two levels of dimensions, the report data keeps loading instead of displaying the two levels of data.
MDMN-135879
When a user with 60 or more user roles tries to open Multidomain MDM SaaS, it fails to open.
MDMN-134622
The total count of validation errors and warnings increases when you expand each level in nested field groups.
MDMN-132312
If you publish an event that is related to an action on a record and the exported data contains more than 65,000 characters, the exported data doesn't include the complete record.

February 2024 known issues

Issue
Description
MDMN-134247
The users with approval privileges can view the system details of records and claim, approve, reject, send back, and release a task even though they don't have access to the records.
MDMN-122818
When you run a saved search, the search might not display all filter values that you selected by viewing more filter values for a field.
MDMN-131385
When you import data, if the imported data contains updates to the picklist values of existing records, the import job fails.
Workaround: Request your administrator to provide the delete privilege for picklist fields.
(January 2024)
MDMN-130814
After you import a record that includes a field group ID with a period (.) into MDM SaaS, you can't edit the field group entry on the MDM SaaS application user interface.
Workaround: To edit these field group entries, perform a PATCH operation by using REST APIs. Also, before you import new records, ensure that the field group IDs in the records don't contain special characters other than the following special characters:
- _ | :
MDMN-129928
If a child record in a hierarchy has its parent record as a child, you can't perform a search on the hierarchy.

January 2024 known issues

Issue
Description
MDMN-131385
When you import data, if the imported data contains updates to the picklist values of existing records, the import job fails.
Workaround: Request your administrator to provide the delete privilege for picklist fields.

December 2023 known issues

Issue
Description
MDMN-128933
When you export records with validation errors, the exported data contains error messages with field names that don't match the field names in the column headers of the field groups and nested field groups. This issue occurs when the preview feature to export the records with validation errors is enabled.
MDMN-128036
When you add a predefined dashboard that displays an overview of MDM SaaS usage statistics, the total number of source records doesn't include the patch records of the master records.

November 2023 known issues

Issue
Description
MDMN-127577
When you create a report based on the types of validation errors and apply Fields with Validation Errors as a filter, the report data displays all types of validation errors irrespective of the applied filter.
MDMN-127450
When you import data, records with incorrect population names aren't rejected at the Load step. However, the Generate Tokens step fails.
MDMN-126388
When you import business entity records that have field values calculated based on related records, the process takes a long time to complete.
MDMN-126263
When you filter a report that displays merge history activity based on a declarative rule name, you might view duplicate rule IDs as filter values. The duplicate rule IDs appear when a declarative rule has multiple versions and the rule doesn't have a description.
MDMN-126253
When you create a report that displays merge history activity and select a dimension, the dimension remains highlighted even if you change your selection.
MDMN-125796
When you create a report that displays merge history activity based on the users who merged the source records or the merged date, the report displays incorrect data.
MDMN-124933
When you create a report that displays merge history activity based on the match outcome, you can't view the number of source records merged by users that are sent for approval. These records are included in the total number of source records merged by users.
MDMN-124806
When you specify a range to filter the report data of a drill-down report, the Data Set panel doesn't display the search results.
MDMN-124552
If you delete source records after creating a report that displays merge history activity, the report data doesn't exclude the deleted source records even if you refresh it.
MDMN-123888
In a drill-down chart, if you select a field value that also appears as an additional filter value on the Data Set panel, you can't drill down into the report data.

October 2023 known issues

Issue
Description
MDMN-123478
When you add a child record to a hierarchy, there is no information that the changes to the dynamic field definitions aren't inherited yet.
MDMN-124316
A custom report that contains picklist fields doesn't display the updated field values after you update them in Reference 360.
MDMN-122453
The search request might fail if the search text starts with, includes, or ends with a space followed by the following special characters:
+ - = && || > < ! ( ) { } [ ] ^ " ~ * ? : \ /
The following error appears:
Search API Service Failed
Workaround: Delete the space between the search text and the special character, and try again.
MDMN-121153
If you enter values other than integers in the search box to find records with numeric field values, the search request might fail, and the following error appears:
Search API Service Failed
MDMN-120966
After you delete a hierarchy, the hierarchy still appears in the Hierarchy tab of a record that belongs to the hierarchy. The issue occurs if you can assign records to parent nodes in a hierarchy.
MDMN-114485
When you search for a record that has a searchable field with no value, the record doesn't appear in the search results. The issue occurs if optional fields are searchable.
MDMN-108878
System fields that display the date and time, such as Created On, Last Updated Date, or Last Updated Date, display values in the Unix epoch time format.
MDMN-92566
You can view a maximum of 40 entries for a field group in the source records section.

September 2023 known issues

Issue
Description
MDMN-120464
After you fix a few validation errors in a record, a custom report based on the type of validation errors might display incorrect data.

August 2023 known issues

Issue
Description
MDMN-120224
When you try to view the history of records on the record details page, you might get the following error even though you have the required permissions:
Internal Error. Try again later. If the problem persists, contact Informatica Global Customer Support.
Workaround: To view the history of records, refresh the record details page multiple times.
MDMN-119507
When you merge duplicate field group values based on the deduplication criteria, the surviving field group values aren't highlighted on the Source Records page.

July 2023 known issues

Issue
Description
MDMN-118378
When you override the values of a field group that has field groups nested within it with a field group that has no nested field groups, the nested field groups might not appear on the Source Records page. The issue occurs if block survivorship is enabled for a field group that has field groups nested within it.
MDMN-117106
After you approve a task to unmerge multiple source records from a master record, you can't see the corresponding closed task.
Workaround: To view the closed task, refresh the Task Details page.
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-110685
If you don't have the required privilege to delete a field value, you get the following incorrect message when you delete the field value:
The user [username] is not authorized to perform the action [update] on the resource [business entity name].
The preceding message incorrectly indicates that you don't have authorization to update records instead of deleting records.