Skip to content

Commit 587af39

Browse files
committed
updates pre review feedback
1 parent b46492b commit 587af39

9 files changed

+17
-23
lines changed

articles/logic-apps/logic-apps-perform-data-operations.md

Lines changed: 17 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: estfan, azla
77
ms.topic: how-to
8-
ms.date: 03/28/2025
8+
ms.date: 03/31/2025
99
# 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.
1010
---
1111

@@ -32,7 +32,7 @@ This how-to guide shows how you can work with data in your logic app workflow in
3232

3333
## Data operation actions
3434

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

3737
### JSON actions
3838

@@ -126,7 +126,7 @@ To try the **Compose** action, follow these steps by using the workflow designer
126126
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.
127127

128128
| Operation | Properties and values |
129-
| --- | --- |
129+
|-----------|-----------------------|
130130
| **Initialize variable** | - **Name**: firstNameVar <br>- **Type**: String <br>- **Value**: Sophia |
131131
| **Initialize variable** | - **Name**: lastNameVar <br>- **Type**: String <br>- **Value**: Owens |
132132
| **Initialize variable** | - **Name**: ageVar <br>- **Type**: Integer <br>- **Value**: 35 |
@@ -148,14 +148,14 @@ To try the **Compose** action, follow these steps by using the workflow designer
148148
}
149149
```
150150

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:
152152

153153
| JSON property | Cursor location | Variable |
154-
| --- | --- | --- |
154+
|---------------|-----------------|----------|
155155
| `age` | Before comma | `ageVar` |
156156
| `fullName` | - Last name: Before comma <br> - First name: After comma | "`lastNameVar`, `firstNameVar`" |
157157

158-
The following example shows the finished sample **Compose** action:
158+
The following example shows how to prepare the **Compose** action:
159159

160160
:::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":::
161161

@@ -319,10 +319,7 @@ In the **Create CSV table** action, keep the **Header** column empty. On each ro
319319

320320
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.
321321

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**.
326323

327324
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:
328325

@@ -358,7 +355,7 @@ In the action's JSON definition, within the `columns` array, set the `header` pr
358355
```
359356

360357
> [!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.
362359
363360
1. Switch back to designer view to review the results.
364361

@@ -508,10 +505,7 @@ In the **Create HTML table** action, keep the **Header** column empty. On each r
508505

509506
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.
510507

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**.
515509

516510
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:
517511

@@ -547,7 +541,7 @@ In the action's JSON definition, within the `columns` array, set the `header` pr
547541
```
548542

549543
> [!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.
551545
552546
1. Switch back to designer view to review the results.
553547

@@ -565,7 +559,7 @@ To confirm whether the **Create HTML table** action creates the expected results
565559

566560
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
567561

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:
569563

570564
:::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":::
571565

@@ -683,7 +677,7 @@ To confirm whether **Filter array** action creates the expected results, send yo
683677

684678
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
685679

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:
687681

688682
:::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":::
689683

@@ -769,7 +763,7 @@ To confirm whether the **Join** action creates the expected results, send yourse
769763

770764
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
771765

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:
773767

774768
:::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":::
775769

@@ -952,21 +946,21 @@ To confirm whether the **Parse JSON** action creates the expected results, send
952946

953947
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
954948

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:
956950

957951
:::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":::
958952

959953
<a name="select-action"></a>
960954

961955
## Select action
962956

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

965959
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).
966960

967961
> [!TIP]
968962
>
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,
970964
> see the **Select** and **Initialize variable** action definitions in
971965
> [Data operation code examples - Select](logic-apps-data-operations-code-samples.md#select-action-example).
972966

@@ -1072,7 +1066,7 @@ To confirm whether the **Select** action creates the expected results, send your
10721066

10731067
1. Save your workflow, and then manually run your workflow. On the designer toolbar, select **Run** > **Run**.
10741068

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:
10761070

10771071
:::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":::
10781072

23.5 KB
Loading
4.23 KB
Loading
1.78 KB
Loading
2.46 KB
Loading
-1.52 KB
Loading
5.02 KB
Loading
1.94 KB
Loading
2.99 KB
Loading

0 commit comments

Comments
 (0)