You are here:
Packaging in Data 360
A package can contain small individual components or a large set of related apps. You create a data kit with the packageable features and add the data kit to a package. You can distribute this package to other Salesforce users and orgs, including people outside your company.
Required Editions
| Available in: Lightning Experience in all editions except Starter |
Packageable Components
To know more about the support available for Data 360 packageable components, see Data Cloud Extensibility Readiness Matrix.
Managed Package
Use a managed package if you plan to list an app on AppExchange. Managed packages use namespaces that make the content unique to the developer. They also support versioning and push upgrades that allow you to upgrade the packages that are installed in subscriber orgs.
Some Salesforce customers use packaging as part of their application lifecycle management.
Unmanaged Package
You can create an unmanaged package in any Salesforce edition (Enterprise, Unlimited, Performance, and Developer). Unmanaged packages aren’t upgradable, but all the contents in the package are editable after installation. To replace the installed contents with a newer version, uninstall then reinstall the newer unmanaged package.
Dedicated Data 360 Package
When creating a managed package with Data 360 metadata, you must isolate the Data 360 metadata from the other Salesforce metadata by creating separate packages that contain only Data 360 metadata. Then create package dependencies between your dedicated Data 360 package and any related packages.
Unlocked Packages
An unlocked package is a container for your Salesforce metadata. It provides a trackable way to add, edit, remove, and deploy customizations across orgs, making it easier to manage and upgrade internal business applications. Unlocked packages aren't supported for Data 360 objects.
Second-Generation Managed Packaging in Data 360
Salesforce has first-generation managed packaging (1GP) and second-generation managed packaging (2GP). Going forward, we recommend that all new packages be created using the second-generation managed package. You can use managed 2GP packaging to organize your source, build small modular packages, integrate with your version control system, and better use your custom Apex code. With version control being the source of truth, there are no packaging or patch orgs.
Locking and Unlocking Metadata in a Managed Package
All Data 360 feature metadata in a managed package is locked. As a package owner, you can control and protect the data kit metadata from unauthorized changes. After you install a package and deploy the data kit components, the components are locked. Susbcribers can add entities but can't modify or delete any deployed mappings or entities. If modifications are made to the deployed metadata entities, they're overwritten when the data kit is redeployed.
Versioning
Package versions let you evolve the components in managed packages gracefully by releasing subsequent package versions without breaking existing users using the package.
Push Upgrade
Automatically upgrade your subscriber to a newer version of the package. You can use this feature to ensure that all your orgs are on the same or latest version of your package.
AppExchange
Packages must be in a Managed-Released state to be listed on AppExchange for distribution.
Additional Resources
To learn more about this topic, review the associated Trailhead content.
- Create and Install Your Managed Package for Data Cloud
Use a managed package to build a Data 360 app and distribute it on AppExchange. Packaging is the container that you fill with metadata, and it holds the set of related features, customizations, and schema that make up your app. A package can include many different metadata components, and you can package a single component, an app, or library. - Packaging Data 360 Enrichments
Use second-generation managed packaging (2GP) to move Data 360 enrichments between orgs.
