Saved views

Saved views store Explorer canvas state as JSON — datasource/table (or report) selection, columns, filters, layout, and a widgets array. No JRXML is written. The view routes are part of Data Explorer on the Professional package, including before a license is activated. They are not in the Open Source package. Flagging a view as a dashboard widget requires a Report Server Professional license.

Storage

Views are files under:

{AppRoot}/explorer/views/{username}/{key}.json

Each user owns their view keys. Stable catalog identity is owner/key (for example alice/sales-overview).

What is stored

• Shared dataset definition (table or report query)
• Widget specs (WidgetSpec) for the canvas
• Filters, columns, and layout metadata

Reload a view in the UI to restore the canvas. Flagging a view for dashboards creates a reference (owner/key) without duplicating the JSON payload.

Folders

Saved views can live in catalog folders alongside reports and dashboards:

• Catalog → New → Saved View opens Explorer with the current folder pre-selected
• Save as View in Explorer includes an optional folder picker
• Unfiled views appear under Home so you can Move or drag them into a folder
• API: POST /api/v1/content/move with content_type: explorer_view and content_key: owner/viewKey

Related

• Dashboards
• Folders
• Overview

---

For Developers

Integration path	Go here
Views API	REST Explorer
CLI	CLI explorer