When a rule specification is modified in Cloud Data Quality, select the rule specification again or reset the fields of the advanced rule association in

Reference 360

. Otherwise, the changes to the rule specification aren't effective when the rule is executed.

If you set an attribute as input and output fields for the same advanced rule association, you can't add values for the fields that use the rule specification, on the

New Code Value

page. To add code values to a code list, you can use reference data import jobs.

When you configure an advanced rule association for a reference data field or a field that uses a reference data field, the rule considers only the code field of the referenced code value.

When you re-enable the advanced rule association for the

Code

attribute and update a field other than the input fields, you can't save the code value if the input fields were updated previously.

Disable the advanced rule association.
Revert the changes to the input fields and re-enable the advanced rule association.

By default, Cloud Data Quality uses the Date/Time format to execute rules. When you configure advanced rule associations to validate date fields in

Reference 360

, the rules consider the date based on the time zone. For example, when you configure an advanced rule association to check whether the date is earlier than the current date. The rule considers the time zone and determines the date.

An advanced rule association for a transformation function must have rule statement output values for all the conditions in Cloud Data Quality to generate values in the output field.

After you configure an advanced rule association to code list attributes, specify values in the rule applied field to run the rule and display validation error messages for code values.

When you set the code field as the output field for an advanced rule association, if you import code values, calculate the rule execution result and provide values for the code field. Ensure that the values you provide don't mismatch with the values the rule generates.

When you configure an advanced rule association for a required field, ensure that the field value doesn't depend on the value of another field that is configured with an advanced rule association.

Reference 360

doesn't guarantee the execution order of the rules.