Lookup Filters in Roam

Roam supports the use of Lookup Filters to a similar level as the Web Application does. This includes the

• ability to define individual filters per lookup field
• application of a Dynamic Filter to a field. For example, selecting an Action Priority based on the source of an action.
• the condition must refer to a FORMFIELD ID

Since Roam is designed to work off-line – without access to the SAI360 database -, there are limitations 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.

Unsupported Lookup Filters

Some of the unsupported lookup Filters in Roam are listed below.

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

• Any use of NOT in the expression
• Use of OR
• Any filter with more than one dynamic .FORMFIELD reference
• Drill down in relationships
• Drilling through relationships to something not "on the form" - (Roam does not have access to the whole database, just what is on the form)