Release Notes for IDMC
- Release Notes for IDMC
- All Products
ASK INFAPreview
Please log in to access Ask INFA.
ASK INFAPreview
Issue
| Description
|
|---|---|
MDMN-153022
| When a rule association for data enrichment fails, the business applications don't display any error messages.
Workaround: You can check the logs to identify the cause. To obtain the logs, contact Informatica Global Customer Support.
|
MDMN-152511
MDMN-152509
| When you export all the deleted records in a hierarchy, the exported data contains inaccurate results.
|
MDMN-152443
| When you run an egress job to export a hierarchy that contains less than 1000 records, the exported data might contain duplicate records.
|
MDMN-152205
| If you configure approval workflow for specific fields, the approval workflow isn't triggered for those fields when business application users accept a recommendation that enriches the fields.
|
MDMN-151068
| After you disable error remediation for a business entity, if business users export search results, the exported data incorrectly includes additional columns, such as severity and error message.
Workaround: Ignore the additional columns.
|
MDMN-151029
| MDM SaaS doesn't run the reapply data access rules or publish data access rules jobs even though no other existing jobs are in progress. This issue occurs when a reapply data access rules or publish data access rules job failed previously because of internal service errors.
Workaround: If the publish data access rules or reapply data access rules jobs don't run, contact Informatica Global Customer Support.
|
MDMN-151915
| After you purge data and disable the error remediation property for a business entity, business users still see validation errors and error type filters in a saved search.
Workaround: Ignore the filter values because they don't impact the search results.
|
MDMN-150933
| When you create an egress job to export master records and the identifier details of the associated source records, the Assets section incorrectly displays the option to select the record type.
|
MDMN-150872
| When users select values for business entity record fields and submit records for approval, business applications might display the following error:
Can't send the changes for approval because no user is authorized to approve these changes. The issue occurs when all approvers assigned to a custom user role are denied access to records based on the conditions set in a data access rule.
|
MDMN-150328
| When you create a record through business entity record APIs, the response payload differs depending on whether error remediation is enabled or disabled for the business entity.
|
MDMN-148242
| When a record that belongs to a hierarchy is pending approval, the process hierarchies job fails. The issue occurs if the record awaiting approval has records that inherit dynamic field definitions from the record.
Workaround: Before you run a process hierarchies job, ensure that no record has pending changes awaiting approval.
|
MDMN-146444
| When you configure basic rule associations and select an input field, picklists appear in the list. However, you can't select a picklist.
|
MDMN-146190
| When you configure basic rule associations for picklists to run even if all input fields are empty,
MDM SaaS doesn't apply these rule associations to the picklist fields. If users create a record without adding values to picklists in business applications,
MDM SaaS displays the following error:
|
MDMN-144892
| You can't delete or disable objective groups that you create for data enrichment.
|
Issue
| Description
|
|---|---|
MDMN-148496
| When you use the Create Master Record REST API to create a record for a business entity that has basic and advanced rule associations,
MDM SaaS validates the field values. However, if the validations fail for both basic and advanced rule associations,
MDM SaaS displays validation messages only for the basic rule association in the response.
|
MDMN-147824
| When you add a match model for the predefined business entities, such as Category, and Contact, the following error appears:
Internal error. Cannot create the match model. Try again later. |
MDMN-147806
| A user with a custom user role that's configured with approval privileges can't view the record details on the
Workflow Inbox page in business applications.
When the user opens an approval task, the following error appears:
This issue occurs when the user role is assigned to a data access rule that has conditions set for relationships and related business entity records.
|
MDMN-147450
| When you configure a picklist with a code list from Reference 360 that contains multiple code values with identical codes, the filters in business applications don't display all the picklist values. Additionally, the search results count incorrectly includes all records that contain duplicate code values.
|
MDMN-147447
| When you search for records in business applications, the filters display the old picklist values instead of the updated values.
|
Issue
| Description
|
|---|---|
MDMN-148780
| When you purge all data, the streaming ingestion and replication task doesn't publish data in real time. The issue exists even after the purge job completes its run.
Workaround: After the purge job completes its run, redeploy the streaming ingestion and replication task that was created to publish events in real time.
|
MDMN-147911
| 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-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-144009
| A calculated field of a record might not contain the correct value after a record that contributes to the value is deleted. The issue occurs if the deleted record is related to the record with the calculated field through a business entity record attribute.
|
MDMN-143925
| After users update a dynamic field in a field group that has deduplication criteria configured, the previously deduplicated field group entries aren't displayed even though they are unique now.
Workaround: Don't apply deduplication criteria to a field group in a dynamic field values attribute.
|
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-123076
| If a master record contains more than 1,000 source records, the ingress job fails at the load step.
|
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:
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-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.
|
