Custom Reports
Your own saved reports: table reports built from a module's columns, and composed reports that combine existing reports.
A custom report is a saved definition that belongs to you. Trabalance stores the definition; every time you open it the figures are fetched fresh through the same permission-checked report engine as the catalog. There are two kinds, and they live in one list.
| Kind | What you build | Where |
|---|---|---|
| Table report | Pick a module, tick the columns you want, order them, filter, and save. One table, generated from your own data. | /reporting/custom/table/new |
| Composed report | Stack blocks — each an existing report you can already open, shown as a table or chart — under a header you design, with optional fields to type when it runs as a pack. | /reporting/custom/new |
My Reports
Saved reports appear in the My reports rail on the Reporting hub (once you have at least one) and on the catalog view (always, with an invitation to create your first). Each card shows the name, description and when it was last updated; clicking it opens the report. The card menu offers Edit and Delete. Deleting asks Delete this report? and removes only the saved definition — The underlying data is untouched — only this saved composition is deleted.
The New report menu on the rail offers Table report — pick your own columns and Composed report — combine existing reports. The hub's + Custom report button opens the composed-report builder directly.
A custom report is scoped to your user within your business. Colleagues do not see it, and it cannot be shared or transferred. Creating, updating and deleting one is recorded in the activity log.
Which Kind to Use
- Use a table report when the answer is a list — invoices with their customer, location and total; sales lines with item, quantity, rate and the account the money was collected to; every employee with department and start date; every customer with their aged balance. See Building a table report.
- Use a composed report when the answer is a pack — several existing reports on one printable page with your own masthead, such as a monthly performance report or a management pack. See Composed reports.
Both kinds require that you can open the reports they draw on. Staff cannot create or open custom reports.
What a Definition Stores
| Kind | Saved with it |
|---|---|
| Table report | The module, the chosen columns and their order, the filters, the sort column and direction, whether drafts are included, and the period as its default range. |
| Composed report | The default period, the template header, any pack fields, and each block with its report, grouping, title and starting view. |
A definition is stored; figures never are. Open a saved report a year later and it runs against today's books over whatever period you give it — which also means a definition can outlive a column. When a saved table report references a column that no longer exists, the page warns Some saved columns are no longer available and shows the rest rather than failing.
Related
- Building a table report — the six-step flow.
- Table report modules — the nine sources and their columns.
- The grain lock — why some columns cannot share a row.
- Composed reports — stacking existing reports into a pack.
- Daily packs — running a composed template as a locked snapshot.
- Saved views — the lighter alternative, stored in your browser.