a!recordFilterDateRange( name, field, isVisible, defaultFrom, defaultTo )
Creates a user filter for a record list.
| Keyword | Type | Description |
|---|---|---|
|
|
Text |
Name of the date range user filter. |
|
|
Record Field |
The record field or related record field the filter will apply to. |
|
|
Boolean |
Determines whether the filter is visible to the user. Default is |
|
|
Date |
Determines the default start date, if any, for the date range filter. |
|
|
Date |
Determines the default end date, if any, for the date range filter. |
Facet
This function creates a Facet type object, and is used within a Record Type Object for creating and configuring date range user filters.
1
2
3
4
5
6
7
=a!recordFilterDateRange(
name: "Hire Date",
field: recordType!Employee.fields.hireDate,
defaultFrom: "today()",
defaultTo: "today() + 365",
isVisible: true
)
See Expression-Based User Filters for common uses.
| Feature | Compatibility | Note |
|---|---|---|
| Portals | Partially compatible | Can be used with Appian Portals if it is connected using an integration and web API. |
| Offline Mobile | Partially compatible | Can be used with offline mobile if it is loaded at the top of the form. |
| Sync-Time Custom Record Fields | Incompatible | |
| Real-Time Custom Record Fields | Incompatible | Custom record fields that evaluate in real time must be configured using one or more Custom Field functions. |
| Process Reports | Incompatible | Cannot be used to configure a process report. |
| Process Events | Incompatible | Cannot be used to configure a process event node, such as a start event or timer event. |
There are older versions of this function. You can identify older versions by looking at the name to see if there is a version suffix. If you are using an old version, be sure to refer to the corresponding documentation from the list below.
| Old Versions | Reason for Update |
|---|---|
| a!recordFilterDateRange_20r2 | Supports updated record types that use record type field references. |
To use the latest version of the function, replace the function with a version suffix with a new function reference.
To learn more about how Appian handles this kind of versioning, see the Function and Component Versions page.
