Analytics Templates Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Why CRM Analytics Templates?
The Source App
Templated App Type
The Configuration Wizard
The Template Object
Choose Your Tool
The Process at a Glance
Prerequisites
Step 1: Create the WaveTemplate Object
Step 2: Retrieve (Export) the WaveTemplate Object
Step 3: Edit the JSON Files
Step 4: Deploy the WaveTemplate Object
Step 5: Test the Template
Step 6: Share the Template
Step 7: Create New (Downstream) Apps from the Template
Step 8: Update an Existing Template
Share CRM Analytics Assets Between Apps
Features Not Supported in This Release
Release Notes
API End-of-Life Policy
Appendix
PDF

The Source App

For the purposes of CRM Analytics Templates, the app you create in CRM Analytics Analytics Studio is called the source app. It’s a collection of CRM Analytics assets—datasets, dataflows, recipes, lenses, and dashboards— stored together in a folder.

You create the template—actually a set of JSON files—from that source app. If you update the source app in Analytics Studio, you can also update the template. The same template can also be updated by source apps in different orgs. This lets your team work collaboratively on the source app and its template. That is, more than one developer can work on the template, at the same time.

This diagram depicts multiple orgs collaborating on a template.

We use the term source app to refer to the app you work on, the one on which you base your template. When organizations use your template to create their own apps, we refer to them as downstream apps.

Note

Templates can reuse dashboards, lenses, and datasets that are part of apps other than the source app by creating dependencies on those assets. The reused assets must be part of apps created from templates. See Share CRM Analytics Assets Between Apps.