Data 360: Data Kit Unlock Scenarios

What are my options? 

For good reason, we disallow deleting items deployed in this manner. The package owner, whether that is Salesforce, your developers, or a third-party package owner, builds the package and owns the upgrades to said package. Making modifications would break the connection between what they develop and what you've deployed and modified in your org, and ultimately prevent future upgrades to the data kit/bundle in question. 

Undeploy the Data Kit

In general, the path forward is for you to undeploy the data kit. This will remove all components from the data kit but then allow you to manually redo the implementation with whatever customizations you desire. Salesforce will ask you to undeploy first before considering any other alternative. 

Blocked from Undeploying due to Circular Dependencies

There are scenarios where you may be blocked from undeploying due to circular dependencies that cannot be resolved, thus blocking the undeploy from being allowed. Salesforce Support will review these scenarios on a case by case basis to understand if there is a product bug. We may unlock specific items to help unblock your implementation/deployment, but not without confirming you understand the risks in doing so. See Risks below. 

Undeploy Fails

If the undeploy fails, be sure to retry undeploying. If it continuously fails on the same step, Salesforce Support can view these scenarios to understand if there is a workaround to fix the undeploy issue. If no workaround is identified, we may unlock specific items to help unblock your implementation/deployment, but not without confirming you understand the risks in doing so. See Risks below. 

Anything Else

Help us understand the criticality of what is blocked and why it is business impacting. Not all requests to unlock will be approved depending on the availability of a workaround. 

Marketing Cloud Next or other Standard App 

Below focuses on Marketing Cloud Next, but similar challenges exist for other customers as well:

Marketing Cloud Next customers commonly deploy out-of-the-box data streams which they later wish to undo. Most commonly, as part of Marketing Cloud Next setup process, users click “install data kits”, which automatically deploys a series of bundles -- including the Sales Data Bundle --  into their account. The less common way which these streams get deployed is by customers manually deploying managed data streams which they later wish to undo.

• The Impact: Managed bundles create locked mappings that cannot be manually undone. These locked mappings do not always match the desired use case, and can lead to unexpected consumption or muddy the customer data if done unintentionally.
• For example:
  • Assume a customer has 1 million Person Accounts in CRM and manually maps that data to the Individual DMO in Data 360.
  • Now, assume the customer later uses Marketing Cloud Next’s “install data kits” button to deploy a series of out-of-the-box data bundles.
  • As part of that broader deployment, the Sales Data Kit gets deployed, which syncs and automatically creates a locked mapping of the Lead and Contact data (2.5 million and 1 million additional records respectively) from CRM into Data 360, including the Individual DMO. As a result, the number of records in the Individual DMO grows to 4,500,000.
  • For the majority of customers, this is expected and desired. For some customers, this behavior conflicts with their desired architecture or introduces unexpected consumption costs when Data 360 processes such as Identity Resolution, Data Transforms, or Segmentation process on the increased number of records in the Individual DMO.  

Customers may request components to be unlocked that were deployed as part of the bundle. Please be sure to review the risks below.  

RISKS

For the scenarios we list above where we may offer to unlock a data kit component, we want you to understand the risks involved in doing so.