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-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-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-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-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-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. |
Issue | Description |
---|---|
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. 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. |
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-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. |
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-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-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-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"}]} |
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. |
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. |
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. |
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:
After you modify the details, you can revert the rule to the existing configuration and then save the business entity. |
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. |
Issue | Description |
---|---|
MDMN-120224 | Users might not be able to view the history of records in business applications even though you have assigned the required privileges. This issue occurs intermittently if you assign only custom user roles to users. |
MDMN-116661 | When you add an advanced rule association and select a rule that's configured in the advanced mode from Cloud Data Quality, MDM SaaS doesn't save the business entity. |
MDMN-115827 | When you apply basic data quality rule associations to the fields in a custom field group and ingress records, MDM SaaS doesn't apply the rules to the fields in the field group. |
MDMN-115743 | After you choose to read values from Reference 360 instead of reading cached reference data for picklists within field groups, the changes aren't saved. When you save the business entity, the following error appears: Unknown feature expiration. |
MDMN-113693 | When you configure an advanced rule association and map the address verifier fields to the business entity fields, MDM SaaS doesn't display the mapped business entity fields. |
MDMN-111571 | When you select a reference data from the business entity Dependencies page, the reference data doesn't open in Reference 360 and displays the following error: Code list not found. |
MDMN-111057 | If there is an empty field group nested under a field group in a business entity, you can't add the business entity to your business application. |
MDMN-110534 | When you run an ingress job through REST API, the extract step fails with the following error: [ERROR] com.mongodb.MongoSecurityException: Exception authenticating the job instance id is :846699806985666560 |
MDMN-109849 | When you import a business entity, if the source and target organizations have different source rankings with identical labels, the source ranking with the identical label in the target organization is overwritten. |
MDMN-109664 | When you create hourly job schedules on the My Jobs page, you get the following incorrect message even though the end time is later than the start time: The end time must be later than the start time. |
MDMN-99279 | If you configure data access rules for related business entities, the search service might fail in the following scenarios:
|
MDMN-97403 | You can view fields and field groups that share the same survivorship configuration but can't modify the configuration as a group. |
RDMNEX-9596 | When you migrate an egress job from a source to target organization, the egress job fails to import in the target organization. |