Component Filters in Roam

note_awesome

ABOUT THE IMPORTANCE OF COMPONENT FILTERING:

Roam devices have to download referential data (e.g. Persons, Departments and Locations) to support off-line functionality.

It is important that you apply the strictest filter(s) acceptable to your referential data, in order to minimize the download size for those records as far as possible.

This can have an impact on Roam’s performance and usability.

Roam supports the use of Component Filters to a similar level as the web application does. This includes the

ability to define individual filters per field
application of a Dynamic Filter to a field. For example, a list of Persons is filtered, depending on the Department which has been selected.

Since Roam is designed to work off-line - without access to the SAI360 database -, there are limitations however in what type of Filters can be supported in Roam.

The web application has measures in place to prevent filters to be pushed to mobile devices which are not suitable for Roam devices. Should the system detect invalid filters or conditions during the publish process,

it will issue WARNING messages.
it will ignore these filters in Roam.

Component Filters

Refer to Component Filters or Dynamic Filtering - Component on how to configure them.

Below are some type of conditions that are not supported in Roam

Note that this is NOT a complete list of all exclusions, it contains just some of the most relevant examples:

Use of OR whenever a dynamic filter is involved
Any filter with more than one dynamic .FORMFIELD reference
Drill down in relationships
Only mandatory filters are supported in Roam - any optional filters are ignored.
Roll-up filtering on a component whose default component lookup list view is not a tree view
Drilling through relationships to something not "on the form" - (Roam does not have access to the whole database, just what is on the form)
Dynamic filters on subform fields cannot refer to FORMFIELDs on the parent form
Dynamic filters on tree view fields