logo

This section guides you through building a list

🗂️ Data Source

You need to determine what this list will show. You There are three types of data presented here:
  1. Channels
  1. Groups
  1. Collections
  1. Products
  1. Categories
  1. Bookings
  1. Events
  1. Catalogs
  1. Images
  1. Videos
  1. Audio Files
  1. Website URLs
  1. Location Maps
  1. Users
Image without caption

➕ Additional Conditions

The Additional Conditions section lets you define extra filtering rules that apply to the ListView results. Use ‘Additional Conditions’ when you want the list to always respect certain constraints—for example, only show items from a specific category, type, or tag.
📌 Example
Let’s say you're displaying Channels in a list.
You have multiple channels named France and others named Brazil.
If you're creating a dedicated tab that should only show France-related channels, you can use Additional Conditions to filter by the "country" or "name" field with the value "France".
This ensures your list will only include content that matches "France" in the data field you specify.
Image without caption

Data Field

Choose where you can find the condition you entered: id, name, name.keyword, description, created_date, updated_date, etc.
Image without caption
📌
The data field is determined by the selected data source. Each source exposes its own relevant fields. For example, when you include products, bookings, or events, the data field will display commerce-related fields such as vendor, price, compareAtPrice, and similar attributes. These fields will not be available if the source is set to community items like groups or channels, since those data types do not carry pricing information.
Image without caption

Clause

You have four options:
  1. Must: You want only documents that definitely match a certain condition.
  1. Should: You want to rank documents higher if they match, but you don’t want to exclude those that don’t.
  1. Filter: You want to apply exact constraints (e.g., tags, categories, date ranges) that don’t influence ranking.
  1. Must Not: You want to exclude documents matching a condition.
Based on the example, if you want the list to display only France channels, you should set the clause type to Must, ensuring the condition is strictly applied.
Image without caption

Query Type

  • Term: Looks for an exact value in a field (like searching for a specific ID or keyword).
  • Terms: Looks for several exact values at once (for example, find products with IDs 1, 2, or 3).
  • Match: Search a single field and find results that contain the word, not just exact matches (like searching “red shoes” in the product name).
  • Multi Match: Search across multiple fields at the same time (for example, look for “red shoes” in product name, description, and tags together).
Based on the example, if the word ‘France’ appears in both the name and description fields of your France channels, the Multi Match option will appear.
Image without caption

Value

This section is for testing how the list will look, so if you want that list to represent France channels, add your value as ‘France.’
Image without caption
Click ‘Create Query.’
Image without caption
And you will see your results.
Image without caption

🔃 Optional Sorting

This section is entirely optional for you, as it controls the sorting of the search results that will appear for users:
Image without caption

Data Field

Choose the type of data field.
Based on the example, we will choose ‘name.keyword.’
Image without caption

Sort Order

It is the order of the data field: Ascending & Descending.
Based on the example, we will choose ‘Ascending.’
Image without caption
Then click ‘Create Query’ and then ‘Search’ to see your results.
As shown in the example, you'll notice that the search results differ from the previous view—this time, the France Channels are displayed in ascending order.
✅With Optional Sorting
✅With Optional Sorting
❌Without Optional Sorting
❌Without Optional Sorting

🔀 Optional Field Mapping

This section defines how the data is displayed in the list. Field mapping allows you to choose which fields appear in specific positions. For example, you can configure the list so that the channel description is shown as the headline instead of the default field. In other words, field mapping lets you replace a default field with the one you prefer.
Image without caption

Field

Choose the type of field.
Based on the example, we will choose ‘Headline.’
Image without caption

Default

Choose the field you want to be replaced with your channel's headline.
Based on the example, we will choose ‘description.’
Image without caption
Then click ‘Create Query’ to check your result.
As you can see, the description is shown in the headline.
Image without caption

Add Map By Source

This section is for more than a single data source; for example, if your data sources are channels & groups, this section is for adjusting each one’s map.
Choose Channels.
Image without caption
Choose ‘Use Fields’ or ‘Use Constant,’ then click ‘Add Map’:
Image without caption
If you chose ‘Use Fields,’ you will have a dropdown menu of existing values.
Image without caption
Image without caption
If you chose ‘Use Constant,’ you can add your value manually; for example, you want to add specific text (ex: New) instead of the headline.
In this case you can ignore the default section, as each source has its own options. The default section is for a single data source.
Image without caption
Do the same for your groups, then click ‘Create Query.’
Image without caption
Just like the result, the channel’s headline is replaced by the value ‘New,’ and the group’s headline is replaced by the description.
Image without caption

❓ FAQs

Q: How can I show a list of items like channels, products, or events in my app without coding?

A: Super easy! In nandbox, you can add a List View to display just about anything—channels, groups, products, events, even user profiles. All you do is pick the data source you want, and the app will automatically organize the content into a clean, scrollable list. No coding needed.

Q: What exactly is a Data Source?

A: Think of the Data Source as the “where” for your list—it tells the app what type of content to pull in. For example:
  • Products, bookings, or events → show details like price or vendor.
  • Groups or channels → show names and descriptions.
  • Users → show profile info.
Choosing the right source makes sure your list shows the right kind of data.

Q: Can I filter my list so only certain items show up?

A: Yes! That’s what Additional Conditions are for. They let you set rules so your list always shows only what you want.
For example, if your app lists channels but you only want to see channels about France, you can add a condition to filter by “country” or “name” with the value “France.” From then on, your list will only display those channels.

Q: What does “Data Field” mean here?

A: The Data Field is simply the piece of information you’re applying your rule to. Common examples are id, name, or description. If you’re working with products or bookings, you’ll also see fields like price or compareAtPrice. Each type of data source has its own fields available to work with.

Q: What are Clauses and how do they affect my list?

A: Clauses are just different ways to tell the system how strict to be with your filters:
  • Must → Only include items that match (strict rule).
  • Should → Prefer items that match, but still show others.
  • Filter → Apply an exact rule, like a date range or tag, without changing ranking.
  • Must Not → Exclude items that match.
So, if you want to see only France channels, you’d use Must.

Q: What’s the difference between Term, Terms, Match, and Multi-Match searches?

A: Great question. These are just different ways of searching:
  • Term → Finds an exact value in one field (like a specific ID).
  • Terms → Finds several exact values at once (IDs 1, 2, or 3).
  • Match → Searches a single field for words that contain your input (like “red shoes” in product name).
  • Multi-Match → Searches across multiple fields at the same time (like looking for “red shoes” in product name, description, and tags).

Q: Can I sort my list items?

A: Absolutely. Sorting is optional, but it’s handy when you want results in a specific order. Just pick a Data Field—like name.keyword or created_date—and choose whether you want it ascending (A–Z or oldest to newest) or descending (Z–A or newest to oldest).

Q: What does Field Mapping do?

A: Field Mapping lets you control how your list looks by swapping out the default field for one you’d rather show. For example, instead of showing the channel name as the headline, you could display the channel description instead. It’s an easy way to customize what your users see.

Q: Can I map fields differently if I’m using more than one data source?

A: Yes, you can! If your list combines things like channels and groups, you can use Add Map by Source to adjust each one separately. You’ll have two options:
  • Use Fields → Pick from existing fields.
  • Use Constant → Type in your own value, like displaying the word “New” as a headline.
This gives you complete control over how each type of content appears in your list.

Powered by Notaku