Edit a report
Update a saved report's data source, columns, filters, joins, and grouping in the Report Builder — or duplicate it as a starting point.
After a report is saved, you can change its configuration from the Report Builder edit view. Users with only view access see a read-only Report tab instead of the builder tabs. Editing is how you keep institutional reports accurate as schemas evolve, terms roll over, or colleagues request additional columns — without rebuilding from scratch.
Duplicating an existing report is also available from the same Actions menu, which is useful when you need a variant (for example, the same cohort report filtered for a different program, or a summary pass-rate view derived from a detail roster) while preserving the original.
Why it matters
Reports are living definitions, not one-time snapshots. A cohort enrollment report created for last year’s intake will need updated filters, an extra join for a new custom field, or revised grouping when your faculty changes how programs are structured. Maintaining reports in place keeps a single canonical definition that colleagues share and re-run each term.
Structural edits — changing the data source or removing joins — can invalidate columns and filters. The edit workflow emphasizes previewing after changes so you catch breakage before others run the report on deadline.
How it fits
| Related area | Relationship |
|---|---|
| Create a report | Initial build workflow; same five steps apply when editing |
| Common reports catalog | Decide whether to edit for a new question or duplicate a variant |
| Run and export a report | Run the updated definition on the Report tab |
| Share a report | Colleagues with view access see results from your edits on next run |
| Statistics and reports | Access model and reporting overview |
Reports draw on the same institutional data as University statistics exports and My Exams records. Editing a report does not change source data — it only changes how that data is queried and presented.
Key concepts
| Step | What you change |
|---|---|
| Data source | Primary entity the report is built from |
| Join data | Related entities connected to the root table (inner or left joins) |
| Pick columns | Fields included in the output |
| Filter | Conditions that narrow which rows are returned |
| Summarize | Group-by fields and aggregation settings |
Reports built in SQL Mode are edited on the SQL Mode tab instead of the query builder steps. Validate your SQL before saving changes.
How to open a report for editing
Go to OrgHub → Statistics Center → Your Reports.
Find the report in the table and open the row Actions menu (⋯).
Select Edit. Fuxam opens the report in the Report Builder.
You can also Duplicate a report from the same menu to create a copy you can modify without affecting the original.
How to edit columns, filters, and joins
On the Query Builder tab, the same five steps used during creation are available:
Navigate to the step you want to change.
Update joins, selected fields, or filter rules as needed.
Select Preview to verify the updated query returns the expected data.
Select Save changes and update the report name or description if prompted.
How to configure grouping
Step 5 — Summarize — controls how results are grouped and aggregated:
Open the Summarize step.
Choose one or more Group by fields.
Adjust aggregation on selected columns where supported.
Preview and save your changes.
Grouping turns row-level reports into summary views — for example, enrollment counts per study program rather than one row per student, or average grades per module rather than one row per attempt. Use it when your audience needs aggregates for planning meetings or accreditation evidence, not individual records.
Editing toward common institutional questions
| Goal | Typical edit |
|---|---|
| Pass / fail rates | Add outcome filters; Group by module; count |
| Grade distribution | Group by grade; count; keep term filter |
| Average grade per cohort | Group by cohort; average aggregation where supported |
| Narrower headcount | Tighten program / cohort filters; keep required term filter |
| Faculty-scoped variant | Duplicate, then change program filter; leave the institutional original intact |
See the Common reports catalog for full patterns.
When to edit vs duplicate vs create new
| Situation | Recommended action |
|---|---|
| Update filters or columns for the same purpose | Edit the existing report |
| Same structure, different program or term scope | Duplicate, then adjust filters |
| Detail roster vs summary rates for the same population | Duplicate; add Summarize on the summary copy |
| Fundamentally different question or audience | Create a new report |
| Shared report; risky structural change | Duplicate first, validate, then communicate the switch |
Best practices
- After any change to Data source or Join data, walk through steps 3–5 even if you only intended to change one join.
- Update the report Description when you add columns or change required filters so shared users know what changed.
- Communicate breaking changes to colleagues who run the report on a schedule — especially if required filters or column names changed.
- For SQL reports, test with Preview or a limited filter before Save changes; SQL errors affect everyone with access.
- When converting a student-level report into a leadership summary, prefer Duplicate so operational staff keep the detail version.
Common pitfalls
| Pitfall | What happens | Fix |
|---|---|---|
| Changed data source | Columns and filters may clear or error | Re-select columns and filters; preview before save |
| Removed a join | Fields from that entity disappear | Re-add join or remove dependent columns |
| Saved without preview | Unexpected empty or huge result sets | Re-open edit, preview, adjust filters |
| Edited a shared report mid-term | Colleagues see new shape on next run | Coordinate changes; consider duplicate for term-specific variants |
| Removed required filters for convenience | Accidental full-population runs and exports | Restore required filters for personal-data reports |
FAQ
Can viewers see that I edited the report?
Users with Can view access run the latest saved configuration. There is no separate version history documented here — coordinate significant changes with your team.
What happens to saved executions after I edit?
Saved execution snapshots from prior runs remain historical records. New runs on the Report tab use the updated definition. See Run and export a report.