Filters
Apply filters to surface relevant data cross your app
By default, your collection views show all the records coming from your data source. However, you can filter the records to restrict what appears in your App. This means only records that meet the filter condition(s) will be visible.
Noloco supports both singular and multiple AND and OR filters which we'll detail how to use below.
You can also enable in-app filter fields so that users can change the filtering themselves. This will be covered in this guide also.

Filter allows us to exclude items from our lists based on different criteria. Users will not be able to see items that you filter out of a list. For example, in the app below we add a filter that shows only the Properties where the status is 'Active'.
Please note that restricting data by filtering is not a security feature. If your app has private or sensitive data then you should use Permissions to restrict access at the API layer.
Click to expand
The filter is created by checking certain criteria on a column (field) from your connected datasource. In the above example, we have a list of Properties synced from an Airtable base. Some of these properties are on the market, some are not.
We have a single-select field in our Properties table that informs us of the Status of the Property with a range of values in that single-select field stored in the Status field from Active, Pending, Under Contract, Closed, Cancelled and Not Listed.
If you're using Google Sheets, a table is the same as a sheet in your Spreadsheet. A column can be referred to as a field. A row represents a record in your table or sheet.
Click to expand
In Noloco, we select that column (a.k.a field) as the Filter and then we choose the criteria by which we are filtering.
The field selected is Status and the criteria is is equal to Active
We can use the same collection of data as a source in multiple tabs of the App and then filter each one in different ways.
For example, the app below shows the same Properties collection in three different sidebar items. Each tab has the same exact source of data, but each one is filtered to show a list of properties under different criteria
  • Properties Board (All properties)
  • Active Properties (Filtered to only show properties on the market)
  • My Properties (Filtered to only show properties related to the Logged in User)
Multiple sidebar menu items for Properties
There are a few different ways you can create multiple views of the same collection.
Either by adding the collection to the sidebar menu again or by cloning an existing menu sidebar item for that collection.
In edit mode - add new sidebar menu item
In edit mode - clone a view
Once you have created your additional sidebar menu item - rename it appropriately, apply your filter and you now have a new way to present data to your Users from this source.
In addition to filtering the data, you can also use custom visibility settings (from Advanced settings) to decide which menu sidebar items should be visible to each type of User. More of this is covered in the User Access guide.

If your app has data that some users should access, but not all users should access, then you should use a combination of Permissions & Linked fields to protect that data.
Anyone who can sign in to your app can see the data it surfaces, either in your app's user interface or by inspecting network traffic with common tools such as a browser's developer console.
Permissions lets you restrict who can access data based on their User role.
Learn more about User access (Roles & Permissions) here​
If your data source has linked fields setup whereby you can associate a User to different tables across your data source, then you can make use of the Noloco User Roles & Permissions whereby the 'Logged in User' can only download rows that they are linked to and based on the permissions permitted for their Role;
Important: If you are NOT using Noloco collections as your backend data source, make sure to sync your User list. This will ensure all of links or relationships between your 'Users' and other tables of data from your backend data source can be retained and therefore associated with their Noloco User login. More on User lists found here.
Noloco's permissions will prevent the user from accessing records that they do not own, so those records cannot be read by inspecting network traffic or by any other means.
Permissions are free to use and available for all Noloco apps.

Once you're happy that your Noloco Users have the necessary relationships setup between your data, you can start to filter collections from the App based on the 'Logged in User'.
In the below example we are applying a filter for the sidebar menu item 'My Properties'. We only want to show properties where the Logged in User is the related 'Buyer'(linked field) on the Property.
Applying this Filter in conjunction with the use of Permissions ensures those Logged in Users will only see data that belongs to them.

We can use multiple filters on a list with AND + OR logic. In the following example, we add two filters to our list of properties to show only items that include 'Active' or 'Pending' in the Status column.
  • Status is equal to 'Active'
  • OR
  • Status is equal to 'Pending'

You can also enable in-app filtering for your users so they can change the items that are displayed in the list. This is particularly useful for long lists of items.
In the example below, we enable in-app filter fields based on the Neighbourhood, Property Name and Status fields which allows users to find properties that meet certain criteria much faster.
To access this feature, enter into edit mode (cmd + e) and head to 'Filter fields' section of the view as seen below in the screenshot. Then choose which fields you want to allow your Users to filter by.
In edit mode from view configuration select 'Filter Fields'
From here, simply toggle on which filter fields you want to display to your Users
​
You can also add a "Search box" to any collection view that will search across any of your text/number fields that you have setup on the view instead of having to add multiple filters for each field.
Copy link
On this page
πŸ–₯ Filtering data in your Views
πŸ‘₯ Logged in User Filters
β›“ Multiple Filters
πŸ” Filter fields