Reporting is unreliable when it is created outside the working data. The team completes tasks in one tool, finance holds amounts elsewhere and management receives a manually assembled report once a week. Apexloop builds reporting on the same records people work with every day.
The key pattern is simple: relations find related data, view columns display it as a filtered list and formulas calculate values over it.
A view column is not just a subgrid
A view column can show all records from a selected database that match a filter. In a project detail this can be tasks, in a company detail projects, in an invoice detail line items and in a campaign detail scheduled newsletters.
Because a view column returns a filtered result, a formula can use it as context. This opens the path to rollups without duplicate manual fields.
Cascades carry totals upward
Imagine companies, projects and tasks. A task has hours worked, a rate and a status. A project has a task view column and formulas for the sum of hours, budget, open blockers and completion estimate. A company has a project view column and its own formulas that sum project values.
Data flows from the lowest records upward:
- a task calculates its cost,
- a project aggregates tasks,
- a company aggregates projects,
- a dashboard shows the summary for management.
When a task changes, the report is built on updated data.
Reporting needs controlled dictionaries
Statuses, priorities and work types should be databases, not free text. If the team uses "Done", "Completed" and "Finished" as three text values, charts lose meaning. A select linked to a status database keeps the dictionary consistent and yet extensible.
The dictionary can carry further information: order in the workflow, group for reporting, colour, responsible role or internal description.
Views answer different questions
One report is not enough for everyone. A datagrid helps verify underlying data, a chart shows the summary, a timeline reveals dependencies, a calendar shows dates and a kanban shows work flow between statuses.
Name each view after the question it answers:
- "Which projects have exceeded the budget?"
- "What is waiting for approval?"
- "Which tasks are blocking the release?"
- "How much work falls in the next week?"
Such a name leads the user to action, not just browsing.
Report as an output
When a report needs to be shared outside Apexloop, use a document page as a template. It can contain text, dashboards, data views, QR codes, media and placeholders. Automation prepares a PDF or email-safe HTML.
Reporting then is not a manual presentation. It is a managed output from the working system.