Release Notes > Business 360 Console > Business 360 Console
  

Business 360 Console

Fixed issues

The tables in this section describe recent fixed issues for Business 360 Console. Note that some releases might not include fixes.

October 2025 fixed issues

Issue
Description
MDMN-183336
A match and merge job that uses a match model with an extended key generation level for generating match keys for candidate selection fails.
MDMN-183310
If users create records while a Generate Search Index and Match Keys job is running, the job fails.
MDMN-181866
An egress job that uses Business 360 FEP Connector to export hierarchies fails during the extract step if node names within the hierarchies exceed 75 characters.
MDMN-180203
When you run an egress job that uses Business 360 FEP Connector to export all records and two nested field groups share the same source primary key, the exported data includes only one of those nested field groups.
MDMN-176081
When users search for records in business applications, the search result don't show the field configured as the title in the search layout components page, if the field is of integer data type.
MDMN-179583
In Operational Insights, when you filter jobs, the Reference 360 usage statistics become null.
MDMN-179392
After you update the search configuration of system fields and save and index the business entity, when users search for records in business applications, the search doesn't return any records.
MDMN-176015
When you run an egress job, the extract step takes a longer time to complete even though taskflows are run successfully in Data Integration.
MDMN-174924
When a taskflow of an egress job is suspended, MDM SaaS doesn't automatically clean up backend files related to the job. However, MDM SaaS continues to run other jobs causing performance issues.
MDMN-169707
A Search Match API request that searches for null values fails.
MDMN-167206
While you edit a business entity, if you delete it, and then try to save the changes, an error message appears. However, the save succeeds on the second attempt.
MDMN-165821
When you purge data, the job appears failed even though the Purge BE Activity Report Index step of the job still continues to run.
MDMN-156527
If you enable a field that's disabled in a business entity, and then enable the field, MDM SaaS removes the existing privileges for the enabled field.
This issue occurs only if you update privileges for another field in the same business entity before enabling the disabled field.

July 2025 fixed issues

Issue
Description
MDMN-173633
After you delete a field group entry in a business application and run an egress job, the exported data incorrectly shows the status of the field group entry as active.
MDMN-173621
If the source primary key of a field group contains invalid special characters, an ingress job fails during the load step.
MDMN-172993
Using the same internal ID for a root field and a field within a field group causes an error when you create a record in a business application.
MDMN-172885
When you run an egress job that uses Business 360 FEP Connector, the exported data doesn't contain any value for the nested field groups with names in the following format: Level<number>_<field group name>_<parentId>.
MDMN-172760
When you run a match and merge job to reset matched records for a specific business entity, the job resets matched records in all business entities.
MDMN-171395
When you try to disable an advanced rule association, MDM SaaS doesn't save the rule association and displays the following error:
Map the applied fields to an input or output rule specification field.
This issue occurs when the field configured for the advanced rule association is mapped to an output field of the rule specification.
MDMN-171327
When you use the EQUALS filter comparator, the Search REST API doesn't return records for fields that are set as searchable.
MDMN-170849
Configure a field with an advanced rule association that uses a rule specification field for the error message. If a field value fails validation, you get the rule association name instead of the error message.
MDMN-169582
When you delete an entry of a field group that's disabled from surviving as a block and configured with minimum or maximum survivorship rules, field values from the deleted entry might survive.
MDMN-168995
A business application doesn't automatically time out after the session idle timeout period.
MDMN-168981
On the View and Edit page of a business entity, when you select a field in one section, another field in a different section is incorrectly selected along with the selected field.
MDMN-167171
When you run an egress job to export deleted relationships, the job fails to export a relationship if any record in the relationship is deleted.
MDMN-157220
When you update the address values of existing records in real time, MDM SaaS doesn't enrich the address values. However, when you create records, MDM SaaS enriches the address values.
MDMN-157206
When you configure the highlighted field for a Page Header component, the Business ID system field doesn't appear for selection.
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-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-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.
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.

May 2025 fixed issues

Issue
Description
MDMN-169072
When you run a match and merge job to match source records that contain null values, the match process doesn’t generate record pairs for records with null values. This issue occurs when declarative rules use the threshold-based merge strategy.
MDMN-169066
If you update the source system of an ingress job for the second time and save the job, an error message appears.
MDMN-166766
When you add business entities to a business application, you can select disabled URL fields as display fields.
MDMN-164565
When you update a source record by using REST APIs, the rule associations for data enrichment are triggered even though you can enrich only master records.

April 2025 fixed issues

Issue
Description
MDMN-167195
When you try to remove a rule association from an objective or disable an objective, Business 360 Console stops responding.
MDMN-165203
When you run an egress job to export relationships in a hierarchy using Business 360 FEP Connector, the egress job doesn't export any records.
MDMN-165109
When you set the browser locale to Japanese, you can’t configure segment matching for declarative rules that contain Boolean fields.
MDMN-165104
You can publish a match model even if the model doesn’t contain declarative rules or a completely trained ML model.
MDMN-164343
When you migrate predefined assets, the migration fails even though the corresponding licensed business application is set up in the target organization.
MDMN-163981
You can save a business entity without specifying an internal ID for its fields.
MDMN-163716
When you run an ingress job, the transform step fails intermittently because the Cloud Application Integration processes time out.
MDMN-163682
Basic rule associations for fields in a field group with multiple picklists return incorrect values when the rule associations use one of the picklists as input.
MDMN-163607
When you render a field group as a table and fields within the field group contains errors based on the rule associations, the validation messages don't appear for the fields in business applications.
MDMN-163147
After you remove a business entity of a business application and migrate assets, the import fails because the references to the business entity isn't removed.
MDMN-161206
After you ingress records that match existing records in MDM SaaS and then run a match and merge job, the job doesn’t generate record pairs for some of the matching records.
MDMN-160917
A search reindex job fails for a business entity that has more records in deleted state than the records in active state.
MDMN-160751
When you run a Search Match API request that uses a match model with a candidate filter to match records, the API returns records that don't match the filter criteria.
MDMN-160328
When you configure advanced rule associations with transformation functions on picklists and then import records that contain invalid picklist values, MDM SaaS generates invalid picklist values, which subsequently get imported.
MDMN-159699
The Create Master Record API fails to run again when the following error appears:
Retryable transaction timeout.
MDMN-159136
When you run an ingress job, MDM SaaS doesn't run the configured advanced rule associations if the mapped field name in Cloud Data Integration contains an underscore as a prefix followed by the business entity name.
This issue occurs when business entity names start with numeric values or special characters.
MDMN-158554
When you create a reference data asset in Business 360 Console with an apostrophe (') in the display name, the asset creation page continues to load indefinitely without displaying an error message.
MDMN-158546
When you update the search configuration of a business entity and search for records using the Search REST API with a model version that's later than the current model version, the API doesn't return any results.
MDMN-158168
When you run an ingress job with a large volume of data, MDM SaaS skips the rule associations for some records. This issue occurs because of internal errors in the source and target transformations in Cloud Data Integration.
MDMN-157990
When you upgrade your organization to the latest release version and run an ingress job, the job fails at the Index for Search step with the following error:
Cannot index the records. Recreate the indexes for the Person business entity and try again.
This issue occurs because the upgrade action internally changes the business entity to the REINDEX_REQUIRED state, which requires you to reindex the records.
MDMN-157129
MDMN-162367
When users submit a record after they delete a field value in a field group, the following error appears in business applications:
Failed executing RuleAssociation:'<Rule_Internal_ID>'.
This issue occurs when you configure advanced rule associations for fields in a field group and enable the rules to run even if all input fields are empty.
MDMN-155369
When Informatica deploys the latest release updates, your organization might face intermittent errors in the Cloud Application Integration processes.
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-152976
When you configure a decimal field with a scale of 0 and import records that contain decimal values with trailing zeros, such as 1.00 or 1,00, and run an ingress job, the job imports these values without any error. However, when you edit these records in business applications, the value incorrectly appear as 1,00 instead of its actual decimal format.
MDMN-151413
When you configure a DaaS real-time rule association on address fields and create records, MDM SaaS takes about two seconds to enrich the address values after the record is created.
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-144963
The translation files don't contain any labels associated with the match and export data feature.
MDMN-141310
Custom reports that are deleted in business applications appear in Business 360 Console.
MDMN-133109
After you configure a page for each step of a custom workflow, when an approver views a create task in the Workflow Inbox, the page incorrectly shows components that aren't part of the Create page.
MDMN-130067
After you configure a DaaS rule association for real-time address verification on an address field group and map specific fields, MDM SaaS incorrectly runs the rule association on unmapped fields in the address field group. This issue occurs when you update these unmapped fields in business applications.
MDMN-65426
The Merge API can't merge master records that have more than 1000 source records.

February 2025 fixed issues

Issue
Description
MDMN-164688
When users update or unmerge records, MDM SaaS runs DaaS rule associations for real-time address verification even though the addresses remain unchanged.
MDMN-161499
In some organizations, the process hierarchies jobs fail to complete during the inherit dynamic field definitions phase.
MDMN-159683
An ingress job might reject records that contain field values in nested field groups in the load step because of incomplete field paths.
MDMN-159600
When you run the following REST API requests with an incorrect value for a picklist field, the response returns an error for a picklist field with a correct value:
  • - Create Master Record
  • - Update Master Record
  • - Update Master Record Field
  • - Update Source Record
  • - Update Source Record Field
This issue occurs when the _resolveCrosswalk parameter is set to true and the request contains multiple picklist fields.
MDMN-159574
When multiple records are open and you open a record created using a custom page that includes a custom button and you click on the button, it opens a dialog box that incorrectly shows details of another record that is open.
MDMN-159473
In Operational Insights, the usage summary metrics don't display the correct source and master records count because hierarchy records are excluded from the counts.
MDMN-159078
When a user updates the field values of records, MDM SaaS doesn't run the advanced rule associations configured for those fields and displays the following error:
Failed to update record. Failed executing <Rule Association ID>.
MDMN-158827
MDMN-157036
After you purge all records, when you create records and run an ingress or match and merge job, the job fails at the index for search step.
MDMN-158171
When you run an ingress or egress job, the job might fail without any error.
This issue occurs when a parent process in Cloud Application Integration stops running while a child process is still in progress.
MDMN-157782
When users search for or export records, the search results and the exported file display the decimal type field values that end with 0 in exponential format instead of the actual values.
This issue occurs when you set the scale for decimal fields to 0.
MDMN-157576
When you create a record using a custom page that includes header and fields components, the header component occupies more space, requiring you to scroll multiple times to view the complete record details.
MDMN-157125
When you run an egress job to export a hierarchy using Business 360 FEP Connector, the exported data excludes the child records that don't contain a default value for custom relationship attributes.
MDMN-156393
MDMN-150684
When you run an egress job to export all records, the job metrics don't display the number of records that were failed or skipped during the stage step.
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-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-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-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-145059
After a user overrides the surviving field value of a record, the user gets the following error even though their user role is assigned the read and update privileges for the field:
You don't have permission to override the trust score of <Business entity name>. Contact your administrator to review your permissions.
MDMN-143915
When you export multiple business entities with all the dependencies repeatedly, the .dat file doesn't include matchRuleSetVersion for some of the business entities.
MDMN-114643
When you customize a favicon for your organization, the configured favicon fails to appear in all business applications.
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.

November 2024 fixed issues

Issue
Description
MDMN-155624
When you run an ingress job that uses Business 360 FEP Connector to ingress a large volume of records, the extract step might take a long time to load. Additionally, the ingress job fails to import all the child records.
MDMN-154503
When you set system fields in the Source Record Details field group as searchable and save a business entity without indexing records, the ingress job fails. The failure occurs at the Index for Search step with the following error:
Index failed with status 503.
MDMN-154416
After you unmerge a record that you previously didn't enrich by accepting any recommendations, the CLAIRE panel doesn't display recommendations.
MDMN-154329
If the transform step of an ingress job times out, the job fails.
MDMN-153876
When you run an egress job that uses Business 360 Connector to export all the records, the egress job exports only a few records.
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-151953
When you run an Update Source Record Field API request with the _resolveCrosswalk parameter set to true and remove fields, the API request might fail.
(November 2024)
MDMN-151233
When you associate a code list to a picklist field in a source system and run an ingress job, the transform step fails with the following error:
The <picklist_name> field value is not found in the reference data.
This issue occurs when the associated code list is part of a crosswalk in Reference 360, and the picklist field is configured with an advanced rule association.
MDMN-150827
MDMN-150972
When a source record of a deleted master record is updated with values similar to another master record and you run a match and merge job, both master records appear as deleted records. You can't restore these deleted master records.
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-139039
If the transform step of an ingress job rejects any records, the job fails.

October 2024 fixed issues

Issue
Description
MDMN-154783
You can't relate a record to itself using a relationship when it belongs to a custom business entity.
MDMN-151323
When you delete a match model, the system automatically triggers the delete match model job. If the job fails during the Store Cleanup step, the match model page fails to open.
MDMN-151038
When you use the Export all option to egress multiple relationships, the egress job fails at the stage step.
MDMN-150166
After you delete data access rules and try to export and import authorization configuration assets from a source to a target organization, the migration fails with the following exception:
java.lang.NullPointerException: Cannot invoke "Object.toString()" because the return value of "java.util.Map.get(Object)" is null.
MDMN-150006
When you map the createdby field in the target transformation of a mapping in Cloud Data Integration, and run an ingress job, the load step fails with the following error:
The requested metadata field with name _meta.createdBy cannot be found.
MDMN-150004
When you run an ingress job or egress job, the job might stop responding during the extract step.
MDMN-149830
When users with custom user roles that are assigned only the read privilege open a record that contains a business entity field that's related to business entity record field, business applications display the following error:
Something went wrong when we tried to render this page.
This issue occurs when a business entity record field in a record contains the same record.
MDMN-149790
When you use the bulk edit option to update privileges for selected business entities, Business 360 Console overwrites the existing privileges. By default Business 360 Console, sets read and update permissions for the metadata privilege on other business entities.
This issue occurs intermittently when you refresh the Assets page after you save the bulk edit changes.
MDMN-148604
Even though a user with a custom user role has the merge privilege, the merge option might not appear on the search results and record details pages.
MDMN-148501
When you set the browser language to Japanese and configure search properties for a business entity field, the multilingual search property doesn't appear in Japanese.
MDMN-148036
When you run an egress job to export records, the job completes successfully even though an error message appears in the mapping associated with the job.
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-147612
When data is imported through a CSV file into business applications to both create and update records, the event payload contains duplicate create events for the same record.
(October 2024)
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.
MDMN-146690
When you run an Update Source Record API request that includes fields configured with a basic rule association, the API request might fail.
(October 2024)
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-144064
When you run an ingress job to create and update field values in field group entries within nested field groups, MDM SaaS removes field values from one of the entries.
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.
MDMN-143277
When you configure advanced rule associations for picklists and edit records in business applications, MDM SaaS doesn't display validation messages for picklists if the validation fails. The following error appears at the record header:
Some fields that you aren't permitted to view have errors.
This issue occurs when users run the file import job to import records into business applications.
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-143254
When you ingress a record that's related to more than 500 records, the ingress job might fail at the load step.
(October 2024)
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-141982
When you enable segment matching on picklist fields that contain more than 1000 values, the segment matching page fails to open.
MDMN-141294
Custom user roles added to a user group that contains more than 92,000 user roles in Administrator aren't visible on the Security page in Business 360 Console, even after you refresh the page.
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-130930
When you ingress records that contain source last updated dates, the load step metrics might display incorrect count of rejected records. This issue occurs when you create or update records during ingress. If an existing record doesn't have updates and contains the same source last updated date as in MDM SaaS, the count of rejected record includes the successfully created records.
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.

August 2024 fixed issues

Issue
Description
MDMN-146987
If a business event configuration uses a custom workflow for manual merge and you use a REST API with sourcePKey to merge records, an approval task is created. When an approver tries to view the task in the workflow inbox, the following message appears:
You don't have permission to view this record.
Workaround: From the page settings, delete the page layout for manual merge, save the event, and then add the manual merge action to the event again.
MDMN-145861
When you create a record with an invalid value for a field that has a DaaS rule association configured in a field group, a system error appears with validation messages. When you try to edit the field value, the system error reappears.
MDMN-145644
When you run an Update Source Record Field API request with the _resolveCrosswalk parameter set to true and root fields that aren't picklists in the request body, the API request might fail.
(August 2024)
MDMN-143035
If you search for records after you enable real-time address verification for the address field group, the State and Country values don't appear on the search results page. However, these values appear on the search results page for records created after the August release or if you update the address field.
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-138022
When you schedule multiple jobs to run at the same time, the jobs might fail at different steps because of insufficient resources in Cloud Application Integration. This issue persists even after multiple retries.
MDMN-137595
When you create a record, enter space as value in a field that has basic rule association configured with an external validation function. The field value is validated, even though it's empty.
MDMN-127589
When you search for records in business applications, the filters don't display picklist values in the correct case as configured in Reference 360.
RDMNEX-14545
When you use the Search REST API to search for records with specific keywords, the response includes some incorrect results.

July 2024 fixed issues

Issue
Description
MDMN-144374
When you export records in a business entity whose internal ID is identical to one of the field names within the business entity, the records don't get exported.
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-143289
When you run a match and merge job to match source records that contain date fields with null values, the job fails.
MDMN-142616
When you use the Update Source Record API to update the field group values that trigger approval workflows, the API request fails with the following error:
Bad Request {"errorSummary":"A validation error occurred.","errorId":"6dcaabcf-fcd2-4bc8-8fc4-b49abdf62fbc","errorDetail":{"details":[

{"message":"Unsupported codec for type NULL.","localizedMessage":"Unsupported codec for type NULL."}
]},"status":400,"errorCauses":[],"localizedErrorSummary":"A validation error occurred."}
The issue occurs only when you specify population names with the updated field group values.
MDMN-141293
Custom user roles added to a user group that contains more than 90,000 user roles in Administrator aren't visible on the Security page in Business 360 Console.
MDMN-140917
When you configure an advanced rule association for a field within a nested field group, the rule association incorrectly displays the same rule statement output for the field in its child field group entries.
This issue occurs if you enable the rule association to run even if all the input fields are empty.
MDMN-141083
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.
MDMN-140444
When you configure basic rule associations with an external validation function, the rule associations fail if any of the input field values are null.
MDMN-139698
When you add a title for a panel that contains a Dynamic Fields component, the Dynamic Fields section doesn't appear on the business applications. The issue occurs when the Dynamic Fields component doesn't contain any root fields.
MDMN-139071
When users filter search results based on the system fields, business applications don't filter the search results and display the following error message:
Suppressed: org.elasticsearch.ElasticsearchException: Elasticsearch exception [type=query_shard_exception, reason=failed to create query: Cannot search on field [_meta.lastUpdateDate] since it is not indexed.] 
This issue occurs when you enable the system fields as only facetable in predefined business entities.
Workaround: Ensure that you enable the specific system field or any other system fields within the business entity as searchable. If you don't want to enable any other system fields as searchable, run the Generate Search Index and Match Keys job twice.
MDMN-137109
When you run an ingress job, Business 360 Console ignores the values for the fields named as Message Type even though the job succeeds. This issue occurs becauseBusiness 360 Console internally uses the MessageType field to store the operation type that you specify in the Cloud Data Integration mapping.
Workaround: Ensure that you don't use Message Type as a field name.
MDMN-137065
When an egress job fails, an incorrect error message appears instead of displaying the exact reason for the failure.
MDMN-136842
When you use the Update Source Record REST API to add address values, the DaaS rule association for real-time address verification doesn't enrich the address values, and the request fails with the following error:
The patch update failed.
MDMN-136801
When you configure fields that end with _id as searchable in a business entity, users can't view these fields in the CSV file when they export the search results from business applications.
MDMN-136752
If you disable the facetable and searchable properties of a field and then you remove the field from the Facets section of the search results layout component, business applications fail to open.
MDMN-136616
When you open an advanced rule association, MDM SaaS doesn't display business entity fields mapped to output fields. If you edit the rule association and remap output fields to different business entity fields, you can't save the rule association.
This issue occurs when you add fields to a business entity, and without saving the business entity, you try to save the advanced rule associations.
MDMN-135892
When you configure an advanced rule association that uses a rule specification with the concatenate function, the rule concatenates the input field values. However, if you remove the input field values, the rule doesn't update the output field value and retains the old values.
MDMN-134373
After you remove the tip text for a field in a custom page and save the page, the tip text continues to show up.
MDMN-121910
When a user is removed from the SAML group and if the user uses single sign-on (SSO) to log in to a business application, the user can still access the components in business applications even though their role isn't authorized.
MDMN-121525
When a business entity doesn't have a self-referential relationship with itself, the dynamic field definitions of a parent record can't be enabled for inheritance in business applications.
MDMN-121418
When you run an ingress job, the job validates all the fields in a field group even if you don't map the fields configured with data quality rule associations.
MDMN-110776
When users unmerge records, the address values of the unmerged records aren't enriched even though the address fields have DaaS rule associations for real-time address verification configured.
This issue occurs when the preview feature for validation errors is enabled.
MDMN-114753
When you run an ingress job to load incremental data, the job might take longer to complete than the initial load for the same load volume.
MDMN-85558
When a user who belongs to a user role other than an administrator imports a business entity to a target organization, the import process fails.
This issue occurs when an administrator configures system fields as searchable in the source organization.

May 2024 fixed issues

Issue
Description
MDMN- 141319
The load step of an ingress job might fail if a record contains a null picklist value.
MDMN-140211
If your organization can process records with validation errors, add valid data to a field configured with a DaaS rule association for real-time address verification. The record status becomes valid even though the field shows an incorrect validation error.
MDMN-139261
When you purge records that belong to a specific business entity, the purge might take a long time and fail. Purge might fail due to a large volume of business entity records, relationship records, and historical data.
MDMN-136865
When you set conditions for business entity attributes in a data access rule, the Attribute field incorrectly displays the system fields that are enabled as searchable.
Workaround: Ignore the system fields that are listed in the Attribute field and don't create conditions based on the system fields.
MDMN-133821
When you run an egress job to export a large number of records, the job fails at the extract step.

April 2024 fixed issues

Issue
Description
MDMN-137534
When you configure an advanced rule association and add a value to any one of the input fields, Business 360 Console doesn't save the rule association.
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.
MDMN-135181
In Operational Insights, the ingress jobs of MDM SaaS that successfully ran show the count of the success records as zero.
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.
MDMN-134648
A basic rule association with an external validation function doesn't validate fields with empty string values and returns an exception.
MDMN-133707
When you match records that include records from a distinct source system, the match process might not generate few record pairs.
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.
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.
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.
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.
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.
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.
MDMN-122957
When you try to open the predefined Organization Summary or Person Summary component from the Explore page, the components fail to open.
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.
MDMN-120686
When you use single sign-on (SSO) capability to log into a MDM service that is set as default, the login fails with a 403 error. This issue occurs because MDM SaaS doesn't include .okta.com and .microsoftonline.com as valid referrers.
MDMN-116314
After you import a translation file, if you edit a custom page, some translations fall back to English.
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.
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.

February 2024 fixed issues

Issue
Description
MDMN-131931
You can't disable dynamic field definitions with a self-referential inheritance.
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.
MDMN-129712
Even though values of the fields that are set as deduplication criteria are unique in the field group entries, only one field group entry survives. The issue occurs if field group IDs contain periods(.).
(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.
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.
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.
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.
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.
MDMN-120654
You can't run an ingress job with a taskflow that uses Business 360 FEP Connector to delete a hierarchy.
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.
MDMN-117983
When you run the Search Job Instances API with the fieldName set to name, the search results aren't returned.
(February 2024)
MDMN-115671
After you import a translation file, the translations of some field validation messages are inaccurate.
MDMN-112456
When you import a custom page into an organization, some translations might not appear.
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.
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"}]}

January 2024 fixed issues

Issue
Description
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.
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.
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.
MDMN-128204
When you run an egress job that uses a taskflow with multiple mapping tasks and Business 360 Connector, the job fails.
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.

December 2023 fixed issues

Issue
Description
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.
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.
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.
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.

November 2023 fixed issues

Issue
Description
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.
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.
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.
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.
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.
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.
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
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.
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.
MDMN-117054
When you try to ingress up to 5000 records, the ingress job might stop responding at the load step.
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.
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:
  • - When the user deletes the attribute value of a relationship within the hierarchy.
  • - When the user with workflow approver privilege opens a hierarchy task on the Workflow Inbox page and adds an attribute value for a relationship within the hierarchy.

October 2023 fixed issues

Issue
Description
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.
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"]
MDMN-117629
You can't use null matching for the Search Match API.
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:
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.
MDMN-115217
When you stop a queued ingress job, the ingress job fails with an internal error.
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'.
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.
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.
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.

September 2023 fixed issues

Issue
Description
MDMN-119673
MDMN-118856
When you import a job, the import fails.
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.
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.

Known issues

The tables in this section describe known issues for Business 360 Console. Not all monthly releases include known issues.

October 2025 known issues

Issue
Description
CLDDI-45988
If your organization uses the JWT authentication type, when you start the mapping creation process in Business 360 Console, Data Integration doesn't automatically map the fields between the source and target transformations.
MDMN-189921
When you pull a renamed asset from the source control repository, the pull operation fails.
MDMN-188532
After a record fails validation by a rule association, disabling the rule association doesn't change the record’s invalid status, even though the related validation errors aren't displayed.
MDMN-187519
After you run a file import job, the load step might show incorrect values in the sub-metrics. This issue occurs when the POD runs on Oracle Cloud Infrastructure.
MDMN-186818
When you enable the option to reject records that fail validation for an objective, MDM SaaS doesn't display localized error messages even after you update the translation file with them.
MDMN-186699
When a purge job runs, the job permanently deletes records, search, and report indexes of the specified business entity during the Purge Records step. However, the job details page incorrectly displays two obsolete steps, Index for Search and Purge BE Activity Report, without any metrics.
MDMN-186460
When an objective is triggered on a master record, the list of source records that's sent to a plugin also includes the internal source records associated with relationships.
Workaround: Ignore the internal source records associated with relationships. Ensure that your business logic doesn't process those source records.
MDMN-185996
When you create basic, advanced, and DaaS rule associations in organizations created after the October 2025 release, MDM SaaS creates a predefined objective group for the business entity. The predefined objective group contains objectives with rule associations that are equivalent to the basic, advanced, and DaaS rule associations.
If you try to delete the business entity, MDM SaaS doesn't allow you to delete the business entity because of dependent rule associations.
You can't delete business entities that contain rule associations equivalent to DaaS rule associations.
MDMN-185836
When enrichment and validation rule associations run on a field that a user doesn't have access to, MDM SaaS fails to save the record with the enriched data.
MDMN-185557
When a user edits a record and applies changes to a section, all objectives associated with all fields in the section run instead of only those associated with the changed fields.
MDMN-185422
DaaS rule associations for real-time address verifications run even when users apply changes to a section instead of running only when users submit records.
MDMN-185404
The translation file doesn't include key-value pairs for objective names, so you can't localize them.
MDMN-185095
When you open a custom asset and edit its properties by updating the location, the asset is not moved to the new specified location.
MDMN-184970
After you create a data enhancement rule with the Data Quality - Validation or Transformation plugins and select a rule specification from Data Quality, if you use the same rule specification and create an advanced rule association, MDM SaaS fails to save the business entity.
However, if you create an advanced rule association first and then create a data enhancement rule with the same rule specification, the issue doesn't occur.
Workaround: Ensure that you don't create an advanced rule association and a data enhancement rule with the Data Quality - Validation or Transformation plugins using the same rule specification from Data Quality.
MDMN-184956
When you configure rule associations in objective groups that are equivalent to basic and advanced rule associations and don't enable rule associations to run even if all input fields are empty, MDM SaaS runs rule associations. However, the Data Quality Status tab in business applications incorrectly displays the status of the rule association as Success.
MDMN-184550
When you configure basic, advanced, and DaaS rule associations in organizations created after the October 2025 release, MDM SaaS creates a predefined objective group for the business entity. The predefined objective group contains objectives and rule associations that are equivalent to the basic, advanced, and DaaS rule associations.
If you import the predefined objective group into another organization, the migration fails on the first attempt.
Workaround: Try to import the predefined objective group again.
MDMN-175253
When users export search results that belong to a business entity with error remediation enabled, the exported data incorrectly includes a blank column named _id column.
MDMN-173052
The Rejected Records report that you download from the load step of an ingress or file import job doesn't include reasons for validation failures of records.

July 2025 known issues

Issue
Description
MDMN-180169
After a user updates a record in a business application, the user is able to submit the record with validation errors even though an associated objective is configured to reject records that fail validation.
MDMN-177655
When you configure a dynamic pool, if you undo a change, subsequent changes that you make aren’t saved.

April 2025 known issues

Issue
Description
MDMN-173090
When you ingress or import records, the index for search step fails if the searchable fields contain values with special characters, such as , ¦ . Subsequently, the ingress or import job fails. Additionally, the Error Records metric in the index for search step doesn't display the total number of failed records.
MDMN-168990
When you download a match output report, the download might fail, or the downloaded report might not contain the maximum number of 150,000 record pairs.
MDMN-168554
If you create a record through the business entity record API using the internal ID of a deleted business entity, the API creates the record instead of displaying an error.
MDMN-166521
An Update Source Record or Update Source Record Field API request doesn't trigger an approval workflow even though the updated fields were configured to trigger a workflow.

February 2025 known issues

Issue
Description
MDMN-156256
In Operational Insights, the usage summary metrics don't include the count of source and master records that are in MATCH DIRTY status for merge history activity report.
MDMN-156176
Validation errors might not appear when you view a record but appear when you edit the same record. This issue occurs with records that fail validations during the ingress or import process because of advanced rule associations for fields that depend on the values of other fields.
MDMN-144529
MDMN-155578
After you restore a master record, the master records count isn't updated in the MDM SaaS usage statistics that you can view in Operational Insights.
Workaround: Contact Informatica Global Customer Support.

November 2024 known issues

Issue
Description
MDMN-156186
After you merge two source records and run an egress job to export the incremental data, the exported data doesn’t display the updated business ID of the master record for the source records.
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-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.

October 2024 known issues

Issue
Description
MDMN-157663
When you search for records with the Search REST API, the request takes a longer time to retrieve a response.
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-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-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-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-144892
You can't delete or disable objective groups that you create for data enrichment.

August 2024 known issues

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-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.

July 2024 known issues

Issue
Description
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-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:
  • - Before you import the business entity, configure the additional search language on the Localization page in the target organization.
  • - After you import the business entity, if you configure an additional search language in the target organization, run the Generate Search Indexes and Match Keys job.
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-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.

May 2024 known issues

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-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.

April 2024 known issues

Issue
Description
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-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.

February 2024 known issues

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.

November 2023 known issues

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.

October 2023 known issues

Issue
Description
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.

September 2023 known issues

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.

August 2023 known issues

Issue
Description
MDMN-120863
When you filter by job types on the My Jobs page, the following issues occur:
  • - The list of job types includes duplicate entries.
  • - Some job type names aren't user-friendly and appear as internal template names.
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.

July 2023 known issues

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.

June 2023 known issues

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.

May 2023 known issues

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.

February 2023 known issues

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.

January 2023 known issues

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.

December 2022 known issues

Issue
Description
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-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.

November 2022 known issues

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.

September 2022 known issues

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-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.

August 2022 known issues

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:
  • - Upgrading business applications
  • - Importing and exporting assets

June 2022 known issues

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.

May 2022 known issues

Issue
Description
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.

April 2022 known issues

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.

March 2022 known issues

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.

February 2022 known issues

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.

December 2021 known issues

Issue
Description
MDMN-64722
The search box in a custom page does not work as expected when you configure the following user interface elements:
  • - Page header fields
  • - Education field group
  • - Display fields of the business entity
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.

August 2021 known issues

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-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.

July 2021 known issues

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.

December 2020 known issues

Issue
Description
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.