Release Notes > Business 360 Console > Fixed issues
  

Fixed issues

The following table describes the Informatica Intelligent Cloud Services Business 360 Console fixed issues. Not all monthly releases include fixed issues. The (<release>) value in each issue description indicates the release in which the issue was fixed.
Issue
Description
MDMN-135425
If a business entity contains basic rule associations with the Allowed Characters or Not Allowed Characters function, an ingress job fails at the transform step. This issue occurs when a field value contains multiple occurrences of the same special character.
(April 2024)
MDMN-135181
In Operational Insights, the ingress jobs of MDM SaaS that successfully ran show the count of the success records as zero.
(April 2024)
MDMN-134938
An advanced rule association with a transformation function validates the field values for 300 character limit even though you had set the maximum length to more than 300.
(April 2024)
MDMN-134648
A basic rule association with an external validation function doesn't validate fields with empty string values and returns an exception.
(April 2024)
MDMN-131641
When you select Allow assigning record in the hierarchy settings and set the browser locale to a language other than English, the hierarchy fails to load in the business application.
(April 2024)
MDMN-131457
After you ingress data, if you update some field values in field groups through the user interface or REST API, MDM SaaS updates only the specified field values. However, if you run subsequent ingress jobs to update field values within field groups, MDM SaaS updates the specified field values but overwrites the values of other fields within the field groups.
(April 2024)
MDMN-127655
In Cloud Data Integration, when you map a field that has an internal ID of messageType and run an ingress job in Business 360 Console, the job fails at the transform step with the following error:
Failed to execute partition: 910038515403087872p1r5_f635002f9cfe6d51, error message: Mapping generation and execution failed, Reason [SemanticLayer_10002] Cannot add field [messageType] to transformation [ROUTER]: field name already exists.
Workaround: Ensure that you don't use messageType as an internal ID for a field.
(April 2024)
MDMN-127438
When you use the STARTS_WITH comparator in a search REST API request, the response doesn't include the exact records that begin with the specified value. However, the response includes all the records that contain the specified value.
(April 2024)
MDMN-122957
When you try to open the predefined Organization Summary or Person Summary component from the Explore page, the components fail to open.
(April 2024)
MDMN-122697
When you import a search results layout component with a searchable hierarchy model into an organization, only the search results layout component and the associated business entity are imported. The configured hierarchy and its dependent assets aren't imported.
(April 2024)
MDMN-126100
When you add fields to a search results layout component, you can select the fields that are reportable even though these aren't searchable or facetable.
(April 2024)
MDMN-116314
After you import a translation file, if you edit a custom page, some translations fall back to English.
(April 2024)
MDMN-132178
An advanced rule association for a field in a field group validates empty input fields even though the rule isn't set to run on empty input fields. This issue occurs when a record contains multiple field group entries that contain input fields with values and input fields without values.
(April 2024)
MDMN-107295
If you remove the Searchable property for all the fields in a business entity, the search properties are disabled incorrectly, and you can't enable them again.
(April 2024)
MDMN-131931
You can't disable dynamic field definitions with a self-referential inheritance.
(February 2024)
MDMN-131722
When you run an egress job that uses Business 360 FEP Connector to export field groups that contain more than two levels of nested field groups, the job fails.
(February 2024)
MDMN-128594
When you configure rule associations for picklists and run an ingress job Business 360 Consoledoesn't apply the rule associations at transform step if the picklist values are removed after data standardization.
(February 2024)
MDMN-131095
When you download the rejected records from the transform step of an ingress job, the downloaded file incorrectly displays the business entity name as the picklist field names.
(February 2024)
MDMN-130927
When you run the Reset the Matched Records job multiple times on a large data set, the job might fail with the following error:
Match Reset failed with status 503.
(February 2024)
MDMN-128576
If an ingress job that uses Business 360 FEP Connector fails at the transform step, you can't download the list of skipped records and view the error descriptions.
(February 2024)
MDMN-127484
If the display name and the internal ID of a standard publish business events job aren't the same, the job publishes all events instead of new events in subsequent runs.
(February 2024)
MDMN-120654
You can't run an ingress job with a taskflow that uses Business 360 FEP Connector to delete a hierarchy.
(February 2024)
MDMN-118407
Ingress jobs fail at the transform step with an error if the internal ID of a field group includes the internal ID of its business entity.
(February 2024)
MDMN-115671
After you import a translation file, the translations of some field validation messages are inaccurate.
(February 2024)
MDMN-112456
When you import a custom page into an organization, some translations might not appear.
(February 2024)
MDMN-105538
A relationship attribute of decimal data type displays only two digits after the decimal point for the related records even though the configured values have more than two digits.
(February 2024)
MDMN-69041
An ingress job might result in some rejected records with an error similar to the following error:
{"details":[\{"message":"Write conflict encountered.","localizedMessage":"Write conflict encountered.","path":[],"code":"BES.00012.3"}]}
(February 2024)
MDMN-130037
To import a large data set, run an ingress job by using Business 360 FEP Connector. The sourceLastUpdateDate field for some of the records might display the current date and time when the ingress job was run instead of the last updated date of the source records.
(January 2024)
MDMN-129516
When you run an egress job that uses Business 360 FEP Connector, the exported data doesn't include any values for the business entity record fields.
(January 2024)
MDMN-129248
In a business entity, if the internal ID of a text field is similar to the internal ID of a picklist, the text field appears as a picklist on the filtered search page.
(January 2024)
MDMN-128204
When you run an egress job that uses a taskflow with multiple mapping tasks and Business 360 Connector, the job fails.
(January 2024)
MDMN-126445
When you export hierarchies that contain multiple child nodes by using Business 360 FEP Connector, the job exports only the first-level records.
(January 2024)
MDMN-126087
When a relationship has multiple attributes that are picklists with default values, you might not be able to save changes to the default value settings. The following error appears:
Something went wrong when we tried to render this panel.
The issue occurs when a relationship has multiple attributes that are picklists with default values.
(November 2023)
MDMN-125168
When you configure user-triggered business events for record updates, approval tasks might not be created for some changes to field group values.
(December 2023)
MDMN-125091
An ingress job fails at the load step if the fields configured with data quality rule associations have values that contain special characters.
(December 2023)
MDMN-123922
After you import a business entity with survivorship configuration based on other fields, the Rules column on the Survivorship tab doesn't display those field names.
(December 2023)
MDMN-122180
If you update the search properties of a field that is used in a search results layout component, your business application fails to launch.
(December 2023)
MDMN-123049
When you modify the value of a boolean field configured with an advanced rule association that uses the rule statement output as Do nothing in Cloud Data Quality, MDM SaaS doesn't run the rule and displays an error.
(November 2023)
MDMN-122972
Ingress data into a business entity that contains a field group with five or more levels of nested field group. If the source primary keys exceed the allowed 255 characters, the ingress job fails at the transform step.
(November 2023)
MDMN-122654
When you add or edit values for a field that isn't configured with an advanced rule association, MDM SaaS runs the rule association configured for the other fields.
(November 2023)
MDMN-122080
MDMN-124559
When you edit a business event that's triggered for specific fields, an error might occur if a rule checks fields for values from a picklist.
(November 2023)
MDMN-121993
When a delete task is pending for a master record, if you ingress an update to the master record, the master record with the pending delete task becomes active instead of pending update. If you run an egress job to export the master record, the job fails at the staging step with the following error:
E11000 duplicate key error collection
(November 2023)
MDMN-122107
When you ingress data that contains invalid picklist values and source primary keys exceeding the allowed 255 characters, the job fails at the load step.
(November 2023)
MDMN-120539
When you run an advanced rule association for a field in a nested field group to remove any special characters, the rule doesn't remove the special characters.
(November 2023)
MDMN-117469
After you run an ingress job, when you download the error report from the transform step, the custom message for the advanced rule association is truncated if the rule statement output returns an integer data type.
(November 2023)
MDMN-117054
When you try to ingress up to 5000 records, the ingress job might stop responding at the load step.
(November 2023)
MDMN-110902
When you add or edit the field values in an address field group that's configured with a combination of advanced rule association and real-time DaaS rule association, the DaaS rule validation fails.
(November 2023)
MDMN-77212
When you stop an ingress job during the extract phase, the taskflow does not stop and continues to run in Cloud Data Integration.
(November 2022)
MDMN-120239
In an advanced rule association, if you add a hyphen character to the custom message description, the hyphen character doesn't rendition properly in a business application.
(October 2023)
MDMN-119069
When you run an ingress job, and the internal ID of a picklist starts with an integer, the transform step fails with the following error:
["Failed to execute partition: 876494343006298112p1r5_3decff40e40a2c11, error message: Disnext_internal_error_java.lang.reflect.UndeclaredThrowableException"]
(October 2023)
MDMN-117629
You can't use null matching for the Search Match API.
(October 2023)
MDMN-116178
When the block survivorship functionality is available for preview, you can't override the survivorship configurations of individual fields with that of the business entity level configuration. The following error appears:
Invalid survivorship configuration. Configure block survivorship for the following field groups:
(October 2023)
MDMN-116216
When you concurrently run multiple Create Master Record API requests with the same payload through different applications, some requests might fail with an error instead of updating the master record.
(October 2023)
MDMN-115217
When you stop a queued ingress job, the ingress job fails with an internal error.
October 2023
MDMN-106886
MDM SaaS doesn't run an advanced rule association that uses rule statement output as Do nothing in Cloud Data Quality and displays the following error:
Failed executing RuleAssociation:'datenull_168447823737'.
(October 2023)
MDMN-74672
After you import a file, run the match and merge job, and again import the file with a different source system. The total number of matched records is not the same when you import the file with a different source, run the match and merge job, stop the job, and run the Recover a failed job.
(October 2023)
RDMNEX-11225
When you add a description for a job in Reference 360, the updated job description doesn't appear in the Reference360 project folder in Business 360 Console.
October 2023
MDMN-123943
When you configure advanced rule associations that use dictionary assets, the rule fails in some of the environments with the following error:
Failed executing RuleAssociation:'DataDictionaryRule_1692858314583'.
Workaround: To run the rule association successfully, perform one of the following steps:
  • - Delete the existing rule, and add a new rule.
  • - Open the existing rule, modify the output fields or any other details on the Validation tab, and save the business entity.
  • After you modify the details, you can revert the rule to the existing configuration and then save the business entity.
(October 2023)
MDMN-119673
MDMN-118856
When you import a job, the import fails.
(September 2023)
MDMN-118289
When you refresh the usage summary of MDM SaaS in Operational Insights, the job instances associated with the refresh don't trigger immediately.
(September 2023)
MDMN-102515
When you navigate to pages such as Explore, Business Events, and Security, after you try to edit the survivorship properties of a business entity field, their page headers don't appear.
(September 2023)
MDMN-120224
Users might not be able to view the history of records in business applications even though you have assigned the required privileges. This issue occurs intermittently if you assign only custom user roles to users.
(August 2023)
MDMN-116661
When you add an advanced rule association and select a rule that's configured in the advanced mode from Cloud Data Quality, MDM SaaS doesn't save the business entity.
(August 2023)
MDMN-115827
When you apply basic data quality rule associations to the fields in a custom field group and ingress records, MDM SaaS doesn't apply the rules to the fields in the field group.
(August 2023)
MDMN-111571
When you select a reference data from the business entity Dependencies page, the reference data doesn't open in Reference 360 and displays the following error:
Code list not found.
(August 2023)
MDMN-115743
After you choose to read values from Reference 360 instead of reading cached reference data for picklists within field groups, the changes aren't saved. When you save the business entity, the following error appears:
Unknown feature expiration.
(August 2023)
MDMN-113693
When you configure an advanced rule association and map the address verifier fields to the business entity fields, MDM SaaS doesn't display the mapped business entity fields.
(August 2023)
MDMN-111057
If there is an empty field group nested under a field group in a business entity, you can't add the business entity to your business application.
(August 2023)
MDMN-110534
When you run an ingress job through REST API, the extract step fails with the following error:
[ERROR] com.mongodb.MongoSecurityException: Exception authenticating the job instance id is :846699806985666560
(August 2023)
MDMN-109849
When you import a business entity, if the source and target organizations have different source rankings with identical labels, the source ranking with the identical label in the target organization is overwritten.
(August 2023)
MDMN-109664
When you create hourly job schedules on the My Jobs page, you get the following incorrect message even though the end time is later than the start time:
The end time must be later than the start time.
(August 2023)
MDMN-97403
You can view fields and field groups that share the same survivorship configuration but can't modify the configuration as a group.
(August 2023)
MDMN-99279
If you configure data access rules for related business entities, the search service might fail in the following scenarios:
  • - A user with the custom user role searches for records in the business application that has a data model with large volume of related business entity records.
  • - Multiple users with the same custom role search for records simultaneously in the business application that has a data model with large volume of related business entity records.
(August 2023)
RDMNEX-9596
When you migrate an egress job from a source to target organization, the egress job fails to import in the target organization.
(August 2023)
RDMNEX-9924
When you modify the name of a code value in Reference 360, the existing records don't display the updated name.
(July 2023)
MDMN-109715
A basic rule association with the external validation function incorrectly encodes special characters in field values twice in the URL.
(July 2023)
MDMN-107202
After you update code values that are used in picklists, the edited records don't reflect the updated code values.
(July 2023)
MDMN-104592
The tasks for edited records render incorrectly on the Workflow Inbox page for custom user roles with the approver privilege. This issue occurs if a data access rule has a condition on attribute values for these user roles. If the attribute value that is specified in the data access rule is updated in a record, the edited attributes incorrectly appear as deleted on the task details page of the edited record.
(July 2023)
MDMN-96660
After you add a field to a field group, if you map the field to an existing DaaS rule association, Business 360 Console doesn't display the mapped field.
Work around: After you add a field to a field group, save the business entity.
(July 2023)
MDMN-94367
A user can view a business entity record field even though you didn't assign read privilege to the user. The business entity record field incorrectly appears in the related records component in your business application.
(July 2023)
MDMN-89883
When you use a PATCH request to remove a field group, you can view the fieldData details, such as reference path and last updated date.
(July 2023)
MDMN-77342
After you edit a reference data asset that you create in Business 360 Console in Reference 360, the import of this asset after an export fails.
(July 2023)
MDMN-108315
After you upgrade to the April 2023 or May 2023 release, the source ranking assigned to some of the source systems in the survivorship configuration might change automatically.
Workaround: Modify the source ranking of the affected source systems manually in the survivorship configuration.
(June 2023)
MDMN-108035
When you run an ingress job to import duplicate relationships, the job fails with an error.
(June 2023)
MDMN-106037
When you match less than 1000 records, records updated in a business application might not participate in the match process. The issue occurs when the match model is configured to filter candidates or perform segment matching, and the records are not ready to match or use multiple populations.
(July 2023)
MDMN-104538
When you modify a rule specification in Cloud Data Quality, the advanced rule associations that use the updated rule specification don't reflect the changes.
Workaround: To use the modified rule specification, open the advanced rule association, and perform one of the following actions:
  • - On the Validation tab, modify any field and save the rule association.
  • - On the Input and Output Fields tab, modify the input and output field mappings and save the rule association.
  • - On the Rule Specification field, select a new rule and save the rule association. After you save the rule association, edit it, and select the previous rule specification.
(May 2023)
PXM-5320
After you configure a business event to use optional workflow, you can then configure specific fields for which you want to trigger a workflow. When the users create or update those selected field values in the business application, they see only the Submit button, but not the Send for Approval button. When they click the Submit button, the workflow gets triggered and creates approval tasks.
(May 2023)
MDMN-103767
When users with custom user roles use filtered search to search for records in the business applications, the check box adjacent to each record on the search results page might not appear.
Workaround: To view the check box for records, refresh the search results page.
(May 2023)
MDMN-102506
MDMN-105060
When the input file contains no records, the ingress job fails at the transform step with the following error:

[\{"path":"INGRESS.0004.003","isClientError":false,"errorCode":"Index:
0, Size: 0","clientError":false,"message":"Index: 0, Size: 0"}]
(May 2023)
MDMN-98668
You can't stop a queued job.
(May 2023)
MDMN-97909
When you create a data access rule to hide a business entity record field, the records still display the field value in the following format:
<Business Entity Name>-<Internal ID of the related record>
When you try to open the related record, you get the following message:
Authorization cannot be granted.
(February 2023)
MDMN-97525
In an organization that uses real-time address enrichment, if the user updates invalid address for multiple records at a time, the business application doesn't display the warning dialog box.
(May 2023)
MDMN-97432
In a data access rule, if you create two similar conditions for duplicate parent picklist attributes and a condition for the dependent picklist attribute, if you delete one of the parent picklist attribute conditions, the dependent picklist attribute condition is also incorrectly deleted.
In a data access rule that contains a pair of conditions for parent and dependent picklist attributes, if you create a third condition similar to the existing parent condition that uses the duplicate parent picklist attribute, the condition of the dependent picklist attribute is incorrectly deleted.
(May 2023)
MDMN-95329
The records that have multiple values for the filter value selected in the candidate selection criteria, don't participate in the matching process.
(May 2023)
MDMN-94282
When a user with a custom user role, opens a task on the Workflow Inbox page, if the user doesn't have read privilege to the relationship associated with the task, the following errors occur:
  • - The following incorrect message appears:
  • Authorization cannot be granted.
  • - The page keeps loading.
(May 2023)
MDMN-86649
When you add pages to a business application, the Add Page icon on the Pages tab might not work as expected.
(May 2023)
MDMN-47450
If users edit records in Customer 360, the edits cause the match process to generate incorrect matches.
(May 2023)
MDMN-106475
When the business entity name is the display name of a field that you include in the search results layout, the following issues occur in business applications:
  • - Instead of record names, business entity names appear in search results.
  • - The field that has the business entity name as the display name appears blank on the search results page.
(April 2023)
MDMN-101997
If you disable the search properties that you previously enabled for the system fields of a custom business entity, the search results page in the business application displays the system field names in an incorrect format.
(April 2023)
MDMN-101630
If you disable the previously enabled search properties for the system fields of a business entity, you can't remove these system fields from the search results layout. The System Fields list appears disabled in the search results layout.
Workaround: If you edit the properties of any other field that is not a system field, on the search results layout of the business entity, the system fields automatically disappear.
(April 2023)
MDMN-101609
If you choose to show the system fields for a custom business entity on the Attributes tab and navigate to the Match or Events tab, the fields panel incorrectly appears enabled for the basic fields when you return to the Attributes tab.
(April 2023)
MDMN-101518
If you expand a field group for a business entity and then choose to display the system fields on the canvas, the system fields don't appear as expected, and the field group appears instead.
Workaround: Expand the field group to view the system fields.
(April 2023)
MDMN- 99137
If you use a PATCH request for multiple operations, such as add or replace for a field group, only the first operation completes successfully, and the remaining operations fail.
(April 2023)
MDMN-100865
The business application doesn't display the system fields in the same order you add them to the search layout.
(April 2023)
MDMN-98515
The system queues jobs that require resources beyond the allowed limit and doesn't process other jobs.
(April 2023)
MDMN-97936
When you try to open any search layout in Business 360 Console, the page might not open. The page appears to load indefinitely.
(April 2023)
MDMN-97751
An ingress job fails if the source primary key field contains any special characters other than the following supported characters:
.~!/'={}|:@#$^&*()-_+,<>?`
(April 2023)
MDMN-97591
The data access rules to protect attributes in nested field groups don't work as expected if the protected attribute is at the second or higher level of the nested field group. The values of the protected attributes appear incorrectly on the record details page for the user with the custom user role even though the data access rule denies access to these attributes.
(April 2023)
MDMN-97442
An attribute-level data access rule with conditions to protect an attribute doesn't work as expected. The Matched On tooltip text on the search results page of the business application incorrectly displays the protected attribute based on which the search results are rendered for the custom user role.
(April 2023)
MDMN-97390
When you edit a record and save the changes, Customer 360 SaaS doesn't save the changes because it considers the Default source system instead of Informatica Customer 360.
(April 2023)
MDMN-97374
In an attribute-level data access rule, if the protected attribute is a field with multiple values, the rule works as expected for master records but doesn't work as expected for source records. When a user with the custom user role searches for records in the business application, the protected attribute appears incorrectly on the source records tab even though the rule denies access to the protected attribute.
(April 2023)
MDMN-94482
When you disable a field in a field group that is configured with real-time address verification, the Field Dependencies dialog box doesn't display the name of the dependent objects.
(April 2023)
MDMN-94318
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.
(April 2023)
MDMN-93859
When you create a nested field group, the properties section displays the Data Quality tab even though it must not appear.
Workaround: Save the business entity. The Data Quality tab disappears.
(April 2023)
MDMN-93662
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)
MDMN-93378
When you enable a DaaS rule for real-time address verification, Business 360 Console doesn't disable the basic and advanced rule associations for the fields in the field group.
(April 2023)
MDMN-91962
When you add an advanced rule association to concatenate two fields that contain more than 100 characters, the rule output displays the first 100 characters of the fields.
(April 2023)
MDMN-69793
For a user with custom user role, if you do not assign the read privilege for the name fields of business entities associated with the hierarchy, the user gets an incorrect error message in the following scenarios:
  • - When the user opens an existing hierarchy record from the business application.
  • - When the user tries to add a root record or relationship for a hierarchy.
  • - When the user expands the parent record of a hierarchy.
  • - When the user opens the Hierarchy tab of a hierarchy record in the business application.
In all these scenarios, the user gets the following error message instead of displaying the business entity name as expected:
Forbidden: Insufficient rights Cannot retrieve the entity records of business entity <business entity name> with provided filter.
(April 2023)
PXM-5334
When a workflow trigger is configured on fields of a nested field group, the workflow may trigger even if other fields of the nested field groups are changed.
(April 2023)
PXM-5314
The options to view, edit, or delete field level workflow triggers appear for all actions including delete, merge and unmerge. Field level workflow triggers are applicable only for create and update actions. Workflows configured for delete, merge or unmerge actions are ignored.
(April 2023)
MDMN-98504
You can define picklist attributes for a hierarchy. When a user tries to filter the records in a hierarchy based on the picklist attributes, the list of picklist attributes doesn't appear properly.
(March 2023)
MDMN-97739
When users try to open a predefined search results layout or an existing search results layout that they created, the page might not open.
(March 2023)
PXM-5473
When you configure a business event to trigger a workflow with multiple rules applied to a field for an event scenario, the workflow isn't triggered when all rules are met.
(March 2023)
PXM-5337
Custom users roles might be able to see business entity fields without having read access to the attribute metadata when editing fields.
(March 2023)
MDMN-97829
If the business ID field isn't searchable, but is included in the search results layout, the business application displays the business ID on the search results page.
(February 2023)
MDMN-97540
If you create data access rules for a business entity that has duplicate fields or field groups, the search requests fails for custom user roles in the business application.
(February 2023)
MDMN-94687
When you create a DaaS rule association for real-time address verification, the input and output field mapping displays the disabled fields in the field group. If you map the disabled fields and save the rule association, the DaaS rule association isn't displayed for the field group, and you can't add another DaaS rule association.
Workaround: Don't include disabled fields in the field mapping.
(February 2023)
MDMN-94573
You can't change the predefined translations for the Source Records section.
(February 2023)
MDMN-94157
When you set a business entity record field as a display field for a business entity, the field value appears as [object,object] in your business application.
(February 2023)
MDMN-92858
When you configure a related records component to display records related through a business entity record field, you can select the fields that you want to display in the component. If you delete or disable any of these fields, an error message to prevent the action doesn't appear. The attribute is deleted or disabled.
(February 2023)
MDMN-92612
When you try to log out or navigate to another service from Business 360 Console, a warning message appears. The message states that the changes you made may not be saved and requires you to confirm whether you want to leave Business 360 Console. The message appears even if you didn't make any changes in Business 360 Console.
(February 2023)
MDMN-91922
When you use a PATCH request without the last updated date of the source system to update a field value with the same value, a validation error for the source last updated date field appears.
(February 2023)
MDMN-90421
When the last updated date of a field group in the source system is equal to an older date or the current date, you can't use a PATCH request to remove the field group.
(February 2023)
MDMN-90420
You can't use a PATCH request to remove a nested field group from a source record. If you use a PATCH request, the last updated date of the field group changes in the source system.
(February 2023)
MDMN-60554
You cannot delete a published match model.
(February 2023)
MDMN-95956
When you configure a data model for a business application or try to import assets or projects into the organization without provisioning the predefined assets, the metadata gets corrupted.
Workaround: Provision the business application and try again.
(January 2023)
MDMN-94665
To import relationship data, run an ingress job that uses a Business 360 FEP connection in the Cloud Data Integration mapping with the from_buinessEntity_id and to_buinessEntity_id fields mapped. The job doesn’t import any records.
(January 2023)
MDMN-89873
You can use a PATCH request to update the last updated date of the source system for a field without passing a field value.
(December 2022)
MDMN-64235
If you sort the assets of a file that appear on the Import Assets page after selecting the assets to import, all the assets are selected.
(December 2022)
MDMN-85972
When you run the Search Match API with a match model that contains threshold-based match rules, the match model name, version, and population don't appear in the API response.
(November 2022)
MDMN-85851
When you run the Search Match API without specifying a match model and without setting a default match model in Business 360 Console, the API response might be incorrect.
(November 2022)
MDMN-53397
When a boolean field name ends with colon (:), the field name appears incorrectly in the business application.
(November 2022)
MDMN-63024
A user with a custom user role can continue to approve or reject the existing tasks even after you revoke the approver privilege and assign requester privilege for that user role. However, the business application fails to save the approved and rejected records.
(October 2022)
MDMN-83680
When you import records with the same source primary keys and source system into separate business entities, if one of the business entities has a published match model, matching might not work as expected.
(September 2022)
MDMN-83527
When a match training job fails because of an internal error, the Train and Prepare Batch step does not show the failure status. The following incorrect error message appears:
<h1>MATCH_TRAINING_FAULT</h1> <h2>XQuery variable fault is not initialized.</h2>
(September 2022)
MDMN-83410
When you create a business entity within the MultidomainMDM > Multidomain MDM business application and navigate to the Pages tab, you don't see the auto-generated page under the Create tab.
Workaround: To view the auto-generated page, click Add Page.
(August 2022)
MDMN-79530
The Search Job Instance API doesn't search the job instances based on multiple job types or job statuses as expected.
(August 2022)
MDMN-79407
When you provision a new organization for Supplier 360, an invalid business event is created, which doesn't allow reviewers to approve tasks that business users submit.
(August 2022)
MDMN-79189
When you ingress data with the Korean population and select the Company_Name field type as the candidate selection criteria, match tokenization fails.
(August 2022)
MDMN-65727
When you run an ingress job to import large number of records into a data model that contains eight or more field groups, the ingress job fails at transform step.
(August 2022)
MDMN-46965
After you create an ingress job, you cannot update the location of the job.
(August 2022)
MDMN-77865
When a custom user role imports a file to a business entity and if the business entity uses an advanced rule association to validate data, the user might get the following error:
{"localizedErrorSummary":"Failed to execute 1 partition","errorCode":"500","errorDetail":["[\"Failed to execute partition: 711119287103836160p1r5_0547011267879844, error message: Disnext_internal_error_java.lang.reflect.UndeclaredThrowableException\"]"],"errorSummary":"Failed to execute 1 partition"}
Workaround: Enable permission to create, read, update, and run mapplet asset type for the custom user role in Administrator.
(June 2022)
MDMN-77551
When you create a match and merge job, the Match and Merge job description incorrectly displays content about the reset job for the matched records.
(June 2022)
MDMN-72518
When you save a declarative rule with automatically added uniqueness criteria fields in a match model that you copied from a baseline model, you get an internal error.
(June 2022)
MDMN-72127
A user with the custom user role gets incorrect messages on the Workflow Inbox page in the following scenarios:
  • - When a user who has partial or no access to relationships associated with a hierarchy tries to open the updated hierarchy task sent for approval, the user gets the following message:
  • There are no changes.
  • - When a user who does not have the read privilege for a root business entity associated with the hierarchy tries to open the updated hierarchy task sent for approval, the user gets the following message:
  • Forbidden: Insufficient rights Cannot retrieve the pending relationship records of type c360.organization.
  • - When a user who does not have the read privilege for a root business entity associated with the hierarchy tries to open the hierarchy task for creating or deleting the hierarchy data, the user gets the following message:
  • There are currently no records in this hierarchy.
(June 2022)
MDMN-71635
When you copy a match model that contains declarative rules with only automatically added uniqueness criteria fields, you get an internal error.
(June 2022)
MDMN-72196
When you run an egress job to export large number of business entity records, the stage step fails with the following error:
<h1><EGRESS_STEP_FAULT></h1><h2>HTTP method: POST Gateway Time-out </h2>
(May 2022)
MDMN-71440
When you create and save an egress job, the Run button is not enabled as expected.
Workaround: Close and reopen the egress job to enable the Run button.
(May 2022)
MDMN-71029
When the business entity fields contain basic and advanced rule associations, the information and warning messages appear only for the fields that contain basic rule associations.
(May 2022)
MDMN-69361
When you open a Business 360 asset after an upgrade to your organization, the following error might appear:
Something went wrong when we tried to render this page.
(May 2022)
MDMN-68407
If you export hierarchy data that contains relationships with updated attribute values, the updated attribute values appear only in the root output file. The xref output file contains the existing attribute values instead of the updated attribute values.
(May 2022)
MDMN-57000
When you ingress records that contain # in the source primary key value, the Source Records tab doesn't render in Customer 360.
(May 2022)
MDMN-38915
If the name of a root field in a business entity contains only numerals, the file import process fails with the following error message:
2020-12-01T13:35:56.110+00:00 <getThreadPoolTaskExecutor-270> SEVERE: Data integration service failed to create DTM instance because of the following error:
com.informatica.platform.ldtm.util.expr.ExpressionUnparseableException: [EXPR [4_pass] ERROR [<<PM Parse Error>> missing operator
... 4<<<<_pass] WARNING []]
(May 2022)
MDMN-72368
If a declarative rule contains only automatically added uniqueness criteria fields, you get an internal error in the following scenarios:
  • - When you add a fuzzy match declarative rule, navigate to the Add Optional Fields tab and save the rule without adding an optional field.
  • - When you edit a fuzzy match declarative rule, navigate to the Add Optional Fields tab and try to navigate back to the Configure Properties and Thresholds tab without adding an optional field.
(April 2022)
MDMN-71971
Users with custom user roles cannot view the history of records when they click the History tab.
(April 2022)
MDMN-69907
When you save a Merge Only job, you get the following error:
Cannot save the job definition. Select the required values and try again.
(April 2022)
MDMN-69406
The match model configuration allows you to save a duplicate candidate selection criteria instead of displaying an error message.
(April 2022)
MDMN-69396
When you update a declarative rule for a published match model, you get an internal error instead of a new match model version.
(April 2022)
MDMN-68530
If you rename the display name of an egress job, you get the following error when you save the job:
Metadata object version not found. The version is required if you update or delete an object.
(April 2022)
MDMN-68481
When you create an egress job of custom export type, if you use the current date that is selected by default in the Select Date dialog box, you get the following message:
Select the Date
(April 2022)
MDMN-68456
The egress jobs might fail intermittently with the following error:
Failed to parse taskflow input parameter
Workaround: Try again later.
(April 2022)
MDMN-68327
If you import data that contains one or more records without any other field values except the required sourcePkey, parentID and sourceSystem field values, the ingress job fails with the following error:
Failed to execute partition.
(April 2022)
MDMN-67816
On the user role details page that you access from the Security page, if you find an asset using the search box and select it using the Select All option, you get the details of the asset selected by default instead of the currently selected asset.
Workaround: Manually select the asset to view the details.
(April 2022)
MDMN-63023
If you revoke the workflow requester and workflow approver privileges for custom user roles or if you delete or rename the custom user roles in Administrator, you might notice the following issues with the existing tasks:
  • - The user with a custom user role doesn't get any notification regarding the revoked privileges when accessing their existing business events.
  • - The custom user roles such as those mentioned above don't appear in the Affected User Roles list on the Business Events page.
  • - The Affected User Roles column on the Events page displays the custom user roles such as those mentioned above even after their privileges are revoked.
(April 2022)
MDMN-49924
Before you set up your application, you might be prompted to upgrade it on the Home page of Business 360 Console.
Workaround: Skip upgrading the application until you set it up.
(April 2022)
MDMN-38913
When you search for a job instance on the My Jobs page, the search results don't appear on the first page as expected. After you search for a job, the number of job instances resulting from the search and the pagination is incorrect.
Workaround: Navigate to each page to view the search results.
(February 2022)
MDMN-66988
When you open the Multidomain MDM application on the Explore page, the Help check box in the Application Header section displays an editable checkbox instead of help link.
(January 2022)
MDMN-61733
You cannot use attribute names or internal IDs that start with an underscore (_) in REST API requests.
(December 2021)
MDMN-44181
When a field exists in a mapping saved for importing files and you try to delete the field, the error message that appears does not contain helpful information.
(December 2021)
MDMN-61486
A search result layout component does not support the rules configured for the boolean, picklist, and date and time fields.
(November 2021)
MDMN-51199
When you ingress data that contains decimal values with a precision of more than 28, the advanced rule associations do not work as expected.
(July 2021)
MDMN-64915
When you run an ingress job, if the status of the associated taskflow execution is suspended in Cloud Data Integration, the job status appears as Running instead of Failed.
(May 2021)
MDMN-38057
After you select a taskflow for an ingress job, if you update the taskflow in Cloud Data Integration and do not publish, the job fails upon execution.
(December 2020)
MDMN-37289
When you open an advanced rule specification from the Data Quality page, and try to save your changes, the changes are not saved.
(December 2020)
MDMN-35995
You cannot use same names separated by period (.) for two business entities. For example, if you name a business entity as ABC, you cannot name another business entity as A.BC.
(December 2020)
MDMN-35991
When a job fails, the job status might not update in the My Jobs page.
(December 2020)
MDMN-29293
When you configure a basic rule association on a business entity field that is not visible when you create or update records in Customer 360, the validation failure message does not appear.
(December 2020)
MDMN-23752
After you associate a data quality rule with the fields of a business entity, if you update the rule in Cloud Data Quality service, the data quality rule might not work as expected in Customer 360.
(September 2020)