Merge pull request #265657 from ecfan/net

Azure Logic Apps: More info about adding .NET assemblies and XML extension objects

Author: denrea

articles/logic-apps/logic-apps-enterprise-integration-maps.md

@@ -5,16 +5,18 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 10/04/2023
+ms.date: 02/08/2024
 ---
 
 # Add maps for transformations in workflows with Azure Logic Apps
 
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
 Workflow actions such as **Transform XML** and **Liquid** require a map to perform their tasks. For example, the **Transform XML** action requires a map to convert XML between formats. A map is an XML document that uses [Extensible Stylesheet Language Transformation (XSLT)](https://www.w3.org/TR/xslt/) language to describe how to convert data from XML to another format and has the .xslt file name extension. The map consists of a source XML schema as input and a target XML schema as output. You can define a basic transformation, such as copying a name and address from one document to another. Or, you can create more complex transformations using the out-of-the-box map operations. You can manipulate or control data by using different built-in functions, such as string manipulations, conditional assignments, arithmetic expressions, date time formatters, and even looping constructs.
 
 For example, suppose you regularly receive B2B orders or invoices from a customer who uses the YearMonthDay date format (YYYYMMDD). However, your organization uses the MonthDayYear date format (MMDDYYYY). You can define and use a map that transforms the YYYYMMDD format to the MMDDYYYY format before storing the order or invoice details in your customer activity database.
 
-This how-to guide shows how to add a map to your integration account. If you're working with a Standard logic app workflow, you can also add a map directly to your logic app resource.
+This guide shows how to add a map for your workflow to use. You can add maps either to your linked integration account, or if you have a Standard logic app, you can add maps directly to your logic app resource.
 
 ## Prerequisites
 
@@ -128,7 +130,7 @@ Your map must have the following attributes and a `CDATA` section that contains
 
 * `namespace` is the namespace in your assembly that includes the custom code.
 
-The following example shows a map that references an assembly named `XslUtilitiesLib` and calls the `circumference` method from the assembly.
+The following example shows a map that references an assembly named **XslUtilitiesLib** and calls the `circumference` method from the assembly.
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>
@@ -244,26 +246,36 @@ After your assembly finishes uploading, the assembly appears in the **Assemblies
 
 ### [Standard](#tab/standard)
 
-A Standard logic app resource supports referencing external assemblies from maps, which enable directly calling custom .NET code from XSLT maps. For more information about this capability, see [Create and run .NET Framework code from Standard workflows](create-run-custom-code-functions.md).
+A Standard logic app resource supports referencing external assemblies from maps, which enable directly calling custom .NET code from XSLT maps:
+
+| Assembly type | Description |
+|---------------|-------------|
+| **Client/SDK Assembly (.NET Framework)** | This assembly type provides storage and deployment of client and custom SDK for the .NET Framework. For example, the [SAP built-in connector](/azure/logic-apps/connectors/built-in/reference/sap/) uses these assemblies to load the SAP NCo non-redistributable DLL files. |
+| **Client/SDK Assembly (Java)** | This assembly type provides storage and deployment of custom SDK for Java. For example, the [JDBC built-in connector](/azure/logic-apps/connectors/built-in/reference/jdbc/) uses these JAR files to find JDBC drivers for custom relational databases (RDBs). |
+| **Custom Assembly (.NET Framework)** | This assembly type provides storage and deployment of custom DLLs. For example, the [**Transform XML** operation](logic-apps-enterprise-integration-transform.md) uses these assemblies for the custom transformation functions that are required during XML transformation. |
+
+For more information about this capability, see [Create and run .NET Framework code from Standard workflows](create-run-custom-code-functions.md).
+
+#### Azure portal
 
 1. In the [Azure portal](https://portal.azure.com) search box, find and open your logic app resource.
 
 1. On the logic app menu, under **Artifacts**, select **Assemblies**.
 
 1. On the **Assemblies** page toolbar, select **Add**. On the **Add Assembly** pane, under **Assembly Type**, select the following type for your assembly, based on your scenario:
 
-   | Assembly type | Description |
-   |---------------|-------------|
-   | **Client/SDK Assembly (.NET Framework)** | This assembly type provides storage and deployment of client and custom SDK for the .NET Framework. For example, the [SAP built-in connector](/azure/logic-apps/connectors/built-in/reference/sap/) uses these assemblies to load the SAP NCo non-redistributable DLL files. |
-   | **Client/SDK Assembly (Java)** | This assembly type provides storage and deployment of custom SDK for Java. For example, the [JDBC built-in connector](/azure/logic-apps/connectors/built-in/reference/jdbc/) uses these JAR files to find JDBC drivers for custom relational databases (RDBs). |
-   | **Custom Assembly (.NET Framework)** | This assembly type provides storage and deployment of custom DLLs. For example, the [**Transform XML** operation](logic-apps-enterprise-integration-transform.md) uses these assemblies for the custom transformation functions that are required during XML transformation. | 
-
 1. Now, either drag-and-drop your assemblies to the **Upload Files** area, or browse to and select your assemblies.
 
 1. When you're done, select **Upload Files**.
 
    Your selected assemblies now appear on your logic app's **Assemblies** page.
 
+#### Visual Studio Code
+
+1. In your Standard logic app project, open the following folders: **Artifacts** > **lib** > **custom** > **net472**.
+
+1. Add your assemblies to the **net472** folder.
+
 ---
 
 <a name="add-map"></a>
@@ -328,7 +340,7 @@ The following steps apply only if you want to add a map directly to your Standar
 
 1. On the **Maps** pane toolbar, select **Add**.
 
-1. On the **Add Map** pane, enter a unique name for your map and include the `.xslt` extension name.
+1. On the **Add Map** pane, enter a unique name for your map and include the **.xslt** extension name.
 
 1. Next to the **Map** box, select the folder icon. Select the map to upload.
 
@@ -374,7 +386,7 @@ To update an existing map, you have to upload a new map file that has the change
 
 1. On the **Maps** pane toolbar, select **Add**.
 
-1. Under **Add map**, enter a unique name for your map and include the `.xslt` extension name.
+1. Under **Add map**, enter a unique name for your map and include the **.xslt** extension name.
 
 1. Next to the **Map** box, select the folder icon. Select the map to upload.
 

articles/logic-apps/logic-apps-enterprise-integration-transform.md

@@ -7,16 +7,16 @@ author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 10/04/2023
+ms.date: 02/08/2024
 ---
 
 # Transform XML in workflows with Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
-In enterprise integration business-to-business (B2B) scenarios, you might have to convert XML between formats. Your logic app workflow can transform XML by using the **Transform XML** action and a predefined [*map*](logic-apps-enterprise-integration-maps.md). For example, suppose you regularly receive B2B orders or invoices from a customer that uses the YearMonthDay date format (YYYYMMDD). However, your organization uses the MonthDayYear date format (MMDDYYYY). You can create and use a map that transforms the YearMonthDay format to the MonthDayYear format before storing the order or invoice details in your customer activity database.
+In enterprise integration business-to-business (B2B) scenarios, you might have to convert XML between formats. Your logic app workflow can transform XML by using the **Transform XML** action and a predefined [*map*](logic-apps-enterprise-integration-maps.md).
 
-If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overview.md)? For more information about B2B enterprise integration, review [B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md).
+For example, suppose you regularly receive B2B orders or invoices from a customer that uses the YearMonthDay date format (YYYYMMDD). However, your organization uses the MonthDayYear date format (MMDDYYYY). You can create and use a map that transforms the YearMonthDay format to the MonthDayYear format before storing the order or invoice details in your customer activity database.
 
 ## Prerequisites
 
@@ -44,73 +44,108 @@ If you're new to logic apps, review [What is Azure Logic Apps](logic-apps-overvi
 
       > [!NOTE]
       > 
-      > The Liquid built-in connector lets you select a map that you previously uploaded to your logic app resource or to a linked integration account, but not both. 
+      > The Liquid built-in connector lets you select a map that you previously uploaded to your logic app resource or to a linked integration account, but not both.
 
     So, if you don't have or need an integration account, you can use the upload option. Otherwise, you can use the linking option. Either way, you can use these artifacts across all child workflows within the same logic app resource.
 
   You still need an integration account to store other artifacts, such as partners, agreements, and certificates, along with using the [AS2](logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](logic-apps-enterprise-integration-edifact.md) operations.
 
 ## Add Transform XML action
 
-1. In the [Azure portal](https://portal.azure.com), open your logic app resource and workflow in designer view.
+### [Standard](#tab/standard)
 
-1. If you have a blank workflow that doesn't have a trigger, add any trigger you want. This example uses the Request trigger. Otherwise, continue to the next step.
+1. In the [Azure portal](https://portal.azure.com), open your Standard logic app and workflow in the designer.
 
-   To add the Request trigger, in the designer search box, enter `HTTP request`, and select the Request trigger named **When an HTTP request is received**.
+1. If you have a blank workflow that doesn't have a trigger, [follow these general steps to add any trigger you want](create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger). Otherwise, continue to the next step.
 
-1. Under the step in your workflow where you want to add the **Transform XML** action, choose one of the following steps:
+   This example uses the **Request** trigger.
 
-   For a Consumption or ISE-based logic app workflow, choose a step:
+1. Under the step in your workflow where you want to add the **Transform XML** action, [follow these general steps to add the action named **Transform XML**](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
 
-   * To add the **Transform XML** action at the end of your workflow, select **New step**.
+1. In the **Content** box, specify the XML content that you want to transform using any XML data that you receive in the HTTP request.
 
-   * To add the **Transform XML** action between existing steps, move your pointer over the arrow that connects those steps so that the plus sign (**+**) appears. Select that plus sign, and then select **Add an action**.
+   1. To select outputs from previous operations in the workflow, in the **Transform XML** action, click inside the **Content** box, and select the dynamic content list option (lightning icon).
 
-   For a Standard-based logic app workflow, choose a step:
+   1. From the dynamic content list, select the token for the content that you want to transform.
 
-   * To add the **Transform XML** action at the end of your workflow, select the plus sign (**+**), and then select **Add an action**.
+      ![Screenshot shows Standard workflow with opened dynamic content list.](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-standard.png)
 
-   * To add the **Transform XML** action between existing steps, select the plus sign (**+**) that appears between those steps, and then select **Add an action**.
+      This example selects the **Body** token from the trigger.
 
-1. Under **Choose an operation**, select **Built-in**. In the search box, enter `transform xml`. From the actions list, select **Transform XML**.
+      > [!NOTE]
+      >
+      > Make sure that you select XML content. If the content isn't XML or is base64-encoded, 
+      > you must specify an expression that processes the content. For example, you can use 
+      > [expression functions](workflow-definition-language-functions-reference.md), 
+      > such as `base64ToBinary()` to decode content or `xml()` to process the content as XML.
+
+1. From the **Map Source** list, select the location where you uploaded your map, either your **LogicApp** resource or your **IntegrationAccount**.
+
+1. From the **Map** list, select your map.
+
+1. When you're done, save your workflow.
+
+   You're now finished setting up your **Transform XML** action. In a real world app, you might want to store the transformed data in a line-of-business (LOB) app such as SalesForce. To send the transformed output to Salesforce, add a Salesforce action.
+
+1. To test your transformation action, trigger and run your workflow. For example, for the Request trigger, send a request to the trigger's endpoint URL.
+
+   The **Transform XML** action runs after your workflow is triggered and when XML content is available for transformation.
 
-1. To specify the XML content for transformation, you can use any XML data you receive in the HTTP request. Click inside the **Content** box so that the dynamic content list appears.
+### [Consumption](#tab/consumption)
 
-   The dynamic content list shows property tokens that represent the outputs from the previous steps in the workflow. If the list doesn't show an expected property, check the trigger or action heading in the list and whether you can select **See more**.
+1. In the [Azure portal](https://portal.azure.com), open your Consumption logic app and workflow in the designer.
 
-   For a Consumption or ISE-based logic app workflow, the designer looks like this example:
+1. If you have a blank workflow that doesn't have a trigger, [follow these general steps to add any trigger you want](create-workflow-with-trigger-or-action.md?tabs=consumption#add-trigger). Otherwise, continue to the next step.
 
-   ![Screenshot showing multi-tenant designer with opened dynamic content list, cursor in "Content" box, and opened dynamic content list.](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-multi-tenant.png)
+   This example uses the **Request** trigger.
 
-   For a Standard logic app workflow, the designer looks like this example:
+1. Under the step in your workflow where you want to add the **Transform XML** action, [follow these general steps to add the action named **Transform XML**](create-workflow-with-trigger-or-action.md?tabs=consumption#add-action).
 
-   ![Screenshot showing single-tenant designer with opened dynamic content list, cursor in "Content" box, and opened dynamic content list](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-single-tenant.png)
+1. In the **Content** box, specify the XML content that you want to transform using any XML data that you receive in the HTTP request.
 
-1. From the dynamic content list, select the property token for the content you want to validate.
+   1. To select outputs from previous operations in the workflow, in the **Transform XML** action, click inside the **Content** box, which opens the dynamic content list.
 
-   This example selects the **Body** token from the trigger.
+   1. From the dynamic content list, select the token for the content that you want to transform.
 
-   > [!NOTE]
-   > Make sure that the content you select is XML. If the content is not XML or is base64-encoded, you must specify an expression 
-   > that processes the content. For example, you can use [expression functions](workflow-definition-language-functions-reference.md), 
-   > such as `base64ToBinary()` to decode content or `xml()` to process the content as XML.
+   ![Screenshot shows Consumption workflow with opened dynamic content list and cursor in Content box.](./media/logic-apps-enterprise-integration-transform/open-dynamic-content-list-consumption.png)
 
-1. To specify the map to use for transformation, open the **Map** list, and select the map that you previously added.
+      This example selects the **Body** token from the trigger.
 
-1. When you're done, make sure to save your logic app workflow.
+      > [!NOTE]
+      >
+      > Make sure that you select XML content. If the content isn't XML or is base64-encoded, 
+      > you must specify an expression that processes the content. For example, you can use 
+      > [expression functions](workflow-definition-language-functions-reference.md), 
+      > such as `base64ToBinary()` to decode content or `xml()` to process the content as XML.
+
+1. From the **Map** list, select your map.
+
+1. When you're done, save your workflow.
 
    You're now finished setting up your **Transform XML** action. In a real world app, you might want to store the transformed data in a line-of-business (LOB) app such as SalesForce. To send the transformed output to Salesforce, add a Salesforce action.
 
 1. To test your transformation action, trigger and run your workflow. For example, for the Request trigger, send a request to the trigger's endpoint URL.
 
    The **Transform XML** action runs after your workflow is triggered and when XML content is available for transformation.
 
+---
+
 ## Advanced capabilities
 
 ### Reference assemblies or call custom code from maps
 
 The **Transform XML** action supports referencing external assemblies from maps, which enable directly calling custom .NET code from XSLT maps. For more information, see [Add XSLT maps for workflows in Azure Logic Apps](logic-apps-enterprise-integration-maps.md).
 
+### Reference extension objects
+
+In Standard workflows, the **Transform XML** action supports specifying an XML extension object to use with your map.
+
+1. In the **Transform XML** action, open the **Advanced parameters** list, and select **XML Extension Object**, which adds the parameter to the action.
+
+1. In the **XML Extension Object** box, specify your extension object, for example:
+
+   :::image type="content" source="media/logic-apps-enterprise-integration-transform/xml-extension-object-standard.png" alt-text="Screenshot shows Transform XML action with XML Extension Object parameter and value." lightbox="media/logic-apps-enterprise-integration-transform/xml-extension-object-standard.png":::
+
 ### Byte order mark
 
 By default, the response from the transformation starts with a byte order mark (BOM). You can access this functionality only when you work in the code view editor. To disable this functionality, set the `transformOptions` property to `disableByteOrderMark`: