Fixed issues

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:

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

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.

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:

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:

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:

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.

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

MDMN-143582

Even after you purge the records of a specific business entity, the number of records displayed in the merge history activity report remains unchanged.

MDMN-142579

When you enable merge history activity reports to run the Publish Reports Data job, the run time parameter in the metrics isn't available for the job.

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

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:

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.

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.

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

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

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:

This issue occurs when you enable the system fields as only facetable in predefined business entities.

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.

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:

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

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.

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.

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

MDMN-133821

When you run an egress job to export a large number of records, the job fails at the extract step.

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

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:

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

After you import a translation file, if you edit a custom page, some translations fall back to English.

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

MDMN-128594

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

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

MDMN-117983

When you run the Search Job Instances API with the fieldName set to name, the search results aren't returned.

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

MDMN-69041

MDMN-130037

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.

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

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.

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:

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

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

MDMN-117629

You can't use null matching for the Search Match API.

MDMN-116178

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:

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:

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.