Input column: required, select a string column to validate.

Values: required, enter the values to validate against. Values are entered as plain text with each value specified on a separate line. Lines are trimmed (their leading and trailing spaces are removed) before they are considered. Ordering of values does not matter.

Ignore case: checked by default. When checked, the validation is not case-sensitive (i.e., lower-case and upper-case letter are considered to be the same). If unchecked, value comparison is case sensitive, so "red" is not the same as "RED".

Accept empty values: checked by default. When checked, empty values (see working with empty values) are considered valid. If not checked, empty values are considered invalid, and the row will be rejected.

Error message: required, configure an error message that will be associated with invalid values. The error message is displayed when hovering over an identified empty value in the data set and included as the reject reason in the reject file. Default error message is Value is not in the allowed values list.

If you have multi-line values or values with tab characters to validate, you can use escape sequences (\n, \t, etc.). For example enter Baker Street 221b\nNW1 6XE\nLondon to validate the following multi-line value:

To use a backslash itself as a delimiter, enter two backslashes.

Validation steps

Validator component in CloverDX Designer

Input column: required, a string or integer column containing credit card numbers with one card per row.

Accept empty values: configure whether an empty value is considered a valid credit card. Empty value is a value that is either null (shown as No value in data preview), zero-length string or a string composed entirely of whitespaces. By default, this is checked (i.e., empty values are considered valid).

Only the syntax of the credit card number is verified. When checking the syntax, spaces and en dashes (-) are ignored. Any other delimiter characters will cause the card number to be considered invalid.

The step does not attempt to contact any credit card or payment provider to verify the existence of the credit card number.

Running validation on an Error value does not try to validate the value and instead produces an Error right away.

Validation steps

Input column: required, a string column containing email addresses with one address per row.

Accept empty values: configure whether an empty value is considered a valid email. Empty value is a value that is either null (shown as No value in data preview), zero-length string or a string composed entirely of whitespaces. By default, this is checked (i.e., empty emails are considered valid).

The step only validates syntax of the email. It does not verify that the email (or even its domain) exists.

Running validation on an Error value does not try to validate the value and instead produces an Error right away.

Validation steps

Validator component in CloverDX Designer

Columns to validate: required, select one or more columns to test whether they are empty or not. If multiple columns are selected, all of them must have non-empty values for the row to be considered valid.

Error message: specify the error message that will be associated with the validated values of the columns that are empty. If multiple columns have empty values, all of them will be marked as invalid. This error message will be displayed when hovering over an identified empty value in the data set and included as the reject reason in the reject file. It defaults to "Value cannot be empty".

Validation steps

Validator component in CloverDX Designer

Input column: required, select a string column to validate.

Pattern: required, the regular expression to use in the validation.

Accept empty values: checked by default. When checked, empty values (see working with empty values) are considered valid. When not checked, empty values are reported as validation errors.

Error message: specify the error message that will be associated with the validated value. This message will be displayed when hovering over an invalid value in the dataset or included as the reject reason in the reject file. The default value is Value does not match regular expression.

Social security numbers: social security numbers are 9-digit numbers frequently written in three groups - for example 123-45-6789. To validate that a text column matches this format, use regular expression pattern [0-9]{3}-[0-9]{2}-[0-9]{4}. Alternatively, you can use \d{3}-\d{2}-\d{4}.

Tax identification number in Czech Republic starts with letters CZ and then contains 8 to 10 digits. This can be validated using pattern CZ[0-9]{8,10} or CZ\d{8.10}. Note that regular expressions are case-sensitive, so this expression will not match value cz12345678 while it will match CZ12345678. If you wish to also accept lower-case form of the number, you can use (?i) modifier to enable case-insensitive matching: (?i)CZ[0-9]{8,10}.

National Insurance Number in UK is formatted as two prefix letters, six digits and one suffix letter. To validate this in a simple manner, you could use expression like [A-Z]{2}[0-9]{6}[A-Z]. However, this will be only very rough validation since not all letters are allowed to be used in prefix or suffix. A more complete pattern would need to exclude certain letters to get [A-Z&&[^DFIQUV]][A-Z&&[^DFIQUVO]][0-9]{6}[A-D].

Validation always applies to whole input value. To match a substring, use wildcards like .* before and after your pattern.

Pattern matching is case-sensitive. To perform case-insensitive matching, add (?i) at the beginning of your pattern.

Validation steps

Regular expressions in CloverDX

Validator component in CloverDX Designer

Input column: required, a string or integer column containing phone numbers with one number per row.

Region: select which region to use when validating the numbers. The region defines rules that the phone numbers must follow - for example, the number of digits, prefixes, area codes, and more. Typically, regions represent countries - like the Unites States, Germany, and many others. One special region - None - is provided in case you do not have any specific regional requirements for the numbers. This region requires phone numbers to have international dialing the prefix (e.g., +1 etc.).

Accept empty: configure whether an empty value is considered a valid phone number. An empty value is a value that is either null (shown as No value in data preview), a zero-length string, or a string composed entirely of whitespaces. By default, this is checked (i.e., empty values are considered valid).

Only the syntax of the phone number is checked. The step does not try to verify that the phone number exists or is assigned to a user.

Running validation on an Error value does not try to validate the value and instead produces an Error right away.

Validation steps

Validator component in CloverDX Designer

Input column: required, select a string column to validate.

Minimum length: optional ^[1], specify the minimum^[2] value length.

Maximum length: optional ^[1], specify the maximum^[2] value length.

Accept empty values: configure whether empty values are considered empty or not. By default, this option is checked (i.e., empty values are valid).

Error message: configure custom error message that is associated with invalid values and is be displayed when hovering over an invalid value in the data preview. Default error message is Value length is outside of allowed range.

If you want to ensure that there are no trailing or leading spaces prior to the validation, use the Trim step first.

Validation steps

Validator component in CloverDX Designer

Input column: required, select a column to validate. You can select any column with types that can be sorted - string, decimal, integer as well as date columns.

Minimum value: optional^[1], enter the minimum^[2] value. If not specified, the minimum is not tested (i.e., there is no lower bound for the value).

Maximum value: optional^[1], enter the maximum^[2] value. If not specified, the maximum is not tested (i.e., there is no upper bound for the value).

Include minimum: configure whether the minimum is included in the range or not (i.e., whether the range is closed or open on the lower bound). When checked, the minimum value is included in the range - values larger than or equal to the minimum are valid. When unchecked, only values larger than the minimum are valid. By default, this is checked.

Include maximum: configure whether the maximum is included in the range or not (i.e., whether the range is closed or open on the upper bound). When checked, the maximum value is included in the range - values smaller than or equal to the maximum are valid. When unchecked, only values smaller than the maximum are valid. By default, this is checked.

Ignore case for string values: configure whether string comparisons are case-sensitive or not. If checked, the value comparison is not case-sensitive. By default, this option is checked.

Accept empty values: configure whether empty values (see working with empty values for more information) are considered valid or not. If checked, empty values are considered valid. This option is checked by default.

Error message: configure a custom error message that will be associated with invalid values. The error message is displayed when hovering over an invalid value in the data preview and is included as the reject reason in the reject file. The default error message is Value is out of allowed range.