Release Notes > Known Limitations

Known Limitations

The following table describes the Multidomain MDM SaaS known issues in this release. The (<release>) value in each issue description represents the release in which the issue was reported.
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.
(February 2024)
When you create a record, if you add a value within double quotes or parentheses in any searchable field, a business application displays an internal error instead of listing similar records.
(February 2024)
When you create custom reports in an organization where the November 2023 preview functionalities are disabled, you can't create schedules to publish the reports. The issue occurs if you add facetable fields as dimensions and measures to your custom reports. Additionally, you can't view the report data on the report details page.
(February 2024)
When you preview a custom report that uses picklist fields as dimensions and measures, the preview fails with the following error:
Service error. Can't preview the report. Try again later.
(February 2024)
When you add charts as widgets to individual records, the Add Widget button on the record details page appears disabled.
(February 2024)
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.
(February 2024)
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)
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:
- _ | :
(February 2024)
When you export the search results, you might get blank columns for the picklist fields in the nested field groups. The issue occurs when you don't have the preview feature to export the nested field group values enabled.
Workaround: You can safely ignore those columns.
(December 2023)
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.
(December 2023)
When you export records, the exported data doesn't include the ID column for the field groups and nested field groups that contain only picklist fields. This issue occurs when the preview feature to export the nested field group values is enabled.
(December 2023)
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.
(December 2023)
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.
(November 2023)
When you import data, records with incorrect population names aren't rejected at the Load step. However, the Generate Tokens step fails.
(November 2023)
When you import business entity records that have field values calculated based on related records, the process takes a long time to complete.
(November 2023)
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.
(November 2023)
When you create a report that displays merge history activity and select a dimension, the dimension remains highlighted even if you change your selection.
(November 2023)
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.
(November 2023)
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.
(November 2023)
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.
(November 2023)
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.
(November 2023)
When the operation type header in the CSV file contains space and special characters, the import process ignores the operation type values.
(November 2023)
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.
(November 2023)
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.
(October 2023)
When you select a record in a hierarchy, the Dynamic Field Definition tabs from unrelated hierarchies might appear.
(October 2023)
A custom report that contains picklist fields doesn't display the updated field values after you update them in Reference 360.
(October 2023)
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.
(October 2023)
When a record goes through a custom approval workflow, the task details of the record don't appear.
(October 2023)
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
(October 2023)
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.
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.
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.
You can view a maximum of 40 entries for a field group in the source records section.
(October 2023)
After you fix a few validation errors in a record, a custom report based on the type of validation errors might display incorrect data.
(September 2023)
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.
(August 2023)
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.
(August 2023)
When you export search results, you can't export nested child field groups to the CSV file.
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.
(July 2023)
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.
(August 2023)
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.
(July 2023)
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.
(July 2023)
If you select all the records to edit in bulk and then clear some selections, the preview table shows an incorrect number of selected records.
(May 2023)
When you try to edit records in bulk, you can't edit the values of field groups that are empty.
(May 2023)
When you edit records in bulk, if no records match the specified conditions, a message about multiple records being updated is incorrectly displayed.
(May 2023)
When custom role users having a data access rule and select records to edit in bulk, the preview table shows an incorrect number of selected records.
(May 2023)
When you press Tab to navigate out of a blank date field, the following error incorrectly appears:
Enter a valid value.
Workaround: Refresh the browser window.
(April 2023)
If you import records that contain special characters in their field group IDs, you can't update the value of fields in those field groups. When you apply the changes to field values, the following error appears:
The user [username] is not authorized to perform the action [update] on the resource [business application entity].
(April 2023)
After you delete a picklist value of a record in the related records table, the record continues to display the previous value.
When you try to import records into a hierarchy, if the input file doesn't contain the instance details for the records, a preview error appears.
Workaround: Configure the source primary key values for the error records in the input file, and try again.
(March 2023)
When you translate a custom report, some of the translations in the chart are not translated, and translations fall back to English.
(February 2023)
When you select multiple records on the search results page for performing actions, such as exporting, manually merging, editing selected records, there might be a discrepancy between the number of selected records and the number available for action.
(February 2023)
When you import data with integer fields, and if the value of an integer field exceeds the maximum limit of 2147483647, the import fails.
Workaround: Use text fields instead of integer fields if the value of an integer field exceeds the maximum limit and import the data again.
(January 2023)
When you update a record, the information or warning messages that appear might contain fields that aren't present in the record.
(September 2022)
If the name of a newly created custom report uses the name of a custom report that was deleted earlier, the newly created custom report displays the report data of the deleted custom report in the report table.
Workaround: Publish the newly created custom report to view the correct report data.
(August 2022)
When you update a source record by using a REST API, the API response doesn't include the partially rejected record.
(September 2022)
When the MDEFileImport job has failed at the Match Index step due to low resources, the job status still shows as Running.
(August 2022)
When you submit a task and try to claim the same task for approval, an error message appears, indicating that the initiator and the approver are the same.
(July 2022)
When you use your business application or external APIs to create records, you cannot specify the population. Your application and the APIs use the default population.
(June 2022)
Some users cannot view the history of records when they click the History tab.
(April 2022)
When you ingress more than one thousand records with the business ID values, the records use the automatically generated business ID values instead of the user-defined business ID values. The mismatch in the business ID values creates multiple master records and causes performance issue.
When hierarchy properties are updated, the workflow task that is generated doesn't include a description of the updates.
(January 2022)
If you try to open a hierarchy when data is being imported into the hierarchy, the hierarchy does not appear.
(December 2021)
When you filter the history of a record that has a large number of historical changes, the performance is poor.
(December 2021)
When you unmerge a record, a workflow is triggered and the record unmerges successfully after the approval. If you merge these unmerged records and try to unmerge these again, the unmerge fails after the approval.
(December 2021)
When you run the match and merge job for the records in Business 360 Console and unmerge some records from the imported records in Multidomain MDM SaaS, the History panel of the unmerged records does not list the merge and unmerge actions.
(December 2021)
The users with custom user roles can view the Hierarchies page and the Hierarchies tab on the record details page even though they don't have the required privilege to view it. The following incorrect error messages appear when the users with custom user roles click Hierarchies:
Error:Error:Request failed with status code 403
Error: Request failed with status code 403
(December 2021)
When you import data that contains decimal fields, the decimal values might incorrectly round off in the imported records.
(December 2021)
When you import records that contain invalid values in the decimal fields, the import process doesn't reject the records.
(December 2021)
When you perform a search for a negative value, the search results include positive values and negative values. For example, if you search for -92.7, the search results include records that have 92.7 and -92.7.
(December 2021)
You cannot add an image to a record by entering a URL in the Image field.
(December 2021)
When you try to import a file without selecting any target business entity or relationship, you receive multiple copies of the same error message.
(December 2021)
When you edit the Full Name field and submit, the updated data does not appear when the update is approved.
Workaround: Configure Full Name field as read only in Business 360 console.
(December 2021)
You cannot import relationships between two records that belong to different source systems.
(December 2021)
When you edit the first name, middle name, or last name of a Person record, the record title does not match with the full name.
(December 2021)
Validated and Enriched indicator appears in the Address, Email and Phone sections of imported records even though data is not validated.
(December 2021)
In a record, when a phone number includes alphabetical characters, the phone number doesn't get validated.
(December 2021)
The concatenated value of a field does not change when you change the input values to null.
(December 2021)
When you import data, if your CSV file contains boolean field values other than true or false, some records might not be imported.
(December 2021)