Troubleshoot an empty report or dashboard
Check permission, filters, date/status data and source record scope. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Dashboard / Reports
Before you start
- Use an account with Administrator or report user and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What you’ll accomplish
Check permission, filters, date/status data and source record scope. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Dashboard / Reports.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields and options to review
Exact actionTroubleshoot an empty report or dashboard
Exact navigationAdmin Area → Dashboard / Reports
Module version1.0.0
Access ruleAdministrator or report user
VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.
Report filtersSelect the displayed month/year/custom period, status, property type, city, listing or payment criteria.
Source verificationOpen source property, request, tenancy, contract, invoice or payment records to reconcile totals.
Rules the system enforces
- Do not assume zero means no records until filters/ownership are verified.
- Reports require real_report view capability.
- Report results depend on stored status/date/currency values and the current user’s accessible data.
How to confirm it worked
- The supported troubleshoot an empty report or dashboard flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.