Understand Advanced Lead Filters result columns
Read all implemented standard and conditional lead columns. 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
Read all implemented standard and conditional lead columns. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Run a broad controlled report.
- Check ID, name, company, contact and geography columns.
- Check conditional Lead Value and configured custom fields.
- Check status, source, dates, public, assigned and tags.
- Go to the source lead to verify values.
Fields and options to review
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.
Rules the system enforces
- More than four lead custom fields causes the query to enable SQL_BIG_SELECTS for the request.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.