Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/einstein-analytics-basics

einstein-analytics-basics

Verified

Use when deciding whether Salesforce Reports, CRM Analytics, or Tableau is the right level of analytics tooling, and when reviewing or troubleshooting basic CRM Analytics designs. Triggers: 'CRM Analytics', 'Einstein Analytics', 'Tableau CRM', 'lens', 'dataset', 'dataflow', 'analytics dashboard', 'license requirement'. NOT for a detailed CRM Analytics vs Tableau licensing and platform comparison — use architect/crm-analytics-vs-tableau-decision. NOT for building the app, lenses and datasets — use admin/crm-analytics-app-creation.

references/llm-anti-patterns.md

View on GitHub
# LLM Anti-Patterns — Einstein Analytics Basics

Common mistakes AI coding assistants make when generating or advising on Salesforce CRM Analytics (formerly Einstein Analytics / Tableau CRM).
These patterns help the consuming agent self-check its own output.

## Anti-Pattern 1: Recommending CRM Analytics when standard Reports and Dashboards suffice

**What the LLM generates:** "Use CRM Analytics to build a dashboard showing Opportunity pipeline by stage."

**Why it happens:** LLMs default to the more advanced tool because it appears frequently in training data. A pipeline-by-stage dashboard is a basic reporting need that standard Reports and Dashboards handle well without additional licensing costs. CRM Analytics requires separate licenses (CRM Analytics Plus or similar) that many orgs do not have.

**Correct pattern:**

```
Tool selection decision:
- Data is in Salesforce, single object or simple joins,
  standard grouping/filtering → Standard Reports & Dashboards.
- Data spans multiple systems, needs complex transformations,
  row-level security beyond sharing, or predictive analytics
  → CRM Analytics.
- Data needs full SQL, complex visualizations, or is mostly
  outside Salesforce → Tableau.

Start with the simplest tool that answers the business question.
Only move to CRM Analytics when standard reporting hits a wall.
```

**Detection hint:** If the output recommends CRM Analytics for a requirement that involves a single Salesforce object with standard grouping, the tool is over-engineered. Check if the use case involves cross-system data or complex transformations.

---

## Anti-Pattern 2: Ignoring license requirements for CRM Analytics

**What the LLM generates:** "Enable CRM Analytics and start building datasets and lenses."

**Why it happens:** LLMs skip the licensing prerequisite. CRM Analytics requires specific add-on licenses (CRM Analytics Plus, CRM Analytics Growth, or Einstein Analytics licenses depending on the era). Without the correct license assigned to the user, CRM Analytics Setup options are invisible and the platform is inaccessible.

**Correct pattern:**

```
Before building in CRM Analytics:
1. Confirm org-level license: Setup → Company Information →
   check for "CRM Analytics" or "Analytics" in Permission Set Licenses.
2. Assign user licenses: create a Permission Set with "CRM Analytics Plus User"
   or equivalent, and assign it to each analytics user.
3. If no CRM Analytics license exists, the org cannot use CRM Analytics.
   Standard Reports & Dashboards do not require additional licenses.
4. License types:
   - CRM Analytics Plus: full access (build datasets, lenses, dashboards).
   - CRM Analytics Growth: limited (view, interact, but limited building).
   - Einstein Analytics (legacy name): same platform, older license name.
```

**Detection hint:** If the output jumps to building datasets without checking or mentioning license requirements, the licensing step is missing. Search for `license` or `Permission Set License` in the setup instructions.

---

## Anti-Pattern 3: Confusing CRM Analytics datasets with live Salesforce data

**What the LLM generates:** "The CRM Analytics dashboard shows real-time Salesforce data automatically."

**Why it happens:** LLMs assume CRM Analytics queries Salesforce directly like standard reports. CRM Analytics uses datasets that are copies of Salesforce data, loaded via dataflows or recipes on a refresh schedule. Data in CRM Analytics dashboards can be stale by hours or a day depending on the sync schedule.

**Correct pattern:**

```
CRM Analytics data freshness model:
- Datasets are COPIES of Salesforce data, not live queries.
- Data is loaded via dataflows (legacy) or recipes (current):
  - Scheduled sync: runs at defined intervals (e.g., daily at 2 AM).
  - Can be triggered manually or via API.
- Default sync frequency depends on license tier and configuration.
- Dashboard data reflects the last successful sync, NOT real-time.

For real-time data needs:
- Use standard Salesforce Reports & Dashboards.
- Or use Direct Data in CRM Analytics (available for some connectors)
  which queries live data without a dataset.
```

**Detection hint:** If the output says CRM Analytics dashboards show "real-time" or "live" data without mentioning sync schedule or dataset refresh, the freshness model is wrong. Search for `real-time` or `live` combined with CRM Analytics.

---

## Anti-Pattern 4: Using outdated product names interchangeably

**What the LLM generates:** "Set up Einstein Analytics in your org by going to Setup → Wave Analytics."

**Why it happens:** The product has been renamed multiple times: Wave Analytics → Einstein Analytics → Tableau CRM → CRM Analytics. LLMs mix names from different eras and reference obsolete Setup paths. Current Salesforce Setup uses "CRM Analytics" or "Analytics Studio."

**Correct pattern:**

```
Current naming (as of Spring '25):
- Product name: CRM Analytics (or "Salesforce CRM Analytics").
- Setup path to enable: Setup > Quick Find "Analytics" > Getting Started >
  Enable CRM Analytics (Analytics Platform Setup Guide, Spring '26).
- Builder interface: Analytics Studio (accessed via App Launcher).
- Previous names (for reference only):
  - Tableau CRM (used 2021-2022)
  - Einstein Analytics (used 2017-2021)
  - Wave Analytics (used 2015-2017)
- API/metadata names may still use "wave" or "analytics" prefixes
  (e.g., WaveRecipe, WaveDataset, WaveDashboard, AnalyticsSettings with
  enableInsights; corrected from "AnalyticsDataset", which is not a
  Metadata API type).
```

**Detection hint:** If the output uses "Wave Analytics" or navigates to a deprecated Setup path, it is referencing an outdated product era. Search for `Wave` or `Tableau CRM` as the current product name.

---

## Anti-Pattern 5: Building complex dataflows without considering row-level security

**What the LLM generates:** "Create a dataflow that loads all Opportunity data into a dataset. All CRM Analytics users can see the dashboard."

**Why it happens:** LLMs focus on getting data into datasets and forget that CRM Analytics has its own security model separate from Salesforce sharing rules. By default, a dataset may be visible to all CRM Analytics users. Without configuring Security Predicates or inheriting sharing from Salesforce, users may see data they should not see in Salesforce itself.

**Correct pattern:**

```
CRM Analytics security is NOT inherited from Salesforce by default:
1. Security Predicate: a filter applied to the dataset that restricts
   rows based on the running user's identity.
   Example: 'OwnerId' == "$User.Id" || 'ManagerId' == "$User.Id"
2. Row-Level Security dataset: a separate dataset mapping users to
   the records they can see, joined at query time.
3. Salesforce Sharing Inheritance: set with rowLevelSharingSource in a
   dataflow or in the recipe output, and always paired with a backup
   security predicate ('false' blocks users sharing cannot cover).
   (Corrected: an earlier version said dataflows could not use it.)
4. App-level sharing: CRM Analytics apps can be shared with specific
   users, roles, or groups — but this controls app access, not row-level data.

Always configure row-level security for datasets containing sensitive data.
```

**Detection hint:** If the output creates a dataset without mentioning Security Predicates, row-level security, or sharing, the data may be over-exposed. Search for `Security Predicate` or `row-level security` in the dataset configuration.

---

## Anti-Pattern 6: Scheduling Frequent Refreshes To Make CRM Analytics "Real-Time"

**What the LLM generates:** "Schedule the recipe every 15 minutes so the dashboard stays current."

**Why it happens:** The model treats refresh frequency as free and assumes more runs mean fresher data with no cost.

**Correct pattern:**

```
CRM Analytics allows 60 dataflow and recipe runs per rolling 24 hours
(runs under 2 minutes and data sync do not count). At the limit, no
dataflow, recipe, or data sync job can run at all. Concurrency is 1
dataflow in a sandbox or Growth production org, 2 with Plus.
- Budget runs per day across every recipe and dataflow first.
- If the business needs live numbers, use Reports and Dashboards.
(Analytics Platform Setup Guide, CRM Analytics Limits)
```

**Detection hint:** A schedule more frequent than hourly with no run-budget calculation, or "real-time" promised for a dataset-backed dashboard.

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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall