> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/projects/use-cases/reporting.md). # Reporting without a report Pivots, charts and grouped tables computed live from your records. Numbers your users can read on the page they are already on, computed live from the records, with no report builder to open and no dashboard to keep in sync.

				Cover image
Revenue cube without a report	Closed won revenue by region and quarter, totals on both axes, computed live from opportunities. Pivot Table.	Dynamic Components	Beginner, 10 min	https://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FwEkBsQSCmZGT19LAV1Ea%2Fuc-05-revenue-cube.png?alt=media	Revenue cube without a report
Bookings stacked by region	Twelve months of closed won bookings, every column stacked by region, drawn live from the opportunities. Chart.	Dynamic Components	Beginner, 10 min	https://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FJZwx7FUKFZXxrw84mMEu%2Fuc-10-bookings-by-region.png?alt=media	Bookings stacked by region
Expense approvals, grouped by employee	Fourteen expense lines grouped by employee, status badges, three lines checked and an Approve selected button. Data Table Group By.	LWC Components	Advanced, 30 min	https://3857391697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdHOej9Pd5IxJNGEJMZKW%2Fuploads%2FF4VLsIcKf5Rg422hJrMs%2Fuc-13-expense-approvals-lwc.png?alt=media	Expense approvals, grouped by employee

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.avonnicomponents.com/projects/use-cases/reporting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

Revenue cube without a report

Bookings stacked by region

Expense approvals, grouped by employee