From 2ca940d197d312203d5a76a4e9c8fcac2c37cf40 Mon Sep 17 00:00:00 2001 From: Cedric Date: Tue, 21 Oct 2025 18:09:43 +0200 Subject: [PATCH] Update bas-external-system.mdx with .env configuration I did run the 2nd time into this small tiny and time-consuming issue. So, for the next time, everyone should be aware of it :) --- docs-js/guides/bas-external-system.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs-js/guides/bas-external-system.mdx b/docs-js/guides/bas-external-system.mdx index 858fa3d086a..5b36fc0a3c8 100644 --- a/docs-js/guides/bas-external-system.mdx +++ b/docs-js/guides/bas-external-system.mdx @@ -181,6 +181,11 @@ destinations="[{ }]" ``` +Please keep in mind: A `.env` file has to represent environment-variables (like `destinations` in the example above) within 1 line. So, to get represented within your `process.env.destinations` variable, save the `.env` file as one-liner: +``` +destinations="[{"name": "","url": "http://.dest","proxyConfiguration":{"host": "127.0.0.1","port": 8887,"protocol":"http"}}]" +``` + Fill in the `name` and `url` of the destination you [configured on SAP BTP](#prerequisite-2-cloud-connector-and-destination-setup). You can use the same pattern `.dest` that you have used for [testing the connection](#checking-the-connection). The proxy host and port are from the `http_proxy` environment variables BAS creates for you.