Issue | Description |
|---|---|
MDMN-155261 | Operational Insights might display an incorrect number of users in an organization. The user count doesn't include users assigned to user groups. |
MDMN-154673 | When you run a Create Match and Merge Job Instance API request with an incorrect process type parameter value, the API creates a match and merge job instance that doesn't perform any match and merge process. |
MDMN-131168 | On the View and Edit page, the tip text field appears editable for a root field even though you select the Hide label option. |
Issue | Description |
|---|---|
MDMN-156108 | When you refresh the User Roles tab on the Security page, the following error might appear: Can't refresh page. Try again later. This issue might occur due to a timeout error. Workaround: To resolve this issue, refresh the User Roles tab again. |
MDMN-155380 | When you merge records that belong to a business entity with deduplication criteria configured for a field group, the nested field group entires are incorrectly highlighted on the Source Records page. |
MDMN-155365 | When you purge records that belong to a business entity, the purge job might fail at the purge business entity report index step. These failures occur when the purge job is either queued for an extended period or runs for a long time. |
MDMN-155127 | When a user with the update privilege edits an empty field, the following message appears: Failed to update the record Workaround: Assign the create privilege to the user. |
MDMN-154414 | After you enable error remediation for a business entity, add a basic or advanced data quality rule association to a field in a nested field group. When you enter an invalid value in the field, the validation error appears. However, after you apply the changes, the validation error disappears. |
MDMN-154143 | If you map a picklist as one of the input fields for data enrichment, data enrichment isn't triggered when a user updates the field in a business application. |
MDMN-154117 MDMN-153835 | When you edit records with errors on the record details page or in the workflow inbox, the validation error type incorrectly changes from Information to Others. |
MDMN-153443 | After you update an Application Integration process that you use in a data enrichment configuration, the changes aren't automatically reflected in the rule association and the data enhancement rule assets. |
MDMN-152949 | After a DaaS rule association validates a record that you added or updated, a warning message appears for incorrect addresses, although error remediation is disabled for the business entity. |
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 field group ID, severity, and error message. Workaround: Ignore the additional columns. |
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-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: Something went wrong when we tried to render this panel. |
MDMN-144892 | You can't delete or disable objective groups that you create for data enrichment. |
Issue | Description |
|---|---|
MDMN-150252 | When you associate a multi-step approval workflow with a custom View and Edit page of a new or a purged business entity, submitting records for approval fails. The following error message appears: Can't START the already STARTING record. |
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: Cannot load the records in the task. For more details, contact your administrator. 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: 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-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. |
Issue | Description |
|---|---|
MDMN-114699 MDMN-140891 | 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. |
MDMN-110693 | If data access rule names contain special characters or characters of languages other than English, you can't open the rules from the user role details page or the rules list page. |
MDMN-110460 | When you view the details of MDM SaaS jobs in the Operational Insights service, the data is inconsistent between the job instance and performance details panels. |
MDMN-109916 | When you view the performance details of MDM SaaS jobs in the Operational Insights service, the time taken for the jobs to complete appears inconsistent. The inconsistency appears on the job instance and performance details panels. Also, the performance details panel displays the end date and time of jobs that are running. |
MDMN-106929 | When you use the Create Master Record API to create a record without specifying required field values, the record is created without validation errors. |
Issue | Description |
|---|---|
MDMN-113525 | After users delete a value of a field in a field group that has uniqueness criteria configured, users can continue to see a value for the field. This issue occurs when you have another duplicate entry for the field group. |
Issue | Description |
|---|---|
MDMN-138014 MDMN-111793 | If you search for job instances after applying a filter on the My Jobs page, the search request incorrectly applies to all job instances. Also, you can't use job statuses as search criteria for finding job schedules. |
MDMN-105575 | You can't configure data access rules or revoke read privilege to restrict access to record names for custom user roles. The record name appears in the title and description of tasks listed in the workflow inbox. The issue occurs if you configure the record name as the title and description for business events. |
MDMN-102953 | When you import a business entity that has DaaS rule associations and integrity checks along with its dependent objects into another organization, the import process fails. The issue occurs when you override the existing assets during the import process. Workaround: Import the business entity, and then the dependent objects without overriding any existing assets. |
Issue | Description |
|---|---|
MDMN-102010 | After you purge records that belong to a specific business entity, the metrics for the purge matched record pairs step don't include the number of match pairs collected. |
MDMN-96920 | When you unmerge records with relationship attributes that are updated after the records are merged, the updated values are lost. The unmerge operation causes the attributes to return to the default values that existed before the merge, or changes the attributes to have no values. |
MDMN-90835 | When you use the Source Record API to retrieve a source record, the GET request can't contain the pipe (|) symbol encoded as part of the URI. It fails with a bad request error. |
Issue | Description |
|---|---|
MDMN-98400 | When you download translation files, some translations in the files might not apply to your business applications. Workaround: Ignore the translations that aren't applicable. |
MDMN-97563 | If you create data access rules for relationship or related business entity, the number of records for facetable fields is incorrect in the filters panel of the search results page for custom user roles. |
MDMN-96376 | If a data access rule has conditions on a field that isn't searchable or conditions on relationship attributes or related business entity attributes, the search requests don't work as expected for custom user roles. If more than 10000 records exist for the business entity, when a user with the custom user role searches for records, the search results page doesn't retrieve matching records. |
MDMN-86986 | When you try to delete a custom asset, the asset doesn't show up on the Explore page, but doesn't get removed completely. Workaround: To ensure that you completely delete a custom asset, contact Informatica Global Customer Support. |
MDMN-85734 | You can't change the predefined translations for the Related Records, General Information, and Select Date sections. |
Issue | Description |
|---|---|
MDMN-94729 | When you run an ingress job to import data with integer fields, and if the value of an integer field exceeds the maximum limit of 2147483647, the ingress job fails. Workaround: Use text fields instead of integer fields if the value of an integer field exceeds the maximum limit and run the job again. |
Issue | Description |
|---|---|
MDMN-124098 | When you configure a page with the Header 2 template, if the values of breadcrumb, line 1, or line 2 fields are long, the values might wrap or overlap. |
MDMN-100733 | In an organization that uses real-time address enrichment, when the users edit any address on the Workflow Inbox page, the business application doesn't enrich the address of the records in real time. |
MDMN-95173 | When an upgrade job is successful, a notification appears that indicates the job has failed. Workaround: Ignore the notification. The My Jobs page shows that the job is successful. |
MDMN-93837 | When you run egress jobs to export large number of hierarchy records, if the hierarchy data has duplicate relationships, the number of exported records varies in each run of the egress job. |
MDMN-91333 | When you add an exact match field in a declarative rule, if you click the Field Name picklist, the previously added exact match field incorrectly appears. Workaround: After you add an exact match field, click outside the Add Declarative Rule dialog box. |
Issue | Description |
|---|---|
MDMN-91206 | On the My Jobs page, the status of completed egress jobs might incorrectly appear as running. |
MDMN-90345 | You can't export a large number of records if the size of each record exceeds 2.5 MB for more than 1000 records in the data that you export. The egress job might fail with an out-of-memory error. |
Issue | Description |
|---|---|
MDMN-87977 | When you export a report from one organization and import the report to another organization, the imported report doesn't appear on the Reports page in Customer 360. Workaround. Export the Report Set asset from one organization and import the Report Set asset to another organization for the reports to appear in Customer 360. |
MDMN-82844 | If you have sub-organizations in your environment, you can see the Support Access tab on the Global Settings page of your sub-organization. The tab shouldn't appear. |
MDMN-81951 MDMN-81950 | When Informatica Global Customer Support users access your organization after you grant access, the Add, Delete, and Edit buttons appear enabled. However, the users can't save changes to the assets. |
Issue | Description |
|---|---|
MDMN-83666 | When you export data from a business entity that contains nested field groups, you cannot identify the parent field group for each child field group in the exported data. Workaround: To identify the parent field group, manually refer to multiple files in the exported data and then associate the parentId value of the child field group with the sourcePkey value of the parent field group. |
MDMN-81285 | When you enable source control in Administrator, the following processes might fail:
|
Issue | Description |
|---|---|
MDMN-79435 | You aren't warned when you manually merge records that belong to different populations. |
MDMN-78101 | Even though users with custom user roles aren't assigned the Business360ProcessExecutor role in Administrator, these users can access the option to create hierarchies in the business applications. When these users try to create a hierarchy, the following error occurs: Cannot create the hierarchy <hierarchy name>. Workaround: To enable users with a custom user role to create hierarchies, assign the privileges for creating hierarchies on the Security page and the Business360ProcessExecutor role in Administrator. |
MDMN-77826 | When you ingress records that belong to populations that aren't supported, such as aml or ofac, the data loads into the data store, but match tokenization fails. Records with invalid population names do not load. |
Issue | Description |
|---|---|
MDMN-73380 | For a custom user role, the read and update privileges that you assign for a hierarchy model and its associated relationships and business entities do not work as expected. The "Authorization cannot be granted" error appears incorrectly when a user with the custom user role performs the following tasks:
|
MDMN-71954 | For a custom user role, the read privileges that you assign for a hierarchy and its associated relationships and business entities do not work as expected. When a user with the custom user role tries to view the hierarchy record in the business application at a specific point in time, the user gets the following errors: Authorization cannot be granted. Cannot find history data for this hierarchy at given point in time. |
Issue | Description |
|---|---|
MDMN-71748 | If you enable the delete privilege for a business entity on the Security page, the delete and cut icons for the custom fields are not enabled on the Attributes tab of that business entity as expected. |
Issue | Description |
|---|---|
MDMN-71008 MDMN-68427 | If you import an egress job that exports hierarchy or relationship data to a target organization, the import job fails with the following error: Metadata object with id: <hierarchy name>/<relationship name> was not found! Workaround: Create an egress job in the target organization and add the associated taskflow that exports hierarchy or relationship data. |
Issue | Description |
|---|---|
MDMN-68378 | When you run an ingress job to import more than 300,000 records into a data model that contains more than 20 field groups, the ingress job fails. Workaround: Use a taskflow that contains mappings with individual source object for each field group. |
MDMN-68091 | After you select a taskflow in an egress job, the Record Type and Source System columns do not appear as lists. Workaround: Click the Record Type and Source System column values to view them as lists and select the required option. |
MDMN-67134 | On the My Jobs page, the search box on the Job Instances tab fails to retrieve the job instances if you use a job type value as the search text. The search box on the Job Schedules tab fails to retrieve the job schedules if you use a status as the search text. Workaround: To find job instances and job schedules based on the job type or status values, use the filter option. |
MDMN-65426 | The Merge API can't merge master records that have more than 1000 source records. |
Issue | Description |
|---|---|
MDMN-64722 | The search box in a custom page does not work as expected when you configure the following user interface elements:
|
MDMN-64290 | When you add a taskflow to an export job, the complete names of source systems might not appear due to space constraints. Workaround: Hover over a source system name to view its complete name. |
Issue | Description |
|---|---|
MDMN-60929 | When you create a user-triggered event for a hierarchy that requires a workflow and then create a relationship between two business entities, the workflow task does not trigger. |
Issue | Description |
|---|---|
MDMN-56720 | A custom user role with the read privilege to access the Match tab of a business entity can perform edit and delete tasks on the Match tab. |
MDMN-56464 | The attribute names that you can use in the REST API requests are case sensitive. (August 2021) |
MDMN-53843 | The Date and Time fields that you can use in the REST API requests support only the Unix epoch time format. |
MDMN-53702 | For a custom user role, if you assign the create and read privileges to the attributes of a predefined business entity, the create privilege does not work as expected. When the user creates custom fields and saves the business entity, the following error occurs: Metadata authorization error. Workaround: Assign the update privilege for the business entity attributes in addition to the create and read privileges. |
MDMN-53519 | When you run an ingress job that processes records with multiple value fields, and both updates and deletes are part of the process, the process deletes records but ignores updates to the records. |
MDMN-50082 | You can't delete custom smart fields even when they don't contain dependencies. |
MDMN-49897 | You can't delete fields and field groups of custom business entities that were previously used in custom pages. |
Issue | Description |
|---|---|
MDMN-58420 | When you create a business entity field with display name ending with colon (:), the field label does not appear in Customer 360. |
MDMN-47638 | When you render the Alternate Names field group as a card in a custom page, the page validation does not work as expected. |
Issue | Description |
|---|---|
MDMN-68183 | When you define a business entity, you might not be able to drag and drop fields to the canvas. Workaround: Collapse and expand the field category and try again. |
MDMN-38312 | When you configure a custom page, if you add a custom field group that does not allow multiple instances, the field group do not work as expected in Customer 360. |
MDMN-38216 | If you configure fields to allow multiple values, the fields do not appear in Customer 360. Workaround: Delete the multiple value fields, and then create the fields again as single value fields. |
MDMN-37147 | When you manually stop or pause a running job, the job status might not update in the My Jobs page. |
MDMN-21887 | In the Explore page, you cannot use the following Action menu items to perform actions on the Business 360 application assets:
|
MDMN-21065 | If you edit the candidate selection criteria, the changes are effective only for new records. The criteria doesn't apply to the existing records. |