After creating Tableau Next assets in your scratch org and adding them to a data kit, you're ready to package and deploy.
-
From the CLI, run the following command to create a beta Salesforce managed package that points to your data kit metadata folder:
sf package create -n PACKAGE_NAME -t Managed -v DEVHUB_ALIAS -p PATH_TO_DATA_KITBeta packages can only be installed in scratch orgs. See
package create. -
If your Data 360 app builds on the Data Cloud Single Source of Truth (SSOT) package, you must declare the SSOT package as a dependency in your
sfdx-project.jsonfile. Find the latest SSOT package ID on the Salesforce Partner Community site. For example, if your package includes a CRM data stream that maps to a standard data model object (DMO), include the SSOT package as a dependency.{ "versionName": "ver 0.1", "versionNumber": "0.1.0.NEXT", "path": "data-cloud-app", "default": false, "package": "PACKAGE_NAME", "versionDescription": "", "dependencies": [ { "package": "0123456789abcdef" } ] } -
Creating the managed package produces a
0hoID. Copy that ID. Next, create a managed package version with the0hoID. -
Use the following command to create the package version:
`sf package version create -v DEVHUB_ALIAS -k INSTALLATION_KEY -p 0ho_ID -w 45 -f config/project-scratch-def.json`See
package create. -
To distribute the package, promote the package version to a released version. The released version can be installed in a production org. See Release a Second-Generation Managed Package.