Skip to content

docs: mention view underlying data in Data apps guide #826

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: mention view underlying data in Data apps guide #826

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions guides/data-apps.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,12 @@ When an app runs a query, it will appear in the query inspector. Open it to see
![Clean Shot 2026 04 29 At 18 38 42@2x](/images/CleanShot-2026-04-29-at-18.38.42@2x.png)
</Frame>

### Viewing underlying data

Data apps can include **View underlying data** actions on metric values - for example, a button on a KPI card or a menu item on a table row. Clicking one opens the raw rows behind that metric value, the same way [View underlying data](/get-started/exploring-data/exploring-your-content#view-underlying-data) works in an explore. Results respect the user's permissions, user attributes, and row-level filters.

If you want this in your app, ask the agent for it - for example, _"add a 'View underlying data' button to each row in the revenue table"_. The agent uses the same query the chart or table is built from, so the drill-down lines up with what's on screen.

### Refreshing the preview

The preview header has a **Refresh** button that reloads the app's iframe and re-runs every metric query against the warehouse, without starting a new build. Use it when you've changed something in your semantic layer (for example, pushed a dbt update) and want to see the new results in the running preview.
Expand Down
Loading