Release Notes > MDM - Reference 360 > Known issues
  

Known issues

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

November 2024 known issues

Issue
Description
RDMNEX-15946
When you enter a value in a picklist field, Reference 360 fails to retrieve relevant values because it adds a leading space to the entered value.
Workaround: Remove the leading space and then enter a value in the picklist field.
RDMNEX-15829
When you import data from a CSV file using a REST API or the user interface, Reference 360 imports code values with special characters in the business ID field instead of rejecting them.
RDMNEX-15533
When you delete a code value from a draft code list and then publish the code list, the audit trail and the code list history APIs retrieve the change events.

July 2024 known issues

Issue
Description
RDMNEX-15102
If you configure data quality rule associations to generate a Code attribute within a code list and create a code value using the codelist REST API, the REST API ignores the mandatory Code input field. If you try to create multiple code values with the same set of input values, Reference 360 doesn't display an error.
RDMNEX-14706
When you create an advanced rule association, the business entity output field isn't completely visible.
RDMNEX-14452
When you use a REST API to create a code value, levels of the hierarchical code list are not be honored.

February 2024 known issues

Issue
Description
RDMNEX-12692
When you configure an advanced rule association for an attribute and if the rule uses a single field as input and output, Reference 360 disables the attribute.
Workaround: Ensure that you configure a rule association that doesn't use a single field as input and output.
RDMNEX-12688
Reference 360 doesn't run the basic and advanced rule associations with transformation functions on the default value that you set for the code list attributes.

November 2023 known issues

Issue
Description
RDMNEX-11886
When you create a mapping with a Business 360 connection in Cloud Data Integration, the Select Source Object page doesn't display Reference 360 assets if the Secure Agent name contains spaces.
Workaround: Ensure that the Secure Agent name doesn't contain spaces.

October 2023 known issues

Issue
Description
RDMNEX-11926
When you define the scale value greater than or equal to the default precision value for a decimal data type attribute, Reference 360 doesn't display any error message.
MDMN-120973
After you change the license of an organization from full license to Reference Data Management Basic Edition license, if you create a mapping in Cloud Data Integration, you can view hierarchies of the organization with full license.