Skip to main content
Curates which fields each sub-topic contributes to the field picker. Use the @topic-scoped syntax to include or exclude specific fields, views, or tags from individual sub-topics — or apply global directives across all sub-topics. The fields: parameter addresses the “too many filterable dimensions” noise that can occur when combining multiple topics. It filters which fields appear in the field picker, but doesn’t restrict queries — queries against excluded fields still execute, so existing saved queries don’t break.
The fields: parameter intersects with each sub-topic’s own fields: directive — it can only narrow what a sub-topic already exposes, not add fields the sub-topic has already excluded.

​
Syntax

​
Properties

​
string[]
A list of field directives. Each directive either includes or excludes fields from the field picker.@topic-scoped directives apply to a single sub-topic:
  • @<topic_name>.<view>.<field> — include a specific field
  • @<topic_name>.<view>.* or @<topic_name>.<view> — include all fields from a view
  • @<topic_name>.<view>:tag:<tag> — include fields by tag
  • -@<topic_name>.<view>.<field> — exclude a specific field
  • -@<topic_name>.<view> — exclude an entire view
Global directives (without @topic) apply to every sub-topic:
  • <view>.<field>, tag:<tag>, set:<set> — include patterns across all topics
  • -tag:<tag>, -<view>.<field> — exclude patterns across all topics
Include vs. exclude behavior:
  • If all directives are excludes (start with -), everything else is included
  • If any directive is an include (no -), the list becomes a whitelist — only explicitly included fields appear
A sub-topic with no matching @topic-scoped directive is left untouched — so scoping to topic A never hides fields from topic B.

​
Examples

The following examples assume a composite topic that combines sub-topics named sales and marketing.
Include specific views from each topic
Exclude specific fields
Global exclusions across all topics
Mix scoped includes with global excludes

​
Intersection with sub-topic fields:

The composite topic’s fields: parameter is applied on top of each sub-topic’s own fields: directive. The result is an intersection — the composite can only narrow what the sub-topic already exposes. If a sub-topic has:
And the composite topic has:
The field picker shows only orders.total_revenue from that topic — the intersection of the sub-topic’s orders.* (minus internal_notes) and the composite’s scoped include.

​
Picker-only filtering

The fields: parameter only affects which fields appear in the field picker. Queries against excluded fields still execute — this ensures existing saved queries and dashboards don’t break when you refine the field list. If a user has a saved query that references @sales.orders.internal_id, that query continues to run even after you add -@sales.orders.internal_id to the composite topic’s fields: list.
Picker-only filtering applies to the composite topic’s own fields: parameter. It does not relax an included topic’s own fields: directive, which is enforced at query runtime — fields that a sub-topic excludes cannot be queried through the composite topic and will return an error.