Skip to content

Commit c2bc1f4

Browse files
Merge pull request #213503 from ecfan/sap
Azure Logic Apps: SAP - Make note about decoding schemas more visible
2 parents 9e8dece + 4c7648d commit c2bc1f4

File tree

1 file changed

+16
-15
lines changed

1 file changed

+16
-15
lines changed

articles/logic-apps/logic-apps-using-sap-connector.md

Lines changed: 16 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Connect to SAP systems
3-
description: Access and manage SAP resources by automating workflows with Azure Logic Apps.
2+
title: Connect to SAP
3+
description: Connect to SAP resources from workflows in Azure Logic Apps.
44
services: logic-apps
55
ms.suite: integration
66
author: divyaswarnkar
@@ -11,7 +11,7 @@ ms.date: 08/22/2022
1111
tags: connectors
1212
---
1313

14-
# Connect to SAP systems from Azure Logic Apps
14+
# Connect to SAP from workflows in Azure Logic Apps
1515

1616
[!INCLUDE [logic-apps-sku-consumption](../../includes/logic-apps-sku-consumption.md)]
1717

@@ -1581,6 +1581,19 @@ By default, strong typing is used to check for invalid values by performing XML
15811581

15821582
Optionally, you can download or store the generated schemas in repositories, such as a blob, storage, or integration account. Integration accounts provide a first-class experience with other XML actions, so this example shows how to upload schemas to an integration account for the same logic app workflow by using the Azure Resource Manager connector.
15831583

1584+
> [!NOTE]
1585+
>
1586+
> Schemas use base64-encoded format. To upload schemas to an integration account, you must decode them first
1587+
> by using the `base64ToString()` function. The following example shows the code for the `properties` element:
1588+
>
1589+
> ```json
1590+
> "properties": {
1591+
> "Content": "@base64ToString(items('For_each')?['Content'])",
1592+
> "ContentType": "application/xml",
1593+
> "SchemaType": "Xml"
1594+
> }
1595+
> ```
1596+
15841597
1. In the workflow designer, under the trigger, select **New step**.
15851598

15861599
1. In the search box, enter `resource manager` as your filter. Select **Create or update a resource**.
@@ -1599,18 +1612,6 @@ Optionally, you can download or store the generated schemas in repositories, suc
15991612
16001613
![Screenshot that shows the Azure Resource Manager action with a "for each" loop.](./media/logic-apps-using-sap-connector/azure-resource-manager-action-foreach.png)
16011614
1602-
> [!NOTE]
1603-
> The schemas use base64-encoded format. To upload the schemas to an integration account, they must be decoded
1604-
> by using the `base64ToString()` function. Here's an example that shows the code for the `"properties"` element:
1605-
>
1606-
> ```json
1607-
> "properties": {
1608-
> "Content": "@base64ToString(items('For_each')?['Content'])",
1609-
> "ContentType": "application/xml",
1610-
> "SchemaType": "Xml"
1611-
> }
1612-
> ```
1613-
16141615
1. Save your logic app workflow. On the designer toolbar, select **Save**.
16151616
16161617
### Test your workflow

0 commit comments

Comments
 (0)