Filters, sort and row limit

A mapped dataset inherits its rows from its mapping, but you can narrow and reorder those rows per dataset. Same source, same mapping, several datasets — that is the point.

Filters

A filter keeps or excludes rows based on a field value:

• role = "forward" — only forwards.
• score >= 0 — exclude rows without a score.
• is_active = true — skip inactive players.

Add as many as you need; rows must match all of them.

Sort

Order the rows by any field, ascending or descending. Multi-level sort is supported — sort by team, then by position, then by name.

Sort decides the order the control panel's row selector cycles through.

Row limit

Cap the dataset to the first N rows. Useful when a source lists 500 players but the leaderboard only shows 5.

Interaction

Filters apply first, then sort, then limit. Think of it as SQL WHERE → ORDER BY → LIMIT.

Why not do this in the mapping?

Put logic in the mapping if it should apply to every dataset built from the source. Put it on the dataset if it is specific to this one use.