docs(workbooks): document the filter bar's operators and groups (CUB-2119) - #11573
Merged
keydunov merged 2 commits intoAug 19, 2026
Merged
Conversation
The Filtering section was a single sentence. Document what the filter bar actually offers: where filters come from, the dimension/measure split into WHERE and HAVING, the operators available per data type, how values are entered, AND/OR groups, and custom SQL conditions. Operator wording follows the filter bar itself, which is a different vocabulary from the REST (JSON) API's filter operators. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The list named the `after date` / `before or on date` spellings the filter bar dropped, and omitted the operators authored views can already use: `after`, `before`, `after or on`, `before or on`, the empty-string checks and the six period comparisons. Group them by member type and keep the older spellings where they belong, next to the other accepted aliases. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
the
pr:community
keydunov
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Filtering section on the workbook
querying-datapage was one sentence. It now covers what thefilter bar actually does: where a filter comes from, that a dimension filter is a
WHEREand ameasure filter a
HAVING, the operators offered per data type, how values are entered, AND/ORgroups, and custom SQL conditions.
The operator wording is the filter bar's own, taken from
report-filter-operators.tsandFILTER_TYPES_BY_MEMBER_TYPEin the cloud repo. That is deliberately a different vocabulary fromthe REST (JSON) API's filters — the bar says
is/after or on/is nullwhere the API saysequals/gte/set, and it hasbetween,is emptyand the sixin the month|quarter|yearperiod comparisons. A reader sent to the API reference for "the full list" gets the wrong names,
so this page carries its own tables.
Second commit fixes the same vocabulary in the
default_ui_filtersreference, which promised "whatyou see in the filter bar is what you type" and then listed the retired
after date/before or on datespellings, withafter,before, the empty-string checks and the periodcomparisons missing — all of which the authoring parser already accepts. The old spellings are still
accepted, so they moved down to the sentence about aliases.
Closes CUB-2119. Supersedes #10632, whose operator tables described the REST (JSON) API and the old
Playground query builder rather than the workbook.
Verified with
mintlify broken-links --check-anchors(the one hit is a pre-existing anchor inreference/control-plane-api.mdx) and by reading both pages in a localmintlify dev. Not verifiedagainst the running app: the claims about where the bar sits and what a chip's menu offers come from
the components, not from a session in the product.
🤖 Generated with Claude Code