Skip to content

Commit 369c8f4

Browse files
committed
Include customer feedback
1 parent 238e884 commit 369c8f4

File tree

1 file changed

+51
-19
lines changed

1 file changed

+51
-19
lines changed

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

Lines changed: 51 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -115,7 +115,7 @@ To confirm whether the **Compose** action creates the expected results, send you
115115

116116
1. In your logic app, add an action that can send you the results from the **Compose** action.
117117

118-
1. In that action, click anywhere you want the results to appear. When the dynamic content list opens, under the **Compose** action, select **Output**.
118+
1. In that action, click anywhere you want the results to appear. When the dynamic content list opens, under the **Compose** action, select **Output**.
119119

120120
This example uses the **Send an email** action and includes the **Output** fields in the email's body and subject:
121121

@@ -131,11 +131,9 @@ To confirm whether the **Compose** action creates the expected results, send you
131131

132132
## Create CSV table action
133133

134-
To create a comma-separated value (CSV) table that has the properties and values from JavaScript Object Notation (JSON) objects in an array, use the **Create CSV table** action. You can then use
135-
the resulting table in actions that follow the **Create CSV table** action.
134+
To create a comma-separated value (CSV) table that has the properties and values from JavaScript Object Notation (JSON) objects in an array, use the **Create CSV table** action. You can then use the resulting table in actions that follow the **Create CSV table** action.
136135

137-
If you prefer working in the code view editor, you can copy the example **Create CSV table** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition:
138-
[Data operation code examples - Create CSV table](../logic-apps/logic-apps-data-operations-code-samples.md#create-csv-table-action-example)
136+
If you prefer working in the code view editor, you can copy the example **Create CSV table** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition: [Data operation code examples - Create CSV table](../logic-apps/logic-apps-data-operations-code-samples.md#create-csv-table-action-example)
139137

140138
1. In the [Azure portal](https://portal.azure.com) or Visual Studio, open your logic app in Logic App Designer.
141139

@@ -165,13 +163,32 @@ If you prefer working in the code view editor, you can copy the example **Create
165163

166164
![Finished "Create CSV table" action](./media/logic-apps-perform-data-operations/finished-create-csv-table-action.png)
167165

168-
By default, this action automatically creates the columns based on the array items. To manually create the column headers and values, open the **Columns** list. To provide only custom values, select **Custom**. To provide custom column headers too, in the **Header** property, specify the column name. In the **Key** property, specify the column value.
166+
1. Save your logic app. On the designer toolbar, select **Save**.
167+
168+
By default, the **Columns** property is set to automatically create the columns based on the array items. To specify custom column headers and values, follow these steps:
169+
170+
1. Open the **Columns** list, and select **Custom**.
171+
172+
1. To specify custom column headers, in the **Header** property, specify the column name.
173+
174+
1. To specify custom values, in the **Key** property, specify the column value.
169175

170176
> [!TIP]
171177
> To create user-friendly tokens for the properties in JSON objects so you can select those properties as inputs,
172178
> use the [Parse JSON](#parse-json-action) before calling the **Create CSV table** action.
173179
174-
1. Save your logic app. On the designer toolbar, select **Save**.
180+
To omit the column headers, switch from designer view to code view, and edit the action's definition to use only the `value` property in the `columns` definition, and omit the `header` property, for example:
181+
182+
```json
183+
"Create_CSV_table": {
184+
"inputs": {
185+
"columns": [
186+
{ "value": "@item()?['Id']" },
187+
{ "value": "@item()?['Subject']" }
188+
]
189+
}
190+
}
191+
```
175192

176193
For more information about this action in your underlying workflow definition, see the [Table action](../logic-apps/logic-apps-workflow-actions-triggers.md#table-action).
177194

@@ -213,7 +230,7 @@ If you prefer working in the code view editor, you can copy the example **Create
213230

214231
![Add action](./media/logic-apps-perform-data-operations/add-create-table-action.png)
215232

216-
* To add an action between steps, move your mouse over the connecting arrow so the plus sign (+) appears. Select the plus sign, and then select **Add an action**.
233+
* To add an action between steps, move your mouse over the connecting arrow so the plus sign (**+**) appears. Select the plus sign, and then select **Add an action**.
217234

218235
1. Under **Choose an action**, in the search box, enter `create html table` as your filter. From the actions list, select the **Create HTML table** action.
219236

@@ -229,13 +246,32 @@ If you prefer working in the code view editor, you can copy the example **Create
229246

230247
![Finished "Create HTML table" action](./media/logic-apps-perform-data-operations/finished-create-html-table-action.png)
231248

232-
By default, this action automatically creates the columns based on the array items. To manually create the column headers and values, open the **Columns** list. To provide only custom values, select **Custom**. To provide custom column headers too, in the **Header** property, specify the column name. In the **Key** property, specify the column value.
249+
1. Save your logic app. On the designer toolbar, select **Save**.
250+
251+
By default, the **Columns** property is set to automatically create the columns based on the array items. To specify custom column headers and values, follow these steps:
252+
253+
1. Open the **Columns** list, and select **Custom**.
254+
255+
1. To specify custom column headers, in the **Header** property, specify the column name.
256+
257+
1. To specify custom values, in the **Key** property, specify the column value.
233258

234259
> [!TIP]
235260
> To create user-friendly tokens for the properties in JSON objects so you can select those properties as inputs,
236-
> use the [Parse JSON](#parse-json-action) before calling the **Create HTML table** action.
261+
> use the [Parse JSON](#parse-json-action) before calling the **Create CSV table** action.
237262
238-
1. Save your logic app. On the designer toolbar, select **Save**.
263+
To omit the column headers, switch from designer view to code view, and edit the action's definition to use only the `value` property in the `columns` definition, and omit the `header` property, for example:
264+
265+
```json
266+
"Create_HTML_table": {
267+
"inputs": {
268+
"columns": [
269+
{ "value": "@item()?['Id']" },
270+
{ "value": "@item()?['Subject']" }
271+
]
272+
}
273+
}
274+
```
239275

240276
For more information about this action in your underlying workflow definition, see the [Table action](../logic-apps/logic-apps-workflow-actions-triggers.md#table-action).
241277

@@ -273,8 +309,7 @@ To create a smaller array that has items, which meet specific criteria, from an
273309
> For actions to use the array output from the **Filter array** action, either those actions must accept arrays as input, or you might
274310
> have to transform the output array into another compatible format.
275311
276-
If you prefer working in the code view editor, you can copy the example **Filter array** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition:
277-
[Data operation code examples - Filter array](../logic-apps/logic-apps-data-operations-code-samples.md#filter-array-action-example)
312+
If you prefer working in the code view editor, you can copy the example **Filter array** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition: [Data operation code examples - Filter array](../logic-apps/logic-apps-data-operations-code-samples.md#filter-array-action-example)
278313

279314
1. In the [Azure portal](https://portal.azure.com) or Visual Studio, open your logic app in Logic App Designer.
280315

@@ -340,8 +375,7 @@ To confirm whether **Filter array** action creates the expected results, send yo
340375

341376
To create a string that has all the items from an array and separate those items with a specific delimiter character, use the **Join** action. You can then use the string in actions that follow after the **Join** action.
342377

343-
If you prefer working in the code view editor, you can copy the example **Join** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition:
344-
[Data operation code examples - Join](../logic-apps/logic-apps-data-operations-code-samples.md#join-action-example)
378+
If you prefer working in the code view editor, you can copy the example **Join** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition: [Data operation code examples - Join](../logic-apps/logic-apps-data-operations-code-samples.md#join-action-example)
345379

346380
1. In the [Azure portal](https://portal.azure.com) or Visual Studio, open your logic app in Logic App Designer.
347381

@@ -401,8 +435,7 @@ To confirm whether the **Join** action creates the expected results, send yourse
401435

402436
To reference or access properties in JavaScript Object Notation (JSON) content, you can create user-friendly fields or tokens for those properties by using the **Parse JSON** action. That way, you can select those properties from the dynamic content list when you specify inputs for your logic app. For this action, you can either provide a JSON schema or generate a JSON schema from your sample JSON content or payload.
403437

404-
If you prefer working in the code view editor, you can copy the example **Parse JSON** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition:
405-
[Data operation code examples - Parse JSON](../logic-apps/logic-apps-data-operations-code-samples.md#parse-json-action-example)
438+
If you prefer working in the code view editor, you can copy the example **Parse JSON** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition: [Data operation code examples - Parse JSON](../logic-apps/logic-apps-data-operations-code-samples.md#parse-json-action-example)
406439

407440
1. In the [Azure portal](https://portal.azure.com) or Visual Studio, open your logic app in Logic App Designer.
408441

@@ -478,8 +511,7 @@ To create an array that has JSON objects built from values in an existing array,
478511
> For actions to use the array output from the **Select** action, either those actions must accept
479512
> arrays as input, or you might have to transform the output array into another compatible format.
480513
481-
If you prefer working in the code view editor, you can copy the example **Select** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition:
482-
[Data operation code examples - Select](../logic-apps/logic-apps-data-operations-code-samples.md#select-action-example)
514+
If you prefer working in the code view editor, you can copy the example **Select** and **Initialize variable** action definitions from this article into your own logic app's underlying workflow definition: [Data operation code examples - Select](../logic-apps/logic-apps-data-operations-code-samples.md#select-action-example)
483515

484516
1. In the [Azure portal](https://portal.azure.com) or Visual Studio, open your logic app in Logic App Designer.
485517

0 commit comments

Comments
 (0)