Rules and guidelines for advanced rule associations
Rules and guidelines for advanced rule associations
Consider the following rules and guidelines when you define advanced rule associations:
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.
To save the code value, perform one of the following actions:
Disable the advanced rule association.
Revert the changes to the input fields and re-enable the advanced rule association.
By default,
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.
To ensure the success of the comparison operation for the code value field in
Reference 360
, use integer or string values in the rule statement output of the advanced rule association. If you use a float value in the rule statement output, specify additional decimal values in the
Rule is Valid when Status Is
field.
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 for at least one of the input fields to run
the rule and display validation error messages for code values.
In
Data Quality
, you can
create a rule specification to copy the input field value to the output field if
the input field starts with
1
and set the action to
Do
nothing
if the rule statement is not valid. When you use this rule
specification in an advanced rule association, it returns an empty value for the
output field if the input field value doesn't start with
1
. To
use the input field value for the output field, edit the rule specification in
Data Quality
and change
the action
Do nothing
to
Use the Input field
.
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.