From 56d11ff8fa5c109934d069f0224bb8aea82e3163 Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Mon, 9 Feb 2026 15:47:06 +0100 Subject: [PATCH 1/3] tenant-specific deployment parameters --- guides/multitenancy/mtxs.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/guides/multitenancy/mtxs.md b/guides/multitenancy/mtxs.md index 63894855d..30c0e6c21 100644 --- a/guides/multitenancy/mtxs.md +++ b/guides/multitenancy/mtxs.md @@ -1296,6 +1296,12 @@ The _SaasProvisioningService_ is a façade for the _DeploymentService_ to adapt Requests are implicitly asynchronous when `status_callback` is set. ::: +##### Passing tenant-specific deployment parameters + +Using the `"_"` section of the payload, you can pass deployment parameters for an individual tenant. The syntax is identical with the [static deployment configuration of the DeploymentService](#deployment-config). + +In most cases, the requests are received from a third party, so the deployment parameters need to be added in [a handler implementation](#adding-custom-lifecycle-event-handlers) for service `cds.xt.SaasProvisioningService`. + ##### Example Usage
@@ -1436,7 +1442,12 @@ Content-Type: application/json { "subscribedTenantId": "t1", "subscribedSubdomain": "subdomain1", - "eventType": "CREATE" + "eventType": "CREATE", + "_": { + "hdi": { + ... + } + } } ``` From e8bda962fb827acaec2e7f7a1d3ce7a508dcae58 Mon Sep 17 00:00:00 2001 From: ecklie <52252271+ecklie@users.noreply.github.com> Date: Wed, 11 Feb 2026 11:24:53 +0100 Subject: [PATCH 2/3] Update guides/multitenancy/mtxs.md Co-authored-by: Steffen Waldmann --- guides/multitenancy/mtxs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/multitenancy/mtxs.md b/guides/multitenancy/mtxs.md index 30c0e6c21..66724e2ef 100644 --- a/guides/multitenancy/mtxs.md +++ b/guides/multitenancy/mtxs.md @@ -1298,7 +1298,7 @@ Requests are implicitly asynchronous when `status_callback` is set. ##### Passing tenant-specific deployment parameters -Using the `"_"` section of the payload, you can pass deployment parameters for an individual tenant. The syntax is identical with the [static deployment configuration of the DeploymentService](#deployment-config). +Using the `"_"` section of the payload, you can pass deployment parameters for an individual tenant. The syntax is identical with the [static deployment configuration of `cds.xt.DeploymentService`](#deployment-config). In most cases, the requests are received from a third party, so the deployment parameters need to be added in [a handler implementation](#adding-custom-lifecycle-event-handlers) for service `cds.xt.SaasProvisioningService`. From 13a116faf427b7bf43bb44e3761a7a624d414a14 Mon Sep 17 00:00:00 2001 From: ecklie <52252271+ecklie@users.noreply.github.com> Date: Wed, 11 Feb 2026 11:25:07 +0100 Subject: [PATCH 3/3] Update guides/multitenancy/mtxs.md Co-authored-by: Steffen Waldmann --- guides/multitenancy/mtxs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/multitenancy/mtxs.md b/guides/multitenancy/mtxs.md index 66724e2ef..ce5efd6c7 100644 --- a/guides/multitenancy/mtxs.md +++ b/guides/multitenancy/mtxs.md @@ -1300,7 +1300,7 @@ Requests are implicitly asynchronous when `status_callback` is set. Using the `"_"` section of the payload, you can pass deployment parameters for an individual tenant. The syntax is identical with the [static deployment configuration of `cds.xt.DeploymentService`](#deployment-config). -In most cases, the requests are received from a third party, so the deployment parameters need to be added in [a handler implementation](#adding-custom-lifecycle-event-handlers) for service `cds.xt.SaasProvisioningService`. +In most cases, the requests are received from a third party, so the deployment parameters need to be added in [a handler implementation](#adding-custom-lifecycle-event-handlers) for `cds.xt.SaasProvisioningService`. ##### Example Usage