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/data-factory/parameters-data-flow.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Use this capability to make your data flows general-purpose, flexible, and reusa
29
29
* If your data flow has parameters, you will see the list of available parameters in the Parameters tab.** Click on the text box next to each parameter to enter your parameter value.
30
30
* You can choose to create your parameter expression via the pipeline control flow expression language or data flow expressions.
@@ -41,12 +41,22 @@ Inside of your data flow expressions, you can utilize the parameters using the v
41
41
42
42
## Set data flow parameters from pipeline
43
43
44
-
44
+
Once you've created your data flow with parameters, you can now execute that data flow from a pipeline with the Execute Data Flow Activity. Once you add that activity to your pipeline design canvas, you will be presented with the available data flow parameters in the activity's parameters setting tab.
When you click in the text box to fill-in parameter values, you will be presented with the Data Flow Expression Builder. Here, you can enter any expression or literal values that you wish that match the data type of the parameter. Below are examples of data flow expression and a literal string from the expression builder:
49
+
50
+
*```toInteger(Role)```
51
+
*```'this is my static literal string'```
52
+
53
+
If your parameter data type is a string, then you can choose to enter either a pipeline or a data flow expression. If you choose pipeline expression, you will instead be presented with the pipeline expression panel. Make sure to include pipeline functions inside string interpolation syntax using '@{<expression>}', for example:
0 commit comments