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)
0 commit comments