Deploy data graphs with the same base name to multiple data spaces in the same org. When you deploy a data graph through a data kit workflow ( UI and POST API) specifically, Data 360 prefixes the API name with the target data space name, so your data graphs coexist across data spaces without naming collisions.
Where: This change applies to Data 360 in Enterprise, Performance, Unlimited, and Developer editions.
When: This feature is available starting in August 2026.
Why: Before this release, data graph API names weren't scoped to data spaces, so a data graph named CustomerDG in dataspace ds1 couldn't coexist with CustomerDG in data space ds2. With data space-aware naming, you can deploy the same data kit workflow ( UI and POST API) to multiple data spaces and keep each data graph distinct.
How: For non-default data spaces, the data graph API name follows the pattern <dataspace>_<dgName>. For example, deploying dg1 to the ds1 data space produces ds1_dg1. Deployments to the default data space does not prefix data space identifier in the API name. Data 360 applies the prefix idempotently, so a name that already includes the data space prefix isn't prefixed again. Note, this is only for data graphs getting deployed via data kits ( UI and POST API) . For those getting deployed via Connect API/ data graph UI (except managed datakits), the current naming convention continues. This behavior does not change the API name of previously deployed data graphs via data kits in case of updates.
Data space-aware naming applies to data graphs deployed through managed package deployment from the data graph UI, managed and unmanaged package deployment from the Data Kit UI, and the Data Kit Deploy Connect API. Data graphs created from scratch in the Data Graph UI, unmanaged package creation in the Data Graph UI, and the direct Data Graph Create Connect API keep their original names.