...
| [empty] | To match empty values for particular field. Example: field1:[empty] - will match records where field1 is empty (does not have a value, but the form defines this field) |
| [now] | Current time and date, useful with '<' and '>' for comparing with dates stored. Example: someDateField:<[now] - will match records where field 'someDateField' has value which is in the past compared to now (current time) |
| [today] | Same as [now], but without time |
| [tomorrow] | To compare against tomorrow's date. Also something like [today]+1 could be used instead |
| [yesterday] | To compare against yesterday's date. Also something like [today]-1 could be used instead |
| [dateyyyyMMdd] | To compare against given date in the format: yyyyMMdd, example: [date20150130] to give a date as Jan 30 2015 |
| [datetimeyyyyMMdd hhHH:mm] | To compare against given date with time in the format: yyyyMMdd hhHH:mm, example: [date20151231 12:13] to give a date as Dec 31 2015 12:13 |
| [datetimetoday hh:mm] | You can use a shortcut to "today" with given construction |
| '<' and '>' (and '<=' and '>=') | Can be used together with date and datetime fields, as well as to compare values for numeric fields stored |
| ! | To reverse the filter condition. Example: !field1:[empty] - will find records that have 'field1' field filled |
| :this | In *views macros you can reference current user and current page as "this" (when used to filter user (and multiuser) and page (and autopage) field types respectfully), Example:
(thepage is the field of type Page and createdBy is a metadata field to hold created by info for given record). See more about metadata field and available field types in Documentation |
...