Extend the use of Data 360 by building a sharing functionality using data kits and packages.
- Clean Up Data 360 Metadata in Older Sandboxes
Remove outdated Data 360 metadata from sandboxes created before August 2024 and use them for a new setup without a refresh. The cleanup process identifies any non-Data 360 entities that reference Data 360 entities and packages containing outdated metadata. - Deploy Data Kits Across Data Spaces
Replicate your Data 360 metadata and process definitions between data spaces within the same sandbox. Previously, to replicate configurations, such as calculated insights and segments, you manually recreated them in each data space. This process was time-consuming and prone to error. With local data kit deployment, you can create a standard data kit in your default data space. Then, deploy the data kit to other data spaces to ensure consistency and centralized governance. This feature supports standard data kits only. It doesn’t support DevOps data kits. - Extend Data 360 by Using Custom Code with Code Extension (Beta)
With code extension, you can bring your custom Python code into Data 360 to extend Data 360's native capabilities. If native Data 360 features don't meet your business requirements, deploy your custom logic across supported Data 360 features such as batch data transforms. For example, if you need advanced data transformations for your business use case, you can deploy custom business logic to Data 360 to implement your requirements. Data Custom Code SDK is the toolkit for creating and validating custom code for code extension. - Protect Active Connector Settings in Data 360 Sandbox
Ensure configuration stability and reduce the manual work required to re-authorize connections in Data 360 sandboxes. If a connector is active in the target org, DevOps data kit deployments now ignore changes to connector attributes to avoid overwriting your settings. This protection applies to all data stream connectors.