Summary
The Using search operators article needs updates to document the view operator and Insights-related search functionality. Additionally, after reviewing the How to Use Insights article, several improvements are recommended to better connect the two articles.
Slack thread: https://expensify.slack.com/archives/D0AH1G2F4HK/p1775682833688319
Required Changes
1. Add view operator documentation
The search operators article has no mention of the view operator. Add documentation for view: (e.g., view:table, view:bar, view:line, view:pie) which controls how search results are displayed — especially relevant when using grouping operators for Insights-style reports.
2. Add Insights section or cross-reference
The search operators article doesn't mention Insights at all. Add a section explaining how search operators power Insights and link to the Insights article. The Insights article already links back to search operators — but the reverse link is missing.
Suggested Improvements (from reviewing the Insights article)
After comparing the two articles, these gaps and inconsistencies should be addressed in the search operators doc:
3. Document group-currency: more prominently
The search operators article mentions group-currency: only in a brief example (group-currency:USD) but doesn't explain what it does or list supported values. The Insights article references currency normalization implicitly. Add a clear explanation of group-currency: with supported currency codes.
4. Add a "Building Custom Reports" or "Using Search with Insights" section
The Insights article has a "How to create a custom spending report using Insights" section that tells users to modify filters and save searches. The search operators article should have a corresponding section showing practical examples of building Insight-style reports using search operators, e.g.:
type:expense group-by:category date:last-month view:bar — Top categories bar charttype:expense group-by:from date:last-month view:table — Top spenders tabletype:expense group-by:month date:year-to-date view:line — Spend over time
5. Document Save search functionality
The Insights article mentions "Click Save search to store your custom version" but the search operators article doesn't mention saved searches at all. Add a note about saving searches for reuse.
6. Align grouping operator lists
Both articles list group-by: options but the search operators article includes some that the Insights article doesn't (group-by:report, group-by:card, group-by:withdrawal-id) and vice versa. Ensure the search operators article is the canonical, complete reference and that the Insights article links to it rather than maintaining a separate list.
7. Add date filter examples relevant to Insights
The Insights article references date filters like date:this-month, date:last-month, date:year-to-date, and custom date ranges. The search operators article covers these but could benefit from more examples showing how date filters combine with grouping for analytical queries.
Summary
The Using search operators article needs updates to document the
viewoperator and Insights-related search functionality. Additionally, after reviewing the How to Use Insights article, several improvements are recommended to better connect the two articles.Slack thread: https://expensify.slack.com/archives/D0AH1G2F4HK/p1775682833688319
Required Changes
1. Add
viewoperator documentationThe search operators article has no mention of the
viewoperator. Add documentation forview:(e.g.,view:table,view:bar,view:line,view:pie) which controls how search results are displayed — especially relevant when using grouping operators for Insights-style reports.2. Add Insights section or cross-reference
The search operators article doesn't mention Insights at all. Add a section explaining how search operators power Insights and link to the Insights article. The Insights article already links back to search operators — but the reverse link is missing.
Suggested Improvements (from reviewing the Insights article)
After comparing the two articles, these gaps and inconsistencies should be addressed in the search operators doc:
3. Document
group-currency:more prominentlyThe search operators article mentions
group-currency:only in a brief example (group-currency:USD) but doesn't explain what it does or list supported values. The Insights article references currency normalization implicitly. Add a clear explanation ofgroup-currency:with supported currency codes.4. Add a "Building Custom Reports" or "Using Search with Insights" section
The Insights article has a "How to create a custom spending report using Insights" section that tells users to modify filters and save searches. The search operators article should have a corresponding section showing practical examples of building Insight-style reports using search operators, e.g.:
type:expense group-by:category date:last-month view:bar— Top categories bar charttype:expense group-by:from date:last-month view:table— Top spenders tabletype:expense group-by:month date:year-to-date view:line— Spend over time5. Document
Save searchfunctionalityThe Insights article mentions "Click Save search to store your custom version" but the search operators article doesn't mention saved searches at all. Add a note about saving searches for reuse.
6. Align grouping operator lists
Both articles list
group-by:options but the search operators article includes some that the Insights article doesn't (group-by:report,group-by:card,group-by:withdrawal-id) and vice versa. Ensure the search operators article is the canonical, complete reference and that the Insights article links to it rather than maintaining a separate list.7. Add date filter examples relevant to Insights
The Insights article references date filters like
date:this-month,date:last-month,date:year-to-date, and custom date ranges. The search operators article covers these but could benefit from more examples showing how date filters combine with grouping for analytical queries.