Add Chart View
Add Chart View turns an existing tracker plugin into a reporting-ready app with a chart view, a Reports tab, monthly trends, and a dashboard summary stat.
Trusted by frontline teams 15 years of frontline software
Built for: Facilities Management · Operations · Safety And Compliance · Inventory And Asset Tracking
Overview
Add Chart View is an edit-mode template for an existing tracker plugin that needs reporting without rebuilding the app. It adds a chart view declaration to the primary record schema, a Reports navigation tab, a controller action that aggregates records, a shared chart partial render, a monthly trend chart, and a dashboard summary stat.
Use this template when users already enter records and now need to see totals, categories, and trends inside the app. It fits trackers with a clear category field and a main numeric field, such as maintenance costs by asset type, incidents by status, or inventory movement by item group. The template is especially useful when the team wants one place to review live data instead of exporting to spreadsheets.
Do not use it as a starting point for a brand-new app with no existing record structure, or for data that does not group cleanly. If the source record has no meaningful category field, or the numeric field should not be summed, the chart will be misleading. It is also not a replacement for a full analytics stack; it is a focused reporting layer for a tracker plugin. The value of the template is that it keeps the chart tied to the same records, permissions, and navigation as the rest of the app.
How to use this template
- 1. Open the existing plugin schema and add the chart view declaration to the primary record type, choosing the most logical category field for x_field and the main numeric field for y_field.
- 2. Add a Reports tab to the navigation so users can reach the chart view without digging through the table or form screens.
- 3. Create or update the reports controller action to call aggregate_records for grouped totals and pass the result into the shared plugin chart partial.
- 4. Add the monthly trend chart with group_records and a month date bucket so the app can show change over time, not just a single total.
- 5. Update the dashboard with a summary stat using aggregate_records and function: 'sum' so the key number is visible at a glance.
- 6. Test the report with sample data that includes several categories and multiple months, then adjust the fields or aggregation if the chart is flat or misleading.
Best practices
- Choose a category field with a small number of meaningful groups, because charts become hard to read when every record has a unique x-axis value.
- Use a numeric field that truly represents volume, cost, or count, and avoid summing fields that are only identifiers or durations unless that is the intended metric.
- Keep the Reports tab read-only for most users so the reporting view cannot be mistaken for the data-entry screen.
- Seed sample data across multiple categories and at least two or three months so the chart and trend view render with useful variation on first open.
- Match the dashboard summary stat to the same metric used in the chart so users do not see conflicting numbers in different parts of the app.
- If the source record has sensitive fields, limit the chart to non-sensitive aggregates and do not expose detail data that the role should not access.
- Use patch_plugin_file for small edits so the template stays close to the existing plugin and only touches the files that need reporting changes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this template add to my existing plugin?
It adds a chart view declaration to the primary record schema, a new Reports navigation tab, a reports controller action, a shared chart partial render, a monthly trend chart, and a summary stat on the dashboard. The template is meant to extend an existing tracker rather than replace it. It focuses on turning stored records into readable reporting views.
What kind of data works best with this template?
It works best when your record type has one clear category or select field and one main numeric field that can be summed. That makes the chart view and aggregation predictable. If your data is mostly free text or has no meaningful grouping field, the chart will be less useful.
Who should use the Reports tab in the app?
The Reports tab is typically for managers, coordinators, or admins who need to review totals and trends without opening each record. Frontline users can still create or update records in the main table or form screens. You can keep the reporting view read-only for most roles.
How often should the monthly trend chart be reviewed?
Monthly review is the intended cadence because the template includes a month-bucketed trend chart. That makes it useful for spotting changes over time, comparing periods, and checking whether activity is rising or falling. If your workflow is weekly, you can customize the bucket to match.
Does this template handle regulated reporting or audit requirements?
Not by itself. It is a reporting enhancement for an existing tracker, so any compliance needs still depend on the underlying record type, permissions, and retention rules. If the source data is regulated, make sure the chart view does not expose fields to users who should not see them.
What are the most common mistakes when adding chart views?
The biggest mistake is choosing the wrong x_field, such as a field with too many unique values or no real grouping value. Another common issue is using a numeric field that should not be summed, which makes the chart misleading. Teams also forget to add the Reports tab to the navigation, so the chart exists but is hard to find.
Can I customize the chart type or aggregation logic?
Yes. The template is a starting point, so you can change the chart_type, x_field, y_field, aggregate function, or date_bucket logic to fit your record type. You can also add additional charts if the app needs more than one reporting view. Keep the first chart simple so the page remains easy to read.
How does this compare with exporting to spreadsheets?
Spreadsheets can work for one-off analysis, but they usually create a separate copy of the data and require manual updates. This template keeps the chart inside the app, so the report stays tied to the live record set. That reduces version drift and makes it easier for users to check trends without leaving the workflow.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
Fix recruiting pipeline handoffs with a unified candidate portal, branded career pages, and faster offers that keep top talent engaged.
-
MangoApps AI agents now take action across 21 apps—approving leave, advancing candidates, managing schedules—not just surfacing recommendations.
-
MangoApps is now Workday Design Approved, surfacing benefits, pay, learning, and time-off data directly inside the MangoApps platform for frontline workers.
-
Artificial Intelligence helps Human Resources improve hiring, reduce bias, and boost workforce efficiency with smarter, data-driven decisions.
Ready to use this template?
Get started with MangoApps and use Add Chart View with your team — pricing built for small business.
