You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -1581,6 +1581,19 @@ By default, strong typing is used to check for invalid values by performing XML
1581
1581
1582
1582
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.
1583
1583
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:
1. In the workflow designer, under the trigger, select **New step**.
1585
1598
1586
1599
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
1599
1612
1600
1613

1601
1614
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:
0 commit comments