Exported data from the dashboard public does not preserve report formatting/sequence
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
Describe the bug
Environment Details
Metabase version: v0.55.9.5 (Open Source)
Database type: ClickHouse
Issue Description:
When exporting data directly from a report (saved question) that is displayed in a pivot chart, the exported CSV/XLS file respects the sequence and formatting exactly as shown in the report.
However, when the same report is placed inside a public url report and then exported, the exported CSV/XLS file does not maintain the original sequence/format of the data. The order of rows gets changed, which makes the export inconsistent with what is displayed on screen.
This causes confusion for end-users because the report export works correctly, but the public url report export alters the data sequence.
To Reproduce
- Create a pivot chart in Metabase using a saved question (report).
- Format and sequence the data (e.g., sorted categories, pivoted columns, or ordered measures).
- Export the report directly → Export maintains the correct sequence.
- Add the same report to a public URLL report.
- Export the data from the public url report → Data order in CSV/XLS is different and not sequential as shown in the report.
Actual Behaviour:
Exporting data from the public URL report produces CSV/XLS files where the data sequence is incorrect or different from what is displayed in the report.
Screenshots and Document for Reference:
Attaching screenshots and document for reference.
Metabase_Dashboard_Export_Issue_25Sep2025.pdf
Expected behavior
The exported data from the public URL should exactly match the report formatting/sequence, just like when exporting directly from the report.
Logs
No response
Information about your Metabase installation
Metabase version: v0.55.9.5 (Open Source)
Database type: ClickHouse
Severity
Blocker
Additional context
Please help me to sort this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the public URL export with a pivot chart and compare its CSV/XLS output with a direct report export. Trace the public dashboard export entry point and identify why the displayed row sequence and formatting differ; done means public exports match the report output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, clojure
- Domain
- backend, data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100