Issue | Description |
|---|---|
MDMN-149003 | When you add a value to a picklist field in search filters, the following error appears: Enter a correct value. To see all the values, click View More. Workaround: To select a specific picklist value, click View More. |
MDMN-148951 | When you edit records in bulk or view saved searches and apply search filters, the first letter of picklist values that are lowercase appears as uppercase. |
Issue | Description |
|---|---|
MDMN-147828 | If you apply a saved mapping during a CSV file import, the import process doesn't map the fields. If you try to apply the saved mapping again, the import process maps the fields but displays following error: Cannot update metadata object. Supplied version of the object is out of date. |
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-144216 | When you export reports based on record metadata, you can't export more than 10,000 records. |
MDMN-144048 | When you filter search results for active and deleted records, if you try to manually add values from the records as additional filter values, the following error message appears: Enter a correct value. To see all the values, click View More. Workaround: To include additional filter values, click View More, and select the value that you want to apply as a filter. |
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. |
MDMN-141345 | In a related records table that displays records related through a relationship, you can't filter records when you select the Equals operator and enter a double field type value. |
MDMN-140813 | When a record has one field group entry and you delete that entry, the master record on the source records page doesn't display the deleted entry with the icon that indicates deletion. |
MDMN-139443 | When you create a report with dimensions and measures set as error type, the report displays an incorrect error count. |
MDMN-130393 | If you delete source records after you create a report that displays merge history activity, the metrics might display incorrect number of records processed. The metrics are displayed incorrectly for one of the following reasons:
|
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. |
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-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 Product 360 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. |
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-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. |
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. |
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. |
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-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. |
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. |