Data filtering

Filter parts

A filter consists of three parts: a left-hand side value, an operator or comparator, and a right-hand side value. So you will be able to compare a certain value (or values) on the left with another value (or values) on the right.

This allows you to work with a specific subset of all available records.

Left-hand side

On the left, you can select a property of the currently chosen model. This can be either a direct property of that model or a property of a related model. Depending on the type of property you select, we display the operators that are valid for that type.

For example, when the property is a string, it makes sense to offer the `starts with` operator, while for a numeric property, it makes sense to offer operators such as `is greater than` or `is after or equal to`. Each property type has its own set of logical operators.

Operators

As mentioned in the section about the left-hand side, we offer a set of operators for each kind of property.

Property kind	Operator group
boolean boolean_expression	boolean_operators	equals is not equal to
date date_expression date_time date_time_expression time	date_operators	equals is not equal to is before is after is before or equal to is after or equal to
decimal decimal_expression integer integer_expression serial	integer_operators	equals is not equal to is greater than is less than is greater than or equal to is less than or equal to
list	list_operators	equals is not equal to
string string_expression	string_operators	equals is not equal to starts with ends with contains matches with does not match with

Right-hand side

On the right-hand side of a filter, you can select a property/variable/value to compare the left-hand side with.

Relative date filtering

When you have selected a date or datetime on the left-hand side, we offer relative values as well. Those can be:

Today
Yesterday
Tomorrow
Day before yesterday
Day after tomorrow
Three days ago
This week
Last week
Next week
This month
Last month
Next month
This year
Last year
Next year

When one of those values is chosen, we will calculate the date / datetime at runtime and use it in your filter.

The presets resolving (e.g. Today or This month) in the filters is done at the DataAPI level, server side. The current behavior of this resolving process is that it will take the local server time. It does not adhere to the client timezone time from which the actual request is coming.

We the future we envision that the preset resolving includes the client's timezone from which the query is sent.

Applying multiple filters

Often, a single property filter isn’t enough. In most cases, you’ll want to define a more specific condition. For example, if you want to see all tasks assigned to a specific user for this week, one filter won’t do the job — you’ll either get all tasks for this week, or all tasks assigned to that user.

In situations like this, you can add an extra filter row. For more advanced scenarios, you can even work with filter groups, each containing one or more filter rows.

Multiple filter rules

When you need a more specific filter, you can add additional filter rules. Each rule compares a property to a defined value. For example, you might configure a filter to show only users with active accounts who registered after a certain date and time and who also have an admin role.

Filter groups

When multiple filter rules still aren’t enough, you can use filter groups. For example, imagine two filter groups: the data table will show reminders that were created after last month with the status “In progress,” OR any reminder that was created by an admin. Each group consists of one or more rules.

When using groups, there is another operator which is important - the AND/OR operator. You can apply this operator between filter groups.

AND/OR operator

You can use the AND/OR operator between filter rules. This determines whether records must meet the criteria in all rows (AND) or in one or more rows (OR).

In this example, we’ve set two rules for the condition step. To continue along the ‘True’ path, a user must have at least one of the two email address values.