Sandbox tooling

Improve configuration accuracy across sandboxes and seamlessly export and import sandbox configurations between sandboxes with the sandbox tooling feature. Use sandbox tooling to reduce the time to value for the implementation process and move successful configurations across sandboxes.

You can use the sandbox tooling feature to select different objects and export them into a package. A package can consist of a single object or multiple objects. Any objects that are included in a package must be from the same sandbox.

Objects supported for sandbox tooling supported-objects

The sandbox tooling feature provides you with the ability to export Adobe Real-Time Customer Data Platform and Adobe Journey Optimizer objects into a package.

Real-time Customer Data Platform objects real-time-cdp-objects

The table below lists Adobe Real-Time Customer Data Platform objects that are currently supported for sandbox tooling:

The following objects are imported but are in a draft or disabled status:

Adobe Journey Optimizer objects abobe-journey-optimizer-objects

The table below lists Adobe Journey Optimizer objects that are currently supported for sandbox tooling and limitations:

Surfaces (for example, presets) are not copied over. The system automatically selects the closest possible match on the destination sandbox based on the message type and surface name. If there are no surfaces found on the target sandbox, then the surface copy will fail, causing the message copy to fail because a message requires a surface to be available for setup. In this case, at least one surface needs to be created for the right channel of the message in order for the copy to work.

Custom identity types are not supported as dependent objects when exporting a journey.

Export objects into a package export-objects

This example documents the process of exporting a schema and adding it to a package. You can use the same process to export other objects, for example, datasets, journeys, and many more.

Add object to a new package add-object-to-new-package

Select Schemas from the left navigation and then select the Browse tab, which lists the schemas available. Next, select the ellipsis (...) next to the selected schema, and a dropdown displays controls. Select Add to package from the dropdown.

From the Add to package dialog, select the Create new package option. Provide a Name for your package and an optional Description, then select Add.

You are returned to the Schemas environment. You can now add additional objects to the package you created by following the next steps listed below.

Add an object to an existing package and publish add-object-to-existing-package

To view a list of the available schemas, select Schemas from the left navigation and then select the Browse tab. Next, select the ellipsis (...) next to the selected schema to see control options in a dropdown menu. Select Add to package from the dropdown.

The Add to package dialog appears. Select the Existing package option, then select the Package name dropdown and select the package required. Finally, select Add to confirm your choices.

The list of objects added to the package is listed. To publish the package and make it available to be imported into sandboxes, select Publish.

Select Publish to confirm to publication of the package.

You are returned to the Packages tab in the Sandboxes environment, where you can see the new published package.

Import a package to a target sandbox import-package-to-target-sandbox

To import the package into a target sandbox, navigate to the Sandboxes Browse tab and select the plus (+) option beside the sandbox name.

Using the dropdown menu, select the Package name you want to import to the targeted sandbox. Add an optional Job name, which will be used for future monitoring. By default, unified profile will be disabled when the package’s schemas are imported. Toggle Enable schemas for profile to enable this, then select Next.

The Package object and dependencies page provides a list of all assets included in this package. The system automatically detects dependent objects that are required for successfully importing selected parent objects. Any missing attributes are displayed at the top of the page. Select View details for a more detailed breakdown.

To use an existing object, select the pencil icon beside the dependent object.

The options to create new or use existing are displayed. Select Use existing.

The Field group dialog shows a list of field groups available for the object. Select the field groups required, then select Save.

You are returned to the Package object and dependencies page. From here, select Finish to complete the package import.

Monitor import jobs and view import objects details

To view the imported objects and imported details, navigate to the Sandboxes Imports tab and select the package from the list. Alternatively, use the search bar to search for the package.

View imported objects view-imported-objects

On the Imports tab in the Sandboxes environment, select View imported objects from the right details pane.

Select View imported objects from the right details pane on the Imports tab in the Sandboxes environment.

Use the arrows to expand objects to view the full list of fields that have been imported into the package.

View import details view-import-details

Select View import details from the right details pane in the Imports tab in the Sandboxes environment.

The Import details dialog shows a detailed breakdown of the imports.

Video tutorial

The following video is intended to support your understanding of sandbox tooling, and outlines how to create a new package, publish a package, and import a package.

Next steps

This document demonstrated how to use the sandbox tooling feature within the Experience Platform UI. For information on sandboxes, see the sandbox user guide.

For steps on performing different operations using the Sandbox API, see the sandbox developer guide. For a high-level overview of sandboxes in Experience Platform, refer to the overview documentation.