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/logic-apps-perform-data-operations.md
+17-23Lines changed: 17 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: logic-apps
5
5
ms.suite: integration
6
6
ms.reviewer: estfan, azla
7
7
ms.topic: how-to
8
-
ms.date: 03/28/2025
8
+
ms.date: 03/31/2025
9
9
# Customer intent: As a developer using Azure Logic Apps, I want to perform various data operations on various data types for my workflow in Azure Logic Apps.
10
10
---
11
11
@@ -32,7 +32,7 @@ This how-to guide shows how you can work with data in your logic app workflow in
32
32
33
33
## Data operation actions
34
34
35
-
The following sections summarize the data operations you can use and are organized based on the source data types that the operations work on, but each description appears alphabetically.
35
+
The following sections summarize the data operations you can use. The operations are organized based on the source data types that the operations work on, but each description appears alphabetically.
36
36
37
37
### JSON actions
38
38
@@ -126,7 +126,7 @@ To try the **Compose** action, follow these steps by using the workflow designer
126
126
This example uses the Azure portal and a sample workflow with the **Recurrence** trigger followed by several **Variables** actions named **Initialize variable**. These actions are set up to create two string variables and an integer variable.
@@ -148,14 +148,14 @@ To try the **Compose** action, follow these steps by using the workflow designer
148
148
}
149
149
```
150
150
151
-
1. For each variable declaration in the object syntax, place the insertion cursor as described in the following table. Then select the dynamic content list (lightning icon), and choose the corresponding definition from the **Variables** list:
151
+
1. For each variable declaration in the object syntax, place the insertion cursor as described in the following table. Select the dynamic content list (lightning icon), and then select the corresponding definition from the **Variables** list:
152
152
153
153
| JSON property | Cursor location | Variable |
154
-
|--- | --- | ---|
154
+
|---------------|-----------------|----------|
155
155
| `age` | Before comma | `ageVar` |
156
156
| `fullName` | - Last name: Before comma <br> - First name: After comma | "`lastNameVar`, `firstNameVar`" |
157
157
158
-
The following example shows the finished sample **Compose** action:
158
+
The following example shows how to prepare the **Compose** action:
159
159
160
160
:::image type="content" source="media/logic-apps-perform-data-operations/compose-lightning-insert-cursor.png" alt-text="Screenshot shows Standard workflow, Compose action, insert cursor location, and lightning icon." lightbox="media/logic-apps-perform-data-operations/compose-lightning-insert-cursor.png":::
161
161
@@ -319,10 +319,7 @@ In the **Create CSV table** action, keep the **Header** column empty. On each ro
319
319
320
320
In the action's JSON definition, within the `columns` array, set the `header` property to an empty string. For each `value` property, dereference each array property that you want.
321
321
322
-
1. From the designer, switch to code view.
323
-
324
-
***Consumption**: On the designer toolbar, select **Code view**.
325
-
***Standard**: On the workflow navigation menu, under **Tools**, select **Code**.
322
+
1. On the designer toolbar, select **Code view**.
326
323
327
324
1. In the code editor, find the action's `columns` array. For each column of array values that you want, add an empty `header` property and the following expression for the `value` property:
328
325
@@ -358,7 +355,7 @@ In the action's JSON definition, within the `columns` array, set the `header` pr
358
355
```
359
356
360
357
> [!NOTE]
361
-
> If you copy the example into your code, be sure to include the `runAfter` action at the end of the `Create_CSV_table` definition.
358
+
> If you copy the example into your code, make sure you include the `runAfter` action at the end of the `Create_CSV_table` definition.
362
359
363
360
1. Switch back to designer view to review the results.
364
361
@@ -508,10 +505,7 @@ In the **Create HTML table** action, keep the **Header** column empty. On each r
508
505
509
506
In the action's JSON definition, within the `columns` array, set the `header` property to an empty string. For each `value` property, dereference each array property that you want.
510
507
511
-
1. From the designer, switch to code view.
512
-
513
-
***Consumption**: On the designer toolbar, select **Code view**.
514
-
***Standard**: On the workflow navigation menu, under **Tools**, select **Code**.
508
+
1. On the designer toolbar, select **Code view**.
515
509
516
510
1. In the code editor, find the action's `columns` array. For each column of array values that you want, add an empty `header` property and the following expression for the `value` property:
517
511
@@ -547,7 +541,7 @@ In the action's JSON definition, within the `columns` array, set the `header` pr
547
541
```
548
542
549
543
> [!NOTE]
550
-
> If you copy the example into your code, be sure to include the `runAfter` action at the end of the `Create_HTML_table` definition.
544
+
> If you copy the example into your code, make sure you include the `runAfter` action at the end of the `Create_HTML_table` definition.
551
545
552
546
1. Switch back to designer view to review the results.
553
547
@@ -565,7 +559,7 @@ To confirm whether the **Create HTML table** action creates the expected results
565
559
566
560
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
567
561
568
-
If you used the Office 365 Outlook action, the following example shows the result:
562
+
If you use the Office 365 Outlook - Send an email action, the following example shows the result:
569
563
570
564
:::image type="content" source="media/logic-apps-perform-data-operations/create-html-table-email-results.png" alt-text="Screenshot shows email with results from action named Create HTML table." lightbox="media/logic-apps-perform-data-operations/create-html-table-email-results.png":::
571
565
@@ -683,7 +677,7 @@ To confirm whether **Filter array** action creates the expected results, send yo
683
677
684
678
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
685
679
686
-
If you used the Office 365 Outlook action, the following example shows the result:
680
+
If you use the Office 365 Outlook - Send an email action, the following example shows the result:
687
681
688
682
:::image type="content" source="media/logic-apps-perform-data-operations/filter-array-email-results.png" alt-text="Screenshot shows email with results from action named Filter array." lightbox="media/logic-apps-perform-data-operations/filter-array-email-results.png":::
689
683
@@ -769,7 +763,7 @@ To confirm whether the **Join** action creates the expected results, send yourse
769
763
770
764
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
771
765
772
-
If you used the Office 365 Outlook action, the following example shows the result:
766
+
If you use the Office 365 Outlook - Send an email action, the following example shows the result:
773
767
774
768
:::image type="content" source="media/logic-apps-perform-data-operations/join-email-results.png" alt-text="Screenshot shows email with results from the Join action." lightbox="media/logic-apps-perform-data-operations/join-email-results.png":::
775
769
@@ -952,21 +946,21 @@ To confirm whether the **Parse JSON** action creates the expected results, send
952
946
953
947
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
954
948
955
-
If you used the Office 365 Outlook action, the following example shows the result:
949
+
If you use the Office 365 Outlook - Send an email action, the following example shows the result:
956
950
957
951
:::image type="content" source="media/logic-apps-perform-data-operations/parse-json-email-results.png" alt-text="Screenshot shows email with results from action named Parse JSON." lightbox="media/logic-apps-perform-data-operations/parse-json-email-results.png":::
958
952
959
953
<a name="select-action"></a>
960
954
961
955
## Select action
962
956
963
-
By default, the **Select** action creates an array that contains JSON objects built from the values in an existing array. For example, you can create a JSON object for each value in an integer array by specifying the properties that each JSON object must have and mapping the values from the source array to those properties. Although you can change the component JSON objects, the output array always has the same number of items as the source array. To use the output array from the **Select** action, subsequent actions must either accept arrays as input, or you might have to transform the output array into another compatible format.
957
+
By default, the **Select** action creates an array that contains JSON objects built from the values in an existing array. For example, you can create a JSON object for each value in an integer array. Specify the properties that each JSON object must have and map the values from the source array to the properties. Although you can change the component JSON objects, the output array always has the same number of items as the source array. To use the output array from the **Select** action, subsequent actions must either accept arrays as input, or you might have to transform the output array into another compatible format.
964
958
965
959
To try the **Select** action, follow these steps by using the workflow designer. Or, if you prefer working in the code view editor, you can copy the example **Select** and **Initialize variable** action definitions from this guide into your own logic app's underlying workflow definition: [Data operation code examples - Select](logic-apps-data-operations-code-samples.md#select-action-example). For more information about this action in your underlying workflow definition, see [Select action](logic-apps-workflow-actions-triggers.md#select-action).
966
960
967
961
> [!TIP]
968
962
>
969
-
> For an example that creates create an array with strings or integers built from the values in a JSON object array,
963
+
> For an example that creates an array with strings or integers built from the values in a JSON object array,
970
964
> see the **Select** and **Initialize variable** action definitions in
@@ -1072,7 +1066,7 @@ To confirm whether the **Select** action creates the expected results, send your
1072
1066
1073
1067
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
1074
1068
1075
-
If you used the Office 365 Outlook action, the following example shows the result:
1069
+
If you use the Office 365 Outlook - Send an email action, the following example shows the result:
1076
1070
1077
1071
:::image type="content" source="media/logic-apps-perform-data-operations/select-email-results.png" alt-text="Screenshot shows email with results from the Select action." lightbox="media/logic-apps-perform-data-operations/select-email-results.png":::
0 commit comments