Documentation Index
Fetch the complete documentation index at: https://docs.upsolve.ai/llms.txt
Use this file to discover all available pages before exploring further.
Overview
When embedding dashboards in iframes or sharing application links, you can pre-set filter values directly in the URL. This lets you:- Show different data views to different users without building separate dashboards
- Deep-link to a specific filtered state
- Control filters programmatically from your host application
Omnibar Filters (f_ prefix)
The primary way to pass filter values via URL. These filters show as interactive pills in the filter bar — users can see what’s filtered and modify or remove them.
URL Format
Raw— a column from a raw database tableOutput— a computed/output column from chart SQLVariable— an RLS variable filter
Value Types
| Prefix | Type | Example |
|---|---|---|
s: | Select (single value) | s:Athletics |
sm: | Select (multi-select) | sm:Athletics or sm:Athletics,Swimming |
n: | Numeric | n:2000 |
b: | Boolean | b:true |
i: | Text input | i:search term |
dp: | Date preset | dp:last_7_days |
ds: | Date (single) | ds:2024-01-01 |
dr: | Date range | dr:2024-01-01,2024-12-31 |
Examples
Single filter:Behavior
- Filters appear as pills in the omnibar — users can see what’s active
- Multiple filters combine with AND logic
- Users can remove or modify filters using the pill controls
- Non-existent columns are silently ignored (no error)
- Works with both JWT-authenticated and public (anonymous) access
Dynamic Filters from JavaScript
Controlled Filters (filter_ prefix)
Controlled filters are configured in the Upsolve Hub with a control key. They’re designed for server-side or host-app control — typically hidden from end users.
For setup instructions on configuring controlled filters in the Hub, see Controlled Filters.
URL Format
Examples
Combining Both Filter Types
You can use omnibar (f_) and controlled (filter_) filters together in the same URL:
Legacy Hub1 Support (share/dashboard URLs)
Legacy Hub1 Support (share/dashboard URLs)
Troubleshooting
Filter Not Applying
- Check the column name: The
f_prefix requires the exact table and column name from your database. Misspelled names are silently ignored. - Check the source type: Use
Rawfor database columns,Outputfor computed columns. - Check value encoding: For
f_filters, include the type prefix (sm:,s:,n:, etc.). Forfilter_controlled filters, use URL-encoded JSON.
Controlled Filter Causes Chart Errors
- Use JSON arrays for Select Multi:
filter_key=%5B%22value%22%5D(which is["value"]URL-encoded), notfilter_key=value. - Verify the control key matches: The
filter_suffix must match the exactcontrolKeyconfigured in the Hub filter settings.
Filters Visible When They Should Be Hidden (or Vice Versa)
- Omnibar (
f_) filters are always visible as pills - Controlled (
filter_) filters are hidden by default. SetisVisible: truein the Hub filter configuration to make them visible.