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
Copy file name to clipboardExpand all lines: articles/logic-apps/create-maps-data-transformation-visual-studio-code.md
+5-22Lines changed: 5 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,26 +22,11 @@ To exchange messages that have different XML or JSON formats in an Azure Logic A
22
22
23
23
To visually create and edit a map, you can use Visual Studio Code with the Data Mapper extension within the context of a Standard logic app project. The Data Mapper tool provides a unified experience for XSLT mapping and transformation using drag and drop gestures, a prebuilt functions library for creating expressions, and a way to manually test the maps that you create and use in your workflows.
24
24
25
-
After you create your map, you can directly call that map from a workflow in your logic app project or from a workflow in the Azure portal. For this task, add the **Data Mapper Operations** action named **Transform using Data Mapper XSLT**to your workflow. To use this action in the Azure portal, add the map to either of the following resources:
25
+
After you create your map, you can directly call that map from a workflow in your logic app project or from a workflow in the Azure portal. For this task, you can use the **Data Mapper Operations** action named **Transform using Data Mapper XSLT**in your workflow.
26
26
27
-
- An integration account for a Consumption or Standard logic app resource
28
-
- The Standard logic app resource itself
29
-
30
-
This how-to guide shows how to complete the following tasks:
27
+
This how-to guide shows how to create a blank data map, choose your source and target schemas, select schema elements to start mapping, create various mappings, save and test your map, and then call the map from a workflow in your logic app project.
31
28
32
-
- Create a blank data map.
33
-
- Specify the source and target schemas to use.
34
-
- Navigate the map.
35
-
- Select the target and source elements to map.
36
-
- Create a direct mapping between elements.
37
-
- Create a complex mapping between elements.
38
-
- Create a loop between arrays.
39
-
- Crete an if condition between elements.
40
-
- Save the map.
41
-
- Test the map.
42
-
- Call the map from a workflow in your logic app project.
43
-
44
-
## Limitations
29
+
## Limitations and known issues
45
30
46
31
- The Data Mapper extension currently works only in Visual Studio Code running on Windows operating systems.
47
32
@@ -53,9 +38,7 @@ This how-to guide shows how to complete the following tasks:
53
38
54
39
- The map layout and item position are currently automatic and read only.
55
40
56
-
## Known issues
57
-
58
-
The Data Mapper extension currently works only with schemas in flat folder-structured projects.
41
+
- The Data Mapper extension currently works only with schemas in flat folder-structured projects.
59
42
60
43
## Prerequisites
61
44
@@ -457,4 +440,4 @@ To use the same **Transform using Data Mapper XSLT** action in the Azure portal,
457
440
458
441
## Next steps
459
442
460
-
- For data transformations using B2B operations in Azure Logic Apps, see [Add maps for transformations in workflows with Azure Logic Apps](logic-apps-enterprise-integration-maps.md)
443
+
- For data transformations using B2B operations in Azure Logic Apps, see [Add maps for transformations in workflows with Azure Logic Apps](logic-apps-enterprise-integration-maps.md)
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-enterprise-integration-maps.md
+29-15Lines changed: 29 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,11 +3,9 @@ title: Add maps to use with workflows
3
3
description: Add maps for transform operations in workflows with Azure Logic Apps.
4
4
services: logic-apps
5
5
ms.suite: integration
6
-
author: divyaswarnkar
7
-
ms.author: divswa
8
6
ms.reviewer: estfan, azla
9
7
ms.topic: how-to
10
-
ms.date: 08/22/2022
8
+
ms.date: 04/18/2023
11
9
---
12
10
13
11
# Add maps for transformations in workflows with Azure Logic Apps
@@ -22,21 +20,23 @@ This article shows how to add a map to your integration account. If you're worki
22
20
23
21
* An Azure account and subscription. If you don't have a subscription yet, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
24
22
25
-
* The map that you want to add. To create maps, you can use the following tools with the [Enterprise Integration SDK](https://aka.ms/vsmapsandschemas):
23
+
* The map that you want to add. To create maps, you can use the following tools:
26
24
27
-
* Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools Extension](https://aka.ms/vsenterpriseintegrationtools).
25
+
* Visual Studio Code and the Data Mapper extension. To call the maps created with Data Mapper from your workflow, you must use the **Data Mapper Operations** action named **Transform using Data Mapper XSLT**, not the **XML Operations** action named **Transform XML**. For more information, see [Create maps for data transformation with Visual Studio Code](create-maps-data-transformation-visual-studio-code.md).
28
26
29
-
* Visual Studio 2015 and the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0](https://aka.ms/vsmapsandschemas) extension.
27
+
* Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools extension](https://aka.ms/vsenterpriseintegrationtools).
30
28
31
-
> [!NOTE]
32
-
> Don't install the extension alongside the BizTalk Server extension. Having both extensions might
33
-
> produce unexpected behavior. Make sure that you only have one of these extensions installed.
34
-
>
35
-
> On high resolution monitors, you might experience a [display problem with the map designer](/visualstudio/designers/disable-dpi-awareness)
36
-
> in Visual Studio. To resolve this display problem, either [restart Visual Studio in DPI-unaware mode](/visualstudio/designers/disable-dpi-awareness#restart-visual-studio-as-a-dpi-unaware-process),
37
-
> or add the [DPIUNAWARE registry value](/visualstudio/designers/disable-dpi-awareness#add-a-registry-entry).
29
+
* Visual Studio 2015 and the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0 extension](https://aka.ms/vsmapsandschemas).
38
30
39
-
For more information, review the [Create maps](#create-maps) section in this article.
31
+
> [!NOTE]
32
+
> Don't install the Microsoft Azure Logic Apps Enterprise Integration Tools extension alongside the BizTalk Server extension.
33
+
> Having both extensions might produce unexpected behavior. Make sure that you only have one of these extensions installed.
34
+
>
35
+
> On high resolution monitors, you might experience a [display problem with the map designer](/visualstudio/designers/disable-dpi-awareness)
36
+
> in Visual Studio. To resolve this display problem, either [restart Visual Studio in DPI-unaware mode](/visualstudio/designers/disable-dpi-awareness#restart-visual-studio-as-a-dpi-unaware-process),
37
+
> or add the [DPIUNAWARE registry value](/visualstudio/designers/disable-dpi-awareness#add-a-registry-entry).
38
+
39
+
For more information, review the [Create maps](#create-maps) section in this article.
40
40
41
41
* Based on whether you're working on a Consumption or Standard logic app workflow, you'll need an [integration account resource](logic-apps-enterprise-integration-create-integration-account.md). Usually, you need this resource when you want to define and store artifacts for use in enterprise integration and B2B workflows.
42
42
@@ -98,7 +98,21 @@ This article shows how to add a map to your integration account. If you're worki
98
98
99
99
## Create maps
100
100
101
-
To create an XSLT document to use as a map, create an integration project in Visual Studio 2019 or 2015 using the [Enterprise Integration SDK](https://aka.ms/vsmapsandschemas). In the integration project, you can build an integration map file, which lets you visually map items between two XML schema files. These tools offer the following map capabilities:
101
+
You can create maps using either Visual Studio Code with the Data Mapper extension or Visual Studio with the Microsoft Azure Logic Apps Enterprise Integration Tools extension.
102
+
103
+
### Visual Studio Code
104
+
105
+
When you create maps using Visual Studio Code and the Data Mapper extension, you can call these maps from your workflow, but only with the **Data Mapper Operations** action named **Transform using Data Mapper XSLT**, not the **XML Operations** action named **Transform XML**. For more information, see [Create maps for data transformation with Visual Studio Code](create-maps-data-transformation-visual-studio-code.md).
106
+
107
+
### Visual Studio
108
+
109
+
When you create maps using Visual Studio, you'll need to create an integration project with either of the following tools:
110
+
111
+
* Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools extension](https://aka.ms/vsenterpriseintegrationtools)
112
+
113
+
* Visual Studio 2015 and the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0 extension](https://aka.ms/vsmapsandschemas).
114
+
115
+
In the integration project, you can build an integration map file, which lets you visually map items between two XML schema files. These tools offer the following map capabilities:
102
116
103
117
* You work with a graphical representation of the map, which shows all the relationships and links you create.
0 commit comments