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-workflow-definition-language.md
+4-5Lines changed: 4 additions & 5 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: reference
8
-
ms.date: 12/07/2023
8
+
ms.date: 06/13/2024
9
9
---
10
10
11
11
# Schema reference guide for the Workflow Definition Language in Azure Logic Apps
@@ -276,8 +276,7 @@ Here is the general structure for an output definition:
276
276
| <*key-type*> | Yes | int, float, string, securestring, bool, array, JSON object | The type for the output return value |
277
277
| <*key-value*> | Yes | Same as <*key-type*> | The output return value |
278
278
279
-
To get the output from a workflow run, review your logic app's run history and details in the Azure portal or use the [Workflow REST API](/rest/api/logic/workflows). You can also pass output to external systems, for example,
280
-
Power BI so that you can create dashboards.
279
+
To get the output from a workflow run, review your logic app's run history and details in the Azure portal or use the [Workflow REST API](/rest/api/logic/workflows). You can also pass output to external systems, for example, Power BI so that you can create dashboards.
281
280
282
281
<aname="operators"></a>
283
282
@@ -289,8 +288,8 @@ In [expressions](#expressions) and [functions](#functions), operators perform sp
289
288
|----------|------|
290
289
|`'`| To use a string literal as input or in expressions and functions, wrap the string only with single quotation marks, for example, `'<myString>'`. Do not use double quotation marks (`""`), which conflict with the JSON formatting around an entire expression. For example: <br><br>**Yes**: length('Hello') </br>**No**: length("Hello") <br><br>When you pass arrays or numbers, you don't need wrapping punctuation. For example: <br><br>**Yes**: length([1, 2, 3]) </br>**No**: length("[1, 2, 3]") |
291
290
|`[]`| To reference a value at a specific position (index) in an array or inside a JSON object, use square brackets, for example: <br><br>- To get the second item in an array: <br><br>`myArray[1]` <br><br>- To access the properties inside a JSON object: <br><br>*Example 1*: <br>`setProperty(<object>, '<parent-property>', addProperty(<object>['<parent-property>'], '<child-property>', <value>)` <br><br>*Example 2*: <br>`lastIndexOf(triggerBody()?['subject'],'some string')`|
292
-
|`.`| To reference a property in an object, use the dot operator. For example, to get the `name` property for a `customer` JSON object: <br><br>`"@parameters('customer').name"`|
293
-
|`?`| To reference null properties in an object without a runtime error, use the question mark operator. For example, to handle null outputs from a trigger, you can use this expression: <br><br>`@coalesce(trigger().outputs?.body?.<someProperty>, '<property-default-value>')`|
291
+
|`.`| To reference a property in an object, use the dot operator. For example, to get the `name` property for a `customer` JSON object: <br><br>`"parameters('customer').name"`|
292
+
|`?`| To reference null properties in an object without a runtime error, use the null-ignore (**?**) operator. For example, to handle null outputs from a trigger, you can use the following expression: <br><br>`coalesce(trigger().outputs?.body?['<someProperty>'], '<property-default-value>')`|
0 commit comments