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.

When you create an advanced rule association, the business entity output field isn't completely visible.

When you use a REST API to create a code value, levels of the hierarchical code list are not be honored.

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.

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.

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.

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.

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.