Package Wave Assets in Managed Packages | Salesforce
Package Wave Assets in Managed Packages
You can create managed packages of Wave assets, including Wave apps, dashboards, lenses, datasets, and dataflows. Use packages to distribute those assets to other users or organizations, including those outside your company.
A package is a container for something as small as an individual component or as large as a set of related apps. Packages can be distributed to other Salesforce users and organizations, including those outside your company. While packages come in two forms—unmanaged and managed—Wave supports only managed packages, which must be created from a Developer Edition organization.
Why only managed packages? There are some key advantages, especially around licensing and managing licenses. Using the AppExchange and the License Management Application (LMA), partners, ISVs, and developers can sell and manage user-based licenses for the app. Managed packages are also upgradeable, meaning you don’t have to start over; you can incrementally upgrade.
Click Add in the Components tab, then use the Component Type drop-down list to select and add your Wave assets to the package. Note that you must add dependent dataflows manually. That is, if you add a dataset to a package, the associated dataflows are not automatically picked up.
Wave Analytics components include Wave apps, dashboards, dataflows, datasets, and lenses. As you package Wave components, keep these tips and best practices in mind.
Wave Admin permissions are required to create a package, but not for deployment, which requires only Salesforce admin permissions.
There is no spidering between datasets and dataflows, meaning there is no dependency following. When packaging both, they must be added manually. If they are not, an error appears during deployment. The same is true for change sets—when packaging both datasets and dataflows, add them manually.
Images don't render when deploying a dashboard that uses an image widget that references image files not available on the target org. There are two workarounds. Either manually upload the images, or add a folder containing the images to the package. The document ID of the image file in the image widget must match that of the image. The user can’t save the dashboard in the target with an invalid document ID, but they can still view and edit it.
If a dashboard you're deploying has a link widget pointing to another dashboard that exists in the target org, you must manually update the link reference to point to the right one. If the linked dashboard doesn't exist in the target org, an error message appears. Either deploy the linked dashboard too, or re-create the linked dashboard in the target org. Update the link widget to point to the linked dashboard.
Take care when packaging dataflows. Invalid schema overrides, and unsupported or illegal parameters are removed (for example, Type = dim is no longer supported, it's now Type = text). Comments in JSON are removed. Nodes may appear in a different order.