Scenarios Invalidating the Field Visibility Rules

Field visibility rules determine when specific fields appear based on predefined conditions. However, modifying the properties of these fields can invalidate the rules, causing them to no longer function as expected. If a saved rule is later altered, it may become invalid in the following cases.

Changes to Fields Used in the Rule

Modifying the properties of fields used in a visibility rule can make the rule invalid:

• Changing the UID of the operand or target field.
• Deleting or removing the operand or target field.
• Marking the operand field as Multiple.
• Moving the operand or target field into a Group or Modular Blocks.
• Changing the data type of the operand field to an unsupported type.

Field Validations that Invalidate the Rule

Field visibility rules do not work if the target field has specific validations applied. The following validations invalidate the rule:

• Date Range: A specific start and end date
• Max Instances: For any field set as Multiple
• Limit for Multiple Choices: Restrictions on selections in a Select field
• Mandatory Field: For the field marked as Required
• Character Length: Restrictions on the maximum number of characters (e.g., A blog name restricted to 10–20 characters)
• Number Range: Restrictions on numbers to be within a specific range (e.g., A value between 10 and 15)
• Regular Expression Validation: Custom validation through regex

If a field visibility rule stops working after making changes, review these scenarios to identify the cause and update the rule accordingly.