Release Notes > Fixed Limitations

Fixed Limitations

The following table describes the Multidomain MDM SaaS fixed issues. Not all monthly releases include fixed issues. The (<release>) value in each issue description represents the release in which the issue was fixed.
When you try to load more hierarchies in the hierarchy tree, Customer 360 SaaS displays the same set of hierarchies instead of displaying the remaining hierarchies.
(April 2024)
When you remove a parent record that contains child records from a hierarchy using the Remove the record only option, the child record associations aren't removed from the record. When you try to open the hierarchy of the child records, the page doesn't open.
(April 2024)
If you add a space followed by a hyphen in a searchable field of a record, you can't save the record.
(April 2024)
When you update a record, the required dynamic root fields aren't validated in the sections that you don't edit.
(April 2024)
If the related records of a record appear in a table, the Add Filter option might not work as expected.
(April 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.
(February 2024)
The dependent picklist values might not change if you change the parent picklist value multiple times.
(February 2024)
When you use a custom page that has create, read, and update privileges for the fields in one panel and only read privileges for the fields in another panel, you can't create a record.
(February 2024)
When the deduplication criteria is set for a field group and the field group IDs in records contain a period (.), only one field group entry survives even though other entries with a period (.) aren't duplicates.
(February 2024)
When you enable the November 2023 preview functionalities of custom reports in your organization, the edit icon doesn't appear for reports that are created for individual records.
(February 2024)
When you export records with validation errors, the exported data doesn't contain error messages for picklist fields. This issue occurs when the preview feature to export records with validation errors is enabled.
(February 2024)
When you import records with field values that contain multibyte characters, the import job fails at the transform step and the following error appears:
Disnext_internal_error_An internal server error has occurred.
(February 2024)
When you filter a report that displays validation errors of records, you can't view filter values for the types of validation errors and severity of errors.
(February 2024)
You can't view some fields on the dimensions, measures, and filter lists for custom reports that are based on validation errors. These fields are hidden behind the horizontal scroll bar.
(February 2024)
When you review a task that has an updated address, the task displays an unenriched address.
(February 2024)
When you expand a search result, the fields display incorrect values.
(January 2024)
When you enable the November 2023 preview functionalities of custom reports in your organization, you can view, edit, and refresh report data when the fields used in custom reports are enabled as reportable.
(January 2024)
When you create a custom report, the names of the fields that you set as dimensions appear incorrectly on the applied filters section of the Data Set panel.
(January 2024)
If you create custom reports based on validation errors, the dimensions, measures, and filter lists appear empty for business entities that don't have any records.
(January 2024)
Even though your user role doesn't have the update privilege, you can assign a record to a hierarchy node after you move the record within the hierarchy.
(January 2024)
When you run a saved search that contains configured filter values, the search results might be incorrect because some of the filter values might not be applied.
(November 2023)
When you filter a report that displays merge history activity based on a declarative rule name, you can view the deleted rules as filter values.
(November 2023)
When you filter a report that displays merge history activity based on declarative rule names, you might not view any declarative rules as filter values.
Workaround: Contact Global Customer Support to resolve this issue.
(November 2023)
If you add an integer field as a measure to view the sum of all field values in your custom report, the chart doesn't render.
(November 2023)
When you select the fields of a field group as dimensions and measures in a custom report, the report might show inconsistent data. The inconsistency appears if the field added in measures doesn't have any value.
(November 2023)
If the input value is null for a float data type field that has an advanced data quality rule association, you don't get a warning message when you save the record.
(November 2023)
When you import a hierarchy, if you don't map the required source primary key field for the hierarchy instance, Customer 360 SaaS doesn't display an error.
(November 2023)
You can merge records even though matching is disabled for the records.
(November 2023)
On the Record Details page, if you delete a field group from a record, the deleted field group appears as a duplicate field group on the Source Records page.
(November 2023)
In the Customer Distribution by State chart and report table, some of the state names do not appear correctly.
When users display the data in custom reports as pie charts, the following error appears:
There’s a problem with your chart!
TypeError: Cannot read properties of undefined (reading ‘rotation’)
(October 2023)
When you save a custom report that contains picklist fields, the picklist field values might appear as codes in the report table and chart.
(October 2023)
When you import values to a decimal field based on a configured precision and scale, the imported values are incorrect.
(October 2023)
If you use nested fields to create a custom report, the report doesn't display any data.
(October 2023)
After you delete a hierarchy and refresh the Hierarchies page, the hierarchy still appears. However, all the nodes of the hierarchy are deleted.
(August 2023)
When you submit a record that has multiple sections in the edit mode, the required field validation might not work as expected.
(October 2023)
When you use a REST API request to update an address of a record that contains more than one address, Customer 360 SaaS creates a duplicate address instead of updating the existing address.
(October 2023)
When you update a record that contains a country picklist and if an advanced rule association uses the picklist as input and output fields, the record isn't saved. You get the following error:
Required JSON object properties are missing: [country].
(August 2023)
If the input value is null for a date and time field that has an advanced data quality rule association, you don't get a warning message when you save the record.
(August 2023)
After you import a record, if you update the email address and phone fields and save the record, the DaaS rule association validates the fields and doesn't display the updated values.
(August 2023)
When you edit a record, you can't view the boolean field values even though you have create and read permissions.
(September 2023)
You can't submit a record after you delete the value of a parent picklist.
(August 2023)
When you create a record by using REST API, Multidomain MDM SaaS applies the data quality rule associations to the fields but doesn't display the warning message.
(August 2023)
When you view the match pair details for a source record that has more than 100 match pairs, the Match Pair Details page loads the first 20 match pairs. However, the page doesn’t load the remaining match pairs even when you scroll down.
(August 2023)
When you try to stop a bulk edit job on the My Jobs page, the job continues to run.
Workaround: The job stops after a while.
(August 2023)
After you edit records in bulk, the bulk edit job includes skipped records in the count of successful records.
(August 2023)
The Workflow Inbox page doesn't display tasks for a user who belongs to a user role that maps to a SAML group or role.
(August 2023)
When the imported file doesn't contain the Source Primary Key values for the parent nested field groups, the file import job automatically generates the Source Primary Key values for the records. The job imports the records without rejecting them. Due to the automatically generated Source Primary Key values, the data quality rule associations fail.
(August 2022)
When you try to edit records in bulk, you can't update the values of attributes that are at the second or higher level of a nested field group.
(July 2023)
When you try to edit records in bulk, you can't identify records to edit based on a dependent picklist field or update dependent picklist field values.
(July 2023)
When you edit records in bulk, you can delete the values of a required field in a field group.
(July 2023)
When you try to edit records in bulk, the preview table doesn't display values for system fields, such as source system, source business ID, and source primary key.
(July 2023)
A record can have sections that are rendered as tables. If you enter an incorrect value in those sections and apply the changes, you can't apply any more changes to the value.
(July 2023)
When you modify the name of a code value in Reference 360, the existing records don't display the updated name.
(July 2023)
When you edit an existing field value of a record, the system saves the updated value instead of the cleansed value. This issue occurs when the cleansed value is the same as the existing value.
(June 2023)
After upgrading to the latest version of Multidomain MDM SaaS, the Home page does not render correctly, and all the predefined and custom reports do not appear on the Reports tab.
Workaround: Ensure that you do not assign more than 49 user roles to a user.
If you edit the addresses in a nested field group during address enrichment and try to close the field group without saving the changes, Multidomain MDM SaaS disables the Submit button. Also, you can't view the already enriched address.
Workaround: Wait for about three seconds until the enrichment process completes, then edit the address.
(May 2023)
When you enter values for the address fields and submit a record, you can't view the enriched values for those fields but you can view the enriched values for the remaining address fields.
Workaround: To view the enriched address values in all the fields, refresh the page.
(May 2023)
An import job fails if the source primary key field contains special characters other than the following characters:
(April 2023)
When you create a custom report on records that contain multiple entries for a field group, the report displays each entry of the field group as a separate record even though they belong to the same record.
(April 2023)
When you add an entry in a section of a record and submit, you can't add more entries in that section.
(April 2023)
The Customers Distribution by State report doesn't populate any data either on the report table or the chart associated with it.
(April 2023)
When you use the Edit Selected option to edit records that have nested field groups, the changes aren't saved.
(April 2023)
Users with custom user roles that don't have the required privileges can create and edit custom reports, view the Reports page, and view the charts added to the Home page dashboards.
(April 2023)
When a user creates a record with an invalid address that's enriched in real time, the business application doesn't display the enriched address.
Workaround: To view the enriched address, the user must refresh the page.
(April 2023)
When you delete a parent field group that contains a smart field group with validation errors, the section level error messages appear incorrectly.
(July 2023)
While reviewing a merge task in the Workflow Inbox, if an approver changes the label of a record from Match to Not a match, the label of the record continues to appear as Match.
(February 2023)
When you save data in a section of a record, an error message might incorrectly appear even though you enter valid data.
(February 2023)
If you view the details of the Organization by Revenue report, the report doesn't display the chart associated with it.
(February 2023)
In a browser that has the language preference set to French, Portuguese, German, or Spanish, when you select a date to create schedules, the following incorrect error message appears:
Cannot destructure property 'options' of 'getLocale(…)' as it is undefined.
(February 2023)
When you perform a filtered search, a list that depends on another list doesn't display values that you can use to perform the search. For example, a State list that depends on a Country list doesn't display the list of states.
(February 2023)
When you export search results, the exported file doesn't include the boolean fields.
(February 2023)
When you delete a field value that overrides the master record field value, the overriding field remains highlighted on the Source Records tab. The corresponding overridden field on the master record appears empty instead of displaying the field value that survived after trust score recalculation.
(February 2023)
When a user with a custom user role publishes a custom report, the report data doesn't get populated.
(December 2022)
When you edit a custom report, the pie chart associated with that report doesn't load properly.
(December 2022)
When you filter the report data of a custom report that uses date fields, you can't select a date from the Select date dialog box. The Select date dialog box disappears as soon as you select a date.
(December 2022)
The Run button is not disabled as expected for a user with a custom user role that does not have the required privileges to publish reports.
(December 2022)
When a user with a custom role that does not have permission to view record history clicks the History tab, the following incorrect message appears:
Internal error. Try again later. If the problem persists, contact Informatica Global Customer Support.
(December 2022)
When you set the language preference for your browser to a locale-specific language, such as French (Canada), some translations fall back to English.
(February 2023)
If you view the report details of the Organization by Revenue report, a blank page appears instead of the report details.
(November 2022)
The load step of an ingress job displays incorrect metrics for records that are successfully ingressed.
(November 2022)
When you ingress a record with the source last updated date in the future, the value of the rejected records displays zero.
(November 2022)
When you expand the field groups nested within a field group on the Source Records page, the fields don't align properly within the sections that display the nested field groups.
(November 2022)
When you create a custom report and use the Equals operator to filter the field values that contain decimal numbers, the report table does not display the decimal numbers even though the report data contains field values with decimal numbers.
(November 2022)
When you override the values of a master record while viewing the survivorship criteria of the field values, the survivorship criteria disappears after you save the changes.
(November 2022)
When you open a record that has related records, the count of related records that appears in the Related Records section is incorrect.
(September 2022)
When you ingress a record from a source system for incremental changes and the last updated date in the source record is incorrect, the error report doesn't capture the correct path details.
(September 2022)
When you ingress a source record for incremental changes at the field group level, an error message with incorrect source primary key and reference path details appears.
(September 2022)
When you update a source record, the source primary key and reference path details don't appear in the error report for partially rejected records.
(September 2022)
When you create a custom report and select a reference data codelist, such as currency or country, to filter the report data, the reference data codelist fails to display the values as expected.
Workaround: Remove the selected reference data codelist from the filter and add the same codelist again.
(September 2022)
You can ingress a source record for incremental changes with the last updated date as the current date.
(September 2022)
When remove a default relationship attribute value and do not replace it with a new value, the system will revert to the default.
(August 2022)
When you ingress a record, the source primary key details don't appear in the API response if the record is rejected.
(September 2022)
If a Cloud Application Integration process has one task action and a workflow using that process triggers a workflow task, the user can't claim the task. The following error message appears:
Your request cannot be processed at this time. Please refresh your task list and try again.
Operation failed.
Fault: GenericFault
(September 2022)
Population data does not appear in the Source Records section.
(August 2022)
When you create a custom report and apply a boolean filter, the report table shows the False value count as "0" instead of displaying the actual count.
(August 2022)
When you override field values in the master record, the overriding field values appear on the record details page only after you refresh the page.
(August 2022)
When you use the search box to perform a search, the filter attributes that you select from the View More option don't appear after you save and run the search.
(August 2022)
You cannot search for records if you use only the business ID value in a filtered search even though the Business ID field is a searchable field.
(July 2022)
On the My Jobs page, when you filter job instances based on multiple job types or job statuses, the job instances aren't filtered.
(June 2022)
When you unmerge a source record that overrides the field values of a master record, the business ID of the master record changes.
(June 2022)
You cannot view the history of changes if a record contains relationship graphs.
(June 2022)
When you delete some of the fields in the CSV file and import the file, you can see deleted fields as empty rows in the Preview section with the following error:
Mandatory field is empty.
Workaround: If you open the csv file in Notepad ++, you can see the empty rows and columns marked as ,,,,. To remove the empty rows and columns, you must delete them from Notepad ++ and then import the file to your business application.
(June 2022)
You can view the changes to a hierarchy at a specific point in time even though the changes at that point in time were not submitted.
(June 2022)
When you update the value of display field in a record, the display field value that appears on the left navigation bar does not reflect the updated value.
Workaround: Refresh the page.
When the direction of relationship import is from Business Entity 2 to Business Entity 1, the display names of the business entities in the From and To columns of the Preview and Import File page are swapped.
(April 2022)
If you have a business entity and a hierarchy with the same display name, you cannot import data into that business entity.
(April 2022)
When you delete multiple file import mappings at a time, some of the mappings might not get deleted.
(December 2021)
When a task approver tries to open a workflow task for a new or updated hierarchy, the following error appears:
Unauthorized: User could not be authenticated. No message available.
Workaround: Clear the browser cache and try again.
(December 2021)
When you import a hierarchy, if you do not map the Name field with a source column header, the hierarchy does not appear in Multidomain MDM SaaS.