Skip to content

Commit 153288f

Browse files
authored
Clarity and cleanup edits
1 parent c6f3766 commit 153288f

File tree

1 file changed

+5
-22
lines changed

1 file changed

+5
-22
lines changed

articles/logic-apps/create-maps-data-transformation-visual-studio-code.md

Lines changed: 5 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -22,26 +22,11 @@ To exchange messages that have different XML or JSON formats in an Azure Logic A
2222

2323
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.
2424

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.
2626

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.
3128

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
4530

4631
- The Data Mapper extension currently works only in Visual Studio Code running on Windows operating systems.
4732

@@ -53,9 +38,7 @@ This how-to guide shows how to complete the following tasks:
5338

5439
- The map layout and item position are currently automatic and read only.
5540

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.
5942

6043
## Prerequisites
6144

@@ -457,4 +440,4 @@ To use the same **Transform using Data Mapper XSLT** action in the Azure portal,
457440

458441
## Next steps
459442

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

Comments
 (0)