Skip to content

Commit 44f97c9

Browse files
author
ecfan
committed
Draft updates
1 parent d8a1ede commit 44f97c9

File tree

3 files changed

+9
-6
lines changed

3 files changed

+9
-6
lines changed

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

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ The example in this section transforms data in the source element from **String*
200200

201201
:::image type="content" source="media/create-maps-data-transformation-visual-studio-code/no-mapping-select-function.png" alt-text="Screenshot shows selected function named To Date.":::
202202

203-
You can also find and select any custom functions in the same way. For more information, see [Create a custom function](#create-custom-function).
203+
<!--- You can also find and select any custom functions in the same way. For more information, see [Create a custom function](#create-custom-function).--->
204204

205205
> [!NOTE]
206206
>
@@ -393,21 +393,23 @@ To confirm that the transformation works as you expect, you'll need sample input
393393

394394
1. Expand the folder that has your workflow name. From the **workflow.json** file's shortcut menu, select **Open Designer**.
395395

396-
1. On the workflow designer, follow these [general steps to add the **Data Mapper Operations** built-in action named **Transform using Data Mapper XSLT**](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
396+
1. On the workflow designer, [follow these general steps to add the **Data Mapper Operations** built-in action named **Transform using Data Mapper XSLT**](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
397397

398398
1. On the designer, select the **Transform using Data Mapper XSLT** action.
399399

400-
1. On the action information pane that appears, specify the **Content** value, and leave **Map Source** set to **Logic App**. From the **Map Name** list, select the map file (.xslt) that you want to use.
400+
1. On the action information pane that appears, specify the **Content** value, and leave **Map Source** set to **LogicApp**.
401+
402+
1. Open the **Map Name** list, and select your map (.xslt file).
401403

402404
:::image type="content" source="media/create-maps-data-transformation-visual-studio-code/transform-data-mapper-xslt-action.png" alt-text="Screenshot shows Visual Studio Code, Standard workflow designer, with selected action named Transform using Data Mapper XSLT and action properties.":::
403405

404406
To use the same **Transform using Data Mapper XSLT** action in the Azure portal, you must [add the map to the Standard logic app resource](logic-apps-enterprise-integration-maps.md?tabs=standard#add-map-to-standard-logic-app-resource).
405407

406-
<a name="create-custom-function"></a>
408+
<!---<a name="create-custom-function"></a>
407409
408410
## Create a custom function
409411
410-
To create your own function that you can use with the Data Mapper tool, follow these steps:
412+
To create your own function that you can use with Data Mapper, follow these steps:
411413
412414
1. Create an XML (.xml) file that has a meaningful name that describes your function's purpose.
413415
@@ -477,7 +479,8 @@ To create your own function that you can use with the Data Mapper tool, follow t
477479
478480
1. In the **Functions** folder, save your function's XML file.
479481
480-
1. To find your custom function in the Data Mapper tool's functions list, search for the function, or expand the **Custom functions** collection.
482+
1. To find your custom function in the Data Mapper **Functions** list, search for the function, or expand the **Custom functions** collection.
483+
-->
481484

482485
## Related content
483486

1.98 KB
Loading

0 commit comments

Comments
 (0)