PranavNagrecha/AwesomeSalesforceSkills / skills/admin/analytics-data-manager
analytics-data-manager
VerifiedUse this skill when configuring Data Manager in CRM Analytics: enabling objects for sync, scheduling data sync runs, setting up remote connections to external databases, monitoring sync status and error logs, or troubleshooting connected object issues. Trigger keywords: data sync, connected objects, Data Manager, sync schedule, remote connection, Snowflake connector, sync error, incremental sync, CRM Analytics data pipeline. NOT for pushing external data in programmatically via the External Data API — use data/analytics-external-data. NOT for authoring dataflow nodes — use admin/analytics-dataflow-development.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.2 KB |
| references/examples.md | markdown | 6.7 KB |
| references/gotchas.md | markdown | 6.0 KB |
| references/llm-anti-patterns.md | markdown | 9.0 KB |
| references/well-architected.md | markdown | 5.4 KB |
| scripts/check_analytics_data_manager.pyexecutable | script | 11.8 KB |
| templates/analytics-data-manager-template.md | markdown | 4.1 KB |
references/well-architected.md
View on GitHub# Well-Architected Notes — Analytics Data Manager
## Relevant Pillars
- **Reliability** — Data Manager is the foundational sync layer for all CRM Analytics data pipelines. Sync failures, stale connected objects, or credential expiry cascade into stale datasets and incorrect dashboard data. Reliability requires monitoring sync runs, alerting on failure, documenting credential rotation schedules, and scheduling periodic full syncs for objects with cross-object formula dependencies that incremental sync cannot detect.
- **Performance** — Sync performance is constrained by the 3-concurrent-sync limit and the volume of enabled fields per object. Enabling high-field-count objects (Account, Opportunity with many custom fields) increases sync duration and risks breaching the concurrency window. Staggering sync schedules, enabling only fields actively used downstream, and separating high-volume objects to off-peak windows are the primary performance levers available to an admin.
- **Operational Excellence** — Data Manager configuration is not self-documenting. Without a maintained sync runbook (object list, sync mode per object, schedule, downstream recipe dependencies, credential expiry dates), future admins cannot safely change configuration without risking data freshness regressions. Operational excellence requires treating sync configuration as infrastructure-as-documentation.
- **Security** — Remote connections (Snowflake, BigQuery, Redshift) require credential storage in Data Manager. Credentials should use service accounts with minimum necessary permissions, key pair authentication where supported, and rotation schedules enforced externally. Salesforce CRM Analytics IP egress ranges must be allowlisted in external database firewall and network policies — connecting without an IP allowlist exposes credentials to connection failures that may reveal internal hostnames in error messages.
## Architectural Tradeoffs
**Incremental vs. Full Sync per Object**
Incremental sync is faster and consumes fewer platform resources, but it is unreliable for any object that has fields driven by related-object changes (roll-up summaries, cross-object formulas). Full sync is slower and increases sync duration, but it guarantees data correctness. The well-architected tradeoff is to default to incremental sync and add a scheduled periodic full sync specifically for objects identified as having cross-object formula dependencies. Blanket full syncs on all objects waste sync windows unnecessarily.
**Connected Object Granularity vs. Recipe Complexity**
Enabling many small objects and joining them in recipes gives more flexibility but produces larger, more complex recipe graphs that are harder to maintain and debug. Enabling broader objects with more fields simplifies the recipe layer but increases sync volume. The correct balance is to enable the minimal set of fields needed by active downstream recipes, reviewed quarterly as recipe logic evolves.
**Remote Connections vs. Data Loading via API**
External data can reach CRM Analytics either via a Remote Connection (Data Manager managed) or via direct dataset API uploads (bypassing Data Manager entirely). Remote connections are preferred for recurring external data because they provide consistent monitoring, credential management, and incremental sync capability. Direct API uploads are appropriate for one-time imports or sources that do not support JDBC/ODBC connectivity.
## Anti-Patterns
1. **Querying Connected Objects Directly in SAQL or Dashboards** — Connected objects are internal staging replicas and are not accessible via SAQL, lens builder, or dashboard dataset selectors. Referencing a connected object by name in a dashboard query will fail or silently query an unrelated dataset of the same name. All connected objects must be materialized into named datasets via recipes or dataflows before any analytics layer component can use them.
2. **Relying Solely on Incremental Sync for Objects with Cross-Object Formula Fields** — Incremental sync uses `LastModifiedDate` as its sole change detection mechanism. Any field value that changes as a result of a related object update — without bumping the parent object's `LastModifiedDate` — will drift silently. Production orgs that depend on roll-up summary or cross-object formula fields for dashboard metrics must supplement incremental sync with periodic full syncs on affected objects.
3. **Configuring Remote Connections in Dataflow JSON or Recipe Nodes** — Remote connections to external databases are a Data Manager construct configured under Connect > Remote Connections. They cannot be defined inside a dataflow JSON file or a recipe transformation node. Attempting to configure credentials inside recipe logic results in either hard failures or unmaintainable workarounds. Always configure remote connections in Data Manager first; recipes reference the resulting connected objects by name.
## Official Sources Used
- Connect and Sync Your Data to CRM Analytics — https://help.salesforce.com/s/articleView?id=sf.bi_integrate_running_a_dataflow.htm
- Data Sync Limits and Considerations — https://help.salesforce.com/s/articleView?id=sf.bi_integrate_data_sync_limits.htm
- 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
- Salesforce Well-Architected Overview — https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |