Filter Editor

The Filter Editor dialog allows you to specify filter criteria for dashboard items.

Use Filter Editor

The Filter Editor displays filter criteria as a tree where individual nodes specify simple filter conditions. The root node is the logical operator that combines all the conditions. Click this node and select the desired type to change the logical operator.

Filtering_FilterEditor_LogicalOperator

Click the plus button next to the operator to add a new condition or group.

Filtering_FilterEditor_AddConditionMenu

To set a new condition, specify the dimension (including hidden dimensions):

Filtering_FilterEditor_SelectField

Then specify a comparison operator:

Filtering_FilterEditor_ComparisonOperators

Set an operand value type in the dedicated value box:

Filtering_FilterEditor_SelectOperand

The following operand types are available:

  • Value - Allows you to compare dimension and static values.

    Filtering_FilterEditor_ValueDropdown

  • Property - Compares different dimension values.

    Filtering_FilterEditor_FieldsDropdown

  • Parameter - Allows you to compare dimension and dashboard parameter values.

    Filtering_FilterEditor_ParameterDropdown

Click the filter condition’s Remove web-filter-editor-remove-button button to delete the condition.

Advanced Mode

Advanced Mode allows you to enter a custom filter string.

Filtering_FilterEditor_TextMode

Consider the following syntax conventions when you create text-based filter conditions:

  • Insert a dimension by enclosing its name in square brackets (for example, [Category]).
  • Denote string values with apostrophes (for example, ‘Bikes’).
  • Enclose date-time values with hashtags (for example, #2019-06-01#).
  • Reference dashboard parameters by adding a question mark before their names (for example, [Category] = ?categoryParam)

This editor supports intelligent code completion (which suggests functions, parameters, and available data columns as you type).

Filtering_FilterEditor_TextMode_Autocompletion

You can add a comment to your expression to explain it and make the expression more readable. Comments can be multi-line, and begin with /* and end with */.

The Warning expression-editor-error-icon icon appears if a condition contains errors.