Issue | Description |
---|---|
MDMN-148088 | 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-147193 | When you rename or delete a user role associated with a data access rule, the rule becomes invalid. You can't delete the rule on the Data Access Rules page. Also, asset details don't appear for these rules. Workaround: Ensure that you don't rename or delete a user role assigned to data access rules. |
MDMN-144963 | The translation files don't contain any labels associated with the match and export data feature. |
MDMN-144495 | When you export hierarchies and relationships by using Business 360 FEP Connector, the egress job might fail at the stage step with the following error: Invalid JSON input: Unexpected character |
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-144372 | When you export source records that contain validation errors, the exported data doesn't include the source systems of the field groups. The issue occurs only when the preview feature for validation errors is enabled in your organization. |
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-143668 | After you enable merge history activity reports to run the Publish Reports Data job, if the job fails, you can't recover the reports automatically. Workaround: Enable merge history activity reports again and then run the job. |
MDMN-143582 | Even after you purge the records of a specific business entity, the number of records displayed in the merge history activity report remains unchanged. |
MDMN-142579 | When you enable merge history activity reports to run the Publish Reports Data job, the run time parameter in the metrics isn't available for the job. |
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. |
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. |
MDMN-126424 | When you unmerge one of the source records from a master record that has multiple source records, the corresponding patch record remains associated with the master record. |
MDMN-115129 | After you filter jobs in Operational Insights by selecting assets from the asset picker, if you try to update the list of selected assets, the previously selected assets don't appear as selected in the asset picker. |
Issue | Description |
---|---|
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. Workaround: Ensure that the input field contains a value in all the field group entries. |
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. |
Issue | Description |
---|---|
MDMN-141310 | Custom reports that are deleted in business applications appear in Business 360 Console. |
MDMN-139153 | When you enable picklist fields in a business entity as facetable and search records through the Search REST API, the search response doesn't display the code field. However, if you enable the picklist fields as searchable or searchable and facetable, the search response displays the name and code fields. |
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-136927 | If a relationship attribute contains a decimal value with a precision of more than 34, the digits after the 34th digit are replaced with zeroes. |
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-122747 | When you import a searchable hierarchy into an organization, the process hierarchies job doesn't automatically run. Workaround: Run the process hierarchies job to index the records of the searchable hierarchy. |
MDMN-121922 | When you apply the changes to the source ranking of a field, the ranking is automatically saved with a new label. |
MDMN-121913 | When you apply the changes to the source ranking of a field, two labels appear for the same source ranking. |
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. |