Data 360: Data Kit Considerations & Common Issues

Considerations

• Objects deployed using a Standard Data Kit can only be updated by modifying and redeploying the same Data Kit. The same limitation applies to DevOps Data Kits.
  
  • Standard Data Kits and DevOps Data Kits cannot be used interchangeably to update the same object.
  • Objects that were created manually in the org cannot be updated using any Data Kit.
• Segments of Type DBT (created via API) cannot be added to a Data Kit by end users. These segments are excluded from adding to Data Kit.
• Data Lake Objects (DLOs) that are linked to a Data Stream cannot be manually added to a Data Kit.
  • Select the Data Stream and the associated DLO will be automatically added.
  • Only DLOs that are created from a Data Transform can be added.
• If there are any dependencies on a Data Model Object (DMO) or its associated fields, please ensure that the DMO and all relevant fields are explicitly added to the Data Kit.
  • If there is more than one page of dependencies, click into each page to select everything.
• In case you encounter an error related to FieldSrcTrgtRelationship, it indicates that the Field Source Target Relationship must also be included in the package. Please add it to proceed with the deployment.
  • Example Error: CustomField(Account__dlm.rel_1734601266475_end__c) DMO relationships require a FieldSrcTrgtRelationship that references this lookup field.
  • To resolve this, navigate to the Package Manager and select the relevant package.
  • Click on “Add” and choose the Component Type as Field Source Target Relationship.
  • From the list, locate the required DMO relationship, check the corresponding box, and click on “Add to Package”.
  • Note: To add DMO relationships to a package, the Data Model Object (DMO) must be of type Standard or Custom. DMOs of other types are not supported for packaging DMO relationships.
• For Data Kit deployments involving Data Stream bundles, only standard tags are currently supported.

Environment Considerations

1. Production to Production:
   1. A major consideration here is that it is not possible to put non-default objects into a Data Kit.
2. Sandbox to Production or Sandbox to Sandbox:
   1. If following the correct steps of: Create Data Kit as a DevOps Data Kit, Create Outbound Rules, Create Inbound Rules, and Deploy. Then, it is possible to utilize non-default objects.
   2. When deploying utilizing the above method, if you are running into errors when deploying objects, please ensure that all of the objects being deployed have an API Name no longer than 40 characters (maximum).

Common Issues

• Failures caused due to mismatch of Data Kit type.
  • For change sets moving from Sandbox to Production, the Data Kit must be of DevOps type.
• Error: Expected source (e.g. User_00Dxxxx__dll) to have field (e.g. ColumnName__c) 
  •  Ensure that the field exists in the source object and the Data Cloud Salesforce Connector permission set has the proper permissions as per Enable Object and Field Permissions for CRM Connections.
• Failures related to Publishing Sequence
  • Streams are associated with connections, deployment requires the connection to be included when deploying stream changes.
• Connection becomes inactive in the Target org if the Data stream are included in Data Kit.
  • Article : Data 360: Impact of Deploying via Data kit on existing External Integrations Connectors.
• Data Transforms blocks installing Data Transforms via Data Kits in non-default Data Space.
  • Currently Data Transforms tied to non-default Data Space cannot be deployed via Data Kits.