Skip to content

Commit 130ff89

Browse files
author
ecfan
committed
Updates per feedback
1 parent 237633e commit 130ff89

File tree

1 file changed

+25
-4
lines changed

1 file changed

+25
-4
lines changed

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

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: azure-logic-apps
66
ms.suite: integration
77
ms.reviewer: estfan, shahparth, azla
88
ms.topic: how-to
9-
ms.date: 04/18/2025
9+
ms.date: 07/15/2025
1010
# Customer intent: As a developer, I want to convert data between different formats for a Standard workflow in Azure Logic Apps by creating a map with Visual Studio Code.
1111
---
1212

@@ -24,15 +24,21 @@ This how-to guide shows how to create an empty data map, choose your source and
2424

2525
## Limitations and known issues
2626

27-
- Data Mapper currently works only in Visual Studio Code running on Windows operating systems.
28-
2927
- Data Mapper is currently available only in Visual Studio Code, not the Azure portal, and only from within Standard logic app projects, not Consumption logic app projects.
3028

29+
The front-end experience for Data Mapper is available as open source in the public [GitHub repository for the Azure Logic Apps team](https://github.com/Azure/LogicAppsUX/tree/main/libs/data-mapper-v2). For more information, see the following resources:
30+
31+
- [Welcome to Azure Logic Apps UX](https://agreeable-beach-04ed7ce1e.5.azurestaticapps.net/)
32+
33+
- [New and improved Data Mapper UX in Azure Logic Apps](https://techcommunity.microsoft.com/blog/IntegrationsonAzureBlog/%F0%9F%9A%80-new--improved-data-mapper-ux-in-azure-logic-apps-%E2%80%93-now-in-public-preview/4377088)
34+
35+
- Data Mapper currently works only in Visual Studio Code running on Windows operating systems.
36+
3137
- Data Mapper currently doesn't support schemas that use the comma-separated values (.csv) file format.
3238

3339
- The **Code** pane in Data Mapper is currently read only.
3440

35-
- The layout and item positions in Data Mapper are currently automatic and read only.
41+
- On the data mapper surface, the layout and positions for functions are movable, but schema nodes are static.
3642

3743
- The **Filter** function correctly processes numeric conditions that are enclosed by double quotation marks, for example, **">=10"**. However, this function currently doesn't consistently behave for string comparisons such as a check on whether an item name is **"= 'Pen'"**.
3844

@@ -42,8 +48,12 @@ This how-to guide shows how to create an empty data map, choose your source and
4248

4349
- To use the maps that you create with Data Mapper with workflows in the Azure portal, you must [add them directly to your Standard logic app resource](logic-apps-enterprise-integration-maps.md?tabs=standard#add-map-to-standard-logic-app-resource).
4450

51+
For non-blocking bugs or feature requests, [open an item with the **Data Mapper** label in GitHub repository for the Azure Logic Apps team](https://github.com/Azure/LogicAppsUX/issues/new?template=data_mapper.yml).
52+
4553
## Prerequisites
4654

55+
- An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
56+
4757
- [Visual Studio Code and the Azure Logic Apps (Standard) extension](create-single-tenant-workflows-visual-studio-code.md#prerequisites) to create Standard logic app workflows.
4858

4959
> [!NOTE]
@@ -378,6 +388,15 @@ Visual Studio Code saves your data map as the following artifacts:
378388
- A Data Mapper (**<*your-map-name*>.lml**) file in the **Artifacts** > **MapDefinitions** project folder
379389
- A data map (**<*your-map-name*>.xslt**) file in the **Artifacts** > **Maps** project folder
380390

391+
> [!TIP]
392+
>
393+
> To organize your artifacts at deeper levels, you can use the following folders and subfolders:
394+
>
395+
> - **Artifacts**/**MapDefinitions**
396+
> - **Artifacts**/**Schemas**
397+
> - **Artifacts**/**DataMapper**/**Extensions**/**Functions**
398+
> - **Artifacts**/**DataMapper**/**Extensions**/**InlineXslt**
399+
381400
## Test your map
382401

383402
To confirm that the transformation works as you expect, you'll need sample input data.
@@ -599,6 +618,8 @@ The following **SampleFunctions.xml** file shows the implementation for the foll
599618
</customfunctions>
600619
```
601620

621+
622+
602623
## Related content
603624

604625
- [Add maps for transformations in workflows with Azure Logic Apps](logic-apps-enterprise-integration-maps.md)

0 commit comments

Comments
 (0)