If you apply a saved mapping during a CSV file import, the import process doesn't map the fields. If you try to apply the saved mapping again, the import process maps the fields but displays following error:

When you map population fields and run a file import job, the imported records don't display values for the population fields.

When you select a dimension, measure, and filter to create a report, the lookup values appear incorrectly with empty spaces in the drop-down list.

When you create a record through an approval workflow, the record isn't visible in the merge history activity report.

When you create standard reports and apply any date field as a filter, the report data might appear inconsistent.

When you drill down to the second level of a drill-down report that has only two levels of dimensions, the report data keeps loading instead of displaying the two levels of data.

When you enter values other than true and false for Boolean fields and search for records, the search results displays records that contain the specified values.

When you create a report that displays merge history activity and select a dimension, the dimension remains highlighted even if you change your selection.

When you create a report that displays merge history activity based on the match outcome, you can't view the number of source records merged by users that are sent for approval. These records are included in the total number of source records merged by users.

When you specify a range to filter the report data of a drill-down report, the

Data Set

panel doesn't display the search results.

A custom report that contains picklist fields doesn't display the updated field values after you update them in Reference 360.

When you open multiple records, the History tab of the records displays duplicate history feeds.

When users with a custom role try to edit a section that contains a read-only picklist, the picklist displays code instead of names.

When you run an import job,

MDM SaaS

ignores the values for the fields named as

Message Type

even though the job succeeds.

When you search for records with a search string that contains the tilde character

(~)

, business applications display an internal error.

When you try to create a record in a business application, the form might take more than three minutes to load.

When you search for records with a picklist value that contains parentheses by using a filtered search, the search results don't display the records.

When you create a record, if you add a value within double quotes or parentheses in any searchable field, a business application displays an internal error instead of listing similar records.

The search request might fail if the search text starts with, includes, or ends with a space followed by the following special characters:

When you enrich a record that contains a nested field group using a data provider, the import fails.

When you review an unmerge task in the workflow inbox, the source records appear as patch records instead of contributing records.

When a field group in nested field groups has a picklist field without any other fields, the Source Records page doesn't display the field group value.

When you try to edit or add a decimal field value that has trailing zeros and then save it, the trailing zeros are automatically removed.

When you create custom reports in an organization where the November 2023 preview functionalities are disabled, you can't create schedules to publish the reports. The issue occurs if you add facetable fields as dimensions and measures to your custom reports. Additionally, you can't view the report data on the report details page.

When you remove a parent record that contains child records from a hierarchy using the

Remove the record only

option, the child record associations aren't removed from the record. When you try to open the hierarchy of the child records, the page doesn't open.

When you preview a custom report that uses picklist fields as dimensions and measures, the preview fails with the following error:

When you add charts as widgets to individual records, the

Add Widget

button on the record details page appears disabled.

When you export the search results, you might get blank columns for the picklist fields in the nested field groups. The issue occurs when you don't have the preview feature to export the nested field group values enabled.

If you add a space followed by a hyphen in a searchable field of a record, you can't save the record.

When you update a record, the required dynamic root fields aren't validated in the sections that you don't edit.

If the related records of a record appear in a table, the

Add Filter

option might not work as expected.

When you try to unmerge a record from another record and both records have at least two related records, the records might not unmerge. The issue might occur when the business entity contains 1 million records or more.

When you import data, if the imported data contains updates to the picklist values of existing records, the import job fails.

The dependent picklist values might not change if you change the parent picklist value multiple times.

When the deduplication criteria is set for a field group and the field group IDs in records contain a period (.), only one field group entry survives even though other entries with a period (.) aren't duplicates.

When you enable the November 2023 preview functionalities of custom reports in your organization, the edit icon doesn't appear for reports that are created for individual records.

When you export records, the exported data doesn't include the

ID

column for the field groups and nested field groups that contain only picklist fields. This issue occurs when the preview feature to export the nested field group values is enabled.

When you export records with validation errors, the exported data doesn't contain error messages for picklist fields. This issue occurs when the preview feature to export records with validation errors is enabled.

When you import records with field values that contain multibyte characters, the import job fails at the transform step and the following error appears:

When you filter a report that displays validation errors of records, you can't view filter values for the types of validation errors and severity of errors.

When the operation type header in the CSV file contains space and special characters, the import process ignores the operation type values.

You can't view some fields on the dimensions, measures, and filter lists for custom reports that are based on validation errors. These fields are hidden behind the horizontal scroll bar.

When you try to stop a job during the load phase, the job stops only after the load phase completes.

When you expand a search result, the fields display incorrect values.

When you enable the November 2023 preview functionalities of custom reports in your organization, you can view, edit, and refresh report data when the fields used in custom reports are enabled as reportable.

When you create a custom report, the names of the fields that you set as dimensions appear incorrectly on the applied filters section of the

Data Set

panel.

If you create custom reports based on validation errors, the dimensions, measures, and filter lists appear empty for business entities that don't have any records.

When you export search results, you can't export nested child field groups to the CSV file.

When you try to import records into a hierarchy, if the input file doesn't contain the instance details for the records, a preview error appears.

When you run a saved search that contains configured filter values, the search results might be incorrect because some of the filter values might not be applied.

When you filter a report that displays merge history activity based on a declarative rule name, you can view the deleted rules as filter values.

When you filter a report that displays merge history activity based on declarative rule names, you might not view any declarative rules as filter values.

If you add an integer field as a measure to view the sum of all field values in your custom report, the chart doesn't render.

When you select the fields of a field group as dimensions and measures in a custom report, the report might show inconsistent data. The inconsistency appears if the field added in measures doesn't have any value.

If the input value is null for a float data type field that has an advanced data quality rule association, you don't get a warning message when you save the record.

When you import a hierarchy, if you don't map the required source primary key field for the hierarchy instance,

Customer 360 SaaS

doesn't display an error.

You can merge records even though matching is disabled for the records.

On the

Record Details

page, if you delete a field group from a record, the deleted field group appears as a duplicate field group on the

Source Records

page.

When users display the data in custom reports as pie charts, the following error appears:

When you save a custom report that contains picklist fields, the picklist field values might appear as codes in the report table and chart.

When you import values to a decimal field based on a configured precision and scale, the imported values are incorrect.

If you use nested fields to create a custom report, the report doesn't display any data.

After you delete a hierarchy and refresh the Hierarchies page, the hierarchy still appears. However, all the nodes of the hierarchy are deleted.

When you submit a record that has multiple sections in the edit mode, the required field validation might not work as expected.

When you use a REST API request to update an address of a record that contains more than one address,

Customer 360 SaaS

creates a duplicate address instead of updating the existing address.

If you don't have the required privilege to delete a field value, you get the following incorrect message when you delete the field value: