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/control-flow-set-variable-activity.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ To use a Set Variable activity in a pipeline, complete the following steps:
27
27
28
28
2. Search for _Set Variable_ in the pipeline Activities pane, and drag a Set Variable activity to the pipeline canvas.
29
29
30
-
3. Select the Set Variable activity on the canvas if it is not already selected, and then click the **Settings** tab to edit its details.
30
+
3. Select the Set Variable activity on the canvas if it isn't already selected, and then click the **Settings** tab to edit its details.
31
31
32
32
4. Select the variable for the Name property.
33
33
@@ -43,7 +43,7 @@ To set a pipeline return value, complete the following steps:
43
43
44
44
1. Search for _Set Variable_ in the pipeline Activities pane, and drag a Set Variable activity to the pipeline canvas.
45
45
46
-
2. Select the Set Variable activity on the canvas if it is not already selected, and then click the **Settings** tab to edit its details.
46
+
2. Select the Set Variable activity on the canvas if it isn't already selected, and then click the **Settings** tab to edit its details.
47
47
48
48
3. Select **Pipeline return value (preview)** for your **Variable type**.
49
49
@@ -66,7 +66,7 @@ value | String literal or expression object value that the variable is assigned
66
66
67
67
## Incrementing a variable
68
68
69
-
A common scenario involving variables is to use a variable as an iterator within an **Until** or **ForEach** activity. In a **Set variable** activity, you cannot reference the variable being set in the `value` field. To work around this limitation, set a temporary variable and then create a second **Set variable** activity. The second **Set variable** activity sets the value of the iterator to the temporary variable.
69
+
A common scenario involving variables is to use a variable as an iterator within an **Until** or **ForEach** activity. In a **Set variable** activity, you can't reference the variable being set in the `value` field. To work around this limitation, set a temporary variable and then create a second **Set variable** activity. The second **Set variable** activity sets the value of the iterator to the temporary variable.
70
70
71
71
Below is an example of this pattern:
72
72
@@ -126,7 +126,7 @@ Below is an example of this pattern:
126
126
}
127
127
```
128
128
129
-
Variables are currently scoped at the pipeline level. This means that they are not thread safe and can cause unexpected and undesired behavior if they are accessed from within a parallel iteration activity such as a ForEach loop, especially when the value is also being modified within that foreach activity.
129
+
Variables are currently scoped at the pipeline level. This means that they're not thread safe and can cause unexpected and undesired behavior if they are accessed from within a parallel iteration activity such as a ForEach loop, especially when the value is also being modified within that foreach activity.
0 commit comments