🚀 Improved Filtering Logic

We've been hard at work improving the predictability and reliability of filtering logic for your apps. We've squashed many, many bugs (more than a dozen!) that would make Custom List Filters logic behave differently than conditional visibility and actions. With this release we made List, Count, and Dropdown Filters more consistent and have made some new things possible, such as:

Checking to see if a record has a relationship across a many-to-one relationship by checking the Relationship’s ID property for Empty. For example: You can get a list of Leads that do not have a Sales Person assigned [many Leads, one Sales Person], by checking
Current Leads > Sales Person > ID
is equal to
Empty
.
Evaluating if a record does or does not have an image saved for an Image or File property. For example: Only show options in a Dropdown component that have a saved Contract [File property], by applying a custom filter to only show records where
Contract > URL
is not equal to
Empty
.
Evaluating if a record does or does not have an Location saved for a Location property. For example: Getting a count of all Restaurant Records that do not have a Location, by using a Magic Text Count of all Restaurants with a custom filter set to
Restaurant's > Location > Full Address
is equal to
Empty
.

A rebuild of your apps is required for these updates to be applied.

There are so many things you can do to retrieve and format the right data for your app screens whether for counts, lists, or conditional actions & visibility.