Loading
About Salesforce Data 360
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Packaging Data 360 Enrichments

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data 360

            Packaging Data 360 Enrichments

            Use second-generation managed packaging (2GP) to move Data 360 enrichments between orgs.

            Required Editions

            Available in: All Editions supported by Data 360. See Data 360 edition availability.
            User Permissions Needed
            To create packages: Create AppExchange Packages permission
            To upload packages: Upload AppExchange Packages permission
            To create a data kit: Data Cloud Architect permission set

            You need a Salesforce developer edition org to create the package and a subscriber org to install it.

            Using a first-generation managed package (1GP) to deploy direct DMO metadata has significant limitations. All dependencies must be included within a single package, meaning foundational CRM components, the FieldSrcTrgtRelationship, the data kit, and any CRM customizations that reference the relationship can't be split into separate packages. Currently, 1GP provides no way to control or sequence the order in which metadata is deployed in the target org during installation. As a result, if the package contains both the relationship metadata and a referencing customization (such as a page layout, Apex class, or Flow) the deployment may fail because we can't guarantee that the relationship is created before the customization. Due to these sequencing and dependency constraints, direct DMO packaging is not supported with 1GP managed packages and should instead be implemented using 2GP packaging, which allows dependencies to be split across packages and installed in a set order.

            1. In your Salesforce DX project, create a scratch org to serve as the source of truth for package development.
            2. In the scratch org, configure foundational CRM metadata such as custom objects and custom fields.
            3. Configure your direct DMO relationship, which creates a FieldSrcTrgtRelationship.
            4. Create a Data 360 data kit containing any custom Data 360 metadata you created.
            5. Review and publish the data kit to ensure all required dependencies are included.
            6. Retrieve the metadata for your CRM components, data kit, and relationship into the Salesforce DX project.
            7. Create the first 2GP package, which contains foundational CRM metadata (custom objects, custom fields); the FieldSrcTrgtRelationship and custom lookup field for the relationship; and the data kit.
            8. In the same scratch org, create additional CRM customizations (such as page layouts, Apex classes, or Flows) that reference the direct DMO relationship.
            9. Retrieve these customizations into your project.
            10. Create the second 2GP package, which contains CRM customizations that reference the direct DMO relationship.
            11. Install both packages in sequence (first foundational, then customizations) to deploy direct DMO functionality in the target org.
             
            Loading
            Salesforce Help | Article