CRM Analytics. Lens to dashboard. Ship a rep pipeline view by end of day.

What this means for your store

A lens is a saved query or chart exploration. A dashboard bundles lenses with shared filters and drill paths. Most sales stand-ups need three things: pipeline by stage, closed-won trend, and a table of deals going stale. CRM Analytics lets you drop a tested lens onto a dashboard without rewriting SAQL - assuming dataset permissions and row-level security are already sorted.

Scenario on a real storefront

A commercial kitchen-equipment vendor in Texas builds a team pipeline lens, then publishes it for regional managers with Owner and Close Date filters:

# Lens SAQL - open pipeline by stage
q = load "opportunity_grain";
q = filter q by 'IsClosed' == "false";
q = group q by 'StageName';
q = foreach q generate
    'StageName' as 'Stage',
    sum('Amount') as 'Pipeline',
    unique('OpportunityId') as 'DealCount';
q = order q by 'Pipeline' desc;

# Lens UI → Save as "Team Pipeline by Stage"
# Dashboard → New → Add widget → Use existing lens
# Global filters: Owner.Role = "Regional Director"
#                  CloseDate = current fiscal quarter
# App → Manage → Assign to Sales Manager role

What to do next

• Clone a lens for a one-off tweak and you will forget to sync fixes back - update the source lens or accept drift across five dashboard copies.
• Default filters to current quarter and active owners so mobile reps do not land on an empty dashboard Monday morning.
• On Lightning record pages, bind OwnerId dynamically so each rep sees their pipeline without a separate dashboard per person.

Bottom line

Lenses are reusable query blocks; dashboards package them for daily use. One well-tested lens per KPI, shared filters on top, assign by role - not screenshots from Explore.