Skip to content
MapleGatherMapleGather Help

Export a report

This guide covers the rendered-report export available to an admin today: CSV for a report of 1,000 rows or fewer.

Who can do this: Admins with reports:export. If Export is absent, ask your primary admin about your permissions. Current rendered reports use aggregate columns. If a report offers member-detail columns, including them additionally requires reports:export-pii.

Before you start

Section titled “Before you start”

Run a report first. The Export action appears when the results have rendered. See Run a financial report.

Steps

Section titled “Steps”
  1. On the rendered report, select Export. The export dialog offers CSV.
  2. Under Columns to include, select at least one exportable column. The current report’s visible columns are selected by default.
  3. If the report offers member-detail columns and your role has reports:export-pii, select Include member details only when needed. Without that permission, those columns are omitted.
  4. Select Export CSV. A report of 1,000 rows or fewer downloads immediately.

A report over 1,000 rows can’t be exported: the dialog says how many rows it has, that exports are limited to 1,000 rows, and Export CSV stays disabled. Narrow the date range or filters, run the report again, then export. Rendered-report Excel, PDF and queued email delivery are planned capabilities and are not offered by this path today.

Verify

Section titled “Verify”

The CSV file downloads to your browser. Cells beginning with =, +, -, or @ are escaped to prevent spreadsheet formulas from running. The current response does not provide an escaped-cell count, so the dialog cannot show a reliable count notice.

If something goes wrong

Section titled “If something goes wrong”
  • Export is absent: ask your primary admin to check reports:export.
  • Member-detail columns are hidden: export the allowed aggregate columns; the report’s data remains available.
  • Report is too large: narrow filters until it has at most 1,000 rows, then try again.
  • “This report is too large to export”: the server counted more than 1,000 rows (for example, rows were added after you ran the report). Narrow the date range or filters, run the report again, then export.
  • “Nothing left to export — every column you picked is a member-detail column your role can’t export.” — no file was created. Select at least one column that isn’t a member-detail column, then export again.
  • “Couldn’t prepare the export — no file was created” — MapleGather’s server answered with an error, or didn’t answer, before the file was built. Nothing was saved, so exporting again is safe.
  • “This report run no longer exists” — run the report again, then export from the new results.
  • “Your role doesn’t include permission to export reports” — ask an org owner to add report exporting to your role.
  • “Exporting is turned off because your organization has been closed” — a closed organization can’t export; its status is on the Subscription page at /admin/admin-security/subscription.
  • Download file gives you no file: the CSV is built, but MapleGather doesn’t yet save it at the address the link points to, so exporting again won’t help. Use the figures on the rendered report instead.

Members and Payments list exports are separate jobs with different listed formats and current delivery limits. See Export formats and injection safety reference.

Section titled “Related”