PranavNagrecha/AwesomeSalesforceSkills / skills/admin/analytics-dashboard-design
analytics-dashboard-design
VerifiedUse when designing or troubleshooting CRM Analytics dashboards — chart types, bindings, faceting, dashboard interactions, mobile layout, and filters. NOT for standard Salesforce reports and dashboards — use admin/reports-and-dashboards-fundamentals. NOT for hand-editing dashboard JSON or a SAQL step — use admin/analytics-dashboard-json.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.1 KB |
| references/examples.md | markdown | 4.0 KB |
| references/gotchas.md | markdown | 3.2 KB |
| references/llm-anti-patterns.md | markdown | 4.6 KB |
| references/well-architected.md | markdown | 2.8 KB |
| scripts/check_analytics_dashboard_design.pyexecutable | script | 3.7 KB |
| templates/analytics-dashboard-design-template.md | markdown | 2.1 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — CRM Analytics Dashboard Design
## Relevant Pillars
- **Operational Excellence** — Naming steps descriptively, documenting binding logic in dashboard JSON comments, and explicitly configuring mobile layout reduces maintenance burden when the dashboard is handed off or updated by a different admin.
- **Reliability** — The columnMap fix (replacing static `columnMap` with `"columns": []`) is a correctness requirement for any dashboard that uses dynamic bindings. Missing this fix produces silently incorrect charts — a reliability failure that erodes user trust in analytics data.
## Architectural Tradeoffs
**Faceting vs. bindings:** Faceting is simpler and requires no JSON editing but is limited to single-dataset scenarios. Bindings are more powerful and cross-dataset capable but require JSON editing and careful columnMap management. Design dashboards around a single-dataset where possible to minimize binding complexity. Only introduce bindings when cross-dataset filtering is a genuine requirement.
**Dataset join vs. dashboard binding:** Joining two datasets at the dataflow/recipe level and building a single-dataset dashboard (using faceting) is more performant and simpler than maintaining two separate datasets with binding-based cross-filtering. When datasets are joined in the ETL layer, dashboard logic is simpler. The tradeoff: dataset refresh is heavier; if the datasets have very different refresh schedules, joining them at the ETL level forces both to share one cadence.
## Anti-Patterns
1. **Leaving columnMap static with dynamic bindings** — Any dashboard that uses a binding to change a chart's measure or grouping without updating `columnMap` to `"columns": []` silently renders wrong data. This is the highest-frequency invisible bug in CRM Analytics dashboards.
2. **Using faceting for cross-dataset filtering** — Enabling faceting and expecting it to filter widgets on different datasets. Faceting is dataset-scoped. Cross-dataset filtering requires bindings.
3. **Skipping mobile layout configuration** — Building dashboards for mobile users without configuring the mobile canvas. Mobile users see a zoomed-out desktop layout that is unusable on phone screens.
## Official Sources Used
- CRM Analytics Interactions Developer Guide — Bindings — https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_bindings.meta/bi_dev_guide_bindings/bi_bindings_overview.htm
- Visualize Data With Charts — CRM Analytics — https://help.salesforce.com/s/articleView?id=sf.bi_chart_types.htm&type=5
- Filter Dashboard Results with Faceting — https://help.salesforce.com/s/articleView?id=sf.bi_dashboard_filter_faceting.htm&type=5
- CRM Analytics REST API Developer Guide — https://developer.salesforce.com/docs/atlas.en-us.bi_dev_guide_rest.meta/bi_dev_guide_rest/bi_rest_overview.htm
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |