Troubleshoot an empty lead report
Criteria may conflict, the default This Month period may be too narrow, or lead scope may exclude records. 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 → Lead Filters → Lead Filters
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What you’ll accomplish
Criteria may conflict, the default This Month period may be too narrow, or lead scope may exclude records. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour using known test leads and a controlled role.
- Select All Time, clear geography/type/tags and add conditions one at a time.
- Compare with the core Leads workspace.
- Record the verified outcome before changing permissions or code.
Fields and options to review
Verified behaviourCriteria may conflict, the default This Month period may be too narrow, or lead scope may exclude records.
Rules the system enforces
- Criteria may conflict, the default This Month period may be too narrow, or lead scope may exclude records.
How to confirm it worked
- Troubleshoot an empty lead report completes without a validation or permission error.
- The refreshed report, menu or saved-template page shows the expected state.
- A second authorised user sees only the records and navigation allowed by their core CRM permissions.
Security, privacy and operational checks
- Test changes with a non-production record or a controlled administrator account before wider rollout.
- Do not use navigation visibility as a substitute for core CRM record permissions.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.