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/workflow-definition-language-functions-reference.md
+13-10Lines changed: 13 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -179,16 +179,19 @@ To change a value's type or format, you can use these conversion functions. For
179
179
180
180
## Implicit data type conversions
181
181
182
-
The Logic Apps service automatically or implicitly converts values between specific data types, which means that you don't need to manually or explicitly convert between those types by using the relevant expressions. In fact, if these expressions appear in the designer or code view, Logic Apps removes the expressions after you save your logic app because the conversions happen automatically.
183
-
184
-
This table describes the implicit data type conversions and the expressions you'd typically use for those conversions but should omit because Logic Apps will remove the expressions.
185
-
186
-
| From | To |
187
-
|------|----|
188
-
|**Binary** or **File**| - **Byte**: `base64(<value>)` <br>- **DataUri**: `concat('data:;base64,',<value>)`|
The Logic Apps service automatically or implicitly performs some data type conversions, which means that you can omit the corresponding expressions to manually or explicitly make those conversions. However, if you use these expressions in your logic app, save your logic app, reload your logic app, and edit the expression's parameter values, Logic Apps removes those expressions from designer view. To avoid this Logic Apps behavior, don't edit the expression's parameter values. If Logic Apps removes the expressions anyway, those expressions reappear after you save your logic app.
183
+
184
+
This table describes the functions or expressions that are affected by this Logic Apps behavior and should omit:
185
+
186
+
| Function or expression | Example use cases |
187
+
|------------------------|-------------------|
188
+
|`base64(<value>)`| - Converting from **Binary** or **File** to **Byte** <br>- Converting from **Other** to **Byte**|
189
+
|`base64ToBinary(<value>)`| Converting from **Byte** to **Binary** or **File**|
190
+
|`base64ToString(<value>)`| Converting from **Byte** to **Other**|
191
+
|`base64(decodeDataUri(<value>))`| Converting from **DataUri** to **Byte**|
192
+
|`concat('data:;base64,',<value>)`| - Converting from **Binary** or **File** to **DataUri** <br>- Converting from **Byte** to **DataUri**|
193
+
|`concat('data:,',encodeUriComponent(<value>))`| Converting from **Other** to **DataUri**|
194
+
|`decodeDataUri(<value>)`| Converting from **DataUri** to **Binary**, **File**, or **Other** type |
192
195
|||
193
196
194
197
If you use non-string values where strings are expected as inputs, Logic Apps automatically converts the non-string values into strings, for example:
0 commit comments