Understand Advanced Lead Filters result columns
Read all implemented standard and conditional lead columns.
Exact navigationAdmin Area → Lead Filters → Lead Filters
Before you begin
- Confirm 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 this guide covers
Read all implemented standard and conditional lead columns. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Run a broad controlled report.
- Review ID, name, company, contact and geography columns.
- Check conditional Lead Value and configured custom fields.
- Review status, source, dates, public, assigned and tags.
- Open the source lead to verify values.
Fields, choices and supported possibilities
IdentityID, name and company.
ContactEmail and phone.
GeographyCity, state, country and ZIP.
PipelineLead value when supported, custom fields, status, source, created and last contact.
Access/ownershipPublic and assigned.
ClassificationTags.
Code-backed validations and workflow rules
- More than four lead custom fields causes the query to enable SQL_BIG_SELECTS for the request.
Expected result and verification
- The result-column review 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.