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: powerapps-docs/maker/canvas-apps/functions/function-select.md
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,15 +26,15 @@ If you want one or more controls in the gallery to perform different actions fro
26
26
27
27
**Select** queues the target **OnSelect** for later processing, which may happen after the current formula has finished being evaluated. **Select** doesn't cause the target **OnSelect** to evaluate immediately, nor does **Select** wait for **OnSelect** to finish being evaluated.
28
28
29
-
**Select** can't cross the boundaries of container controls, such as a gallery or a form. Controls within a container control can only be the subject of a **Select** function in formulas that are inside the same container control. You can't use **Select** across screens.
29
+
You can't use **Select** across screens.
30
30
31
31
You can use **Select** only with controls that have an **OnSelect** property.
32
32
33
33
You can use **Select** only in [behavior formulas](../working-with-formulas-in-depth.md).
34
34
35
35
A control can't **Select** itself directly or indirectly through other controls.
36
36
37
-
The select function can also be used in repeating container controls such as gallery. For example, it can be used to specify the row or column to select in a gallery and the control to select within that row or column of the gallery.
37
+
The select function can also be used with a gallery. For example, it can be used to specify the row or column to select in a gallery and the control to select within that row or column of the gallery. When you select a row or column, the gallery selection changes and the **OnSelect** formula on the gallery control is evaluated. If a control within the row or column is provided, the **OnSelect** formula for the child control will be evaluated.
38
38
39
39
## Syntax
40
40
**Select**( *Control* )
@@ -55,15 +55,15 @@ The select function can also be used in repeating container controls such as gal
55
55
56
56
-*Gallery*
57
57
58
-
```Select(Gallery1, Row1)```
58
+
```Select(Gallery1, 1)```
59
59
60
-
Simulates a user selecting Row1 in Gallery1.
60
+
Simulates a user selecting row 1 or column 1 in Gallery1.
61
61
62
62
-*Gallery*
63
63
64
-
```Select(Gallery1, Row1, ChildControl1)```
64
+
```Select(Gallery1, 1, ChildControl1)```
65
65
66
-
Simulates a user selecting ChildConttrol1 in Row1 of Gallery1.
66
+
Simulates a user selecting ChildConttrol1 in row 1 or column 1 of Gallery1.
67
67
68
68
#### Basic usage
69
69
@@ -109,4 +109,13 @@ The select function can also be used in repeating container controls such as gal
109
109
110
110
Use individual controls in the gallery to take actions that differ from the gallery's default action.
111
111
112
-

112
+

113
+
114
+
7. On the same screen, add a **Button** control, and set its **OnSelect** property to this formula:
115
+
116
+
**Select( Gallery1,2,Image1 )**
117
+
118
+
8. While holding down the Alt key, select the button.
119
+
120
+
A **Image Selected** notification appears across the top of your app. The button click simulated selecting the image in row 2 of the gallery.
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/functions/function-setproperty.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ search.app:
16
16
---
17
17
# SetProperty function in Power Apps Test Studio
18
18
19
-
The SetProperty function simulates interactions with input controls as if the user had entered or set a value on the control. The following properties can be set using the SetProperty function.
19
+
The SetProperty function simulates interactions with input controls as if the user had entered or set a value on the control. This function is only available if you are writing tests in the Power Apps Test Studio. The following properties can be set using the SetProperty function.
20
20
21
21
## Syntax
22
22
@@ -43,7 +43,9 @@ The SetProperty function simulates interactions with input controls as if the us
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/functions/function-trace.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,20 @@ search.audienceType:
14
14
search.app:
15
15
- PowerApps
16
16
---
17
-
# Trace function in Power Apps Test Studio
17
+
# Trace function
18
18
19
-
Trace is an optional test expression that can be used to provide additional information in your test results from the **OnTestCaseComplete** event. Trace event messages, as well as any messages for both passed and failed assertions, are contained in a Traces table in the TestCaseResult record. The Traces table has two properties, Message and Timestamp.
19
+
When used with Test Studio, Trace is an optional expression that can be used to provide additional information in your test results from the **OnTestCaseComplete** event. Trace event messages, as well as any messages for both passed and failed assertions, are contained in a Traces table in the TestCaseResult record. The Traces table has two properties, Message and Timestamp.
20
+
21
+
If you have allowed your app to send telemetry data to Azure Application Insights, the Trace function can also be used to send custom event or diagnostic information to your Application Insights resource. You can inspect this data in Application Insights to help diagnose problems or understand usage of your apps and features. Trace information used in Tests will also be recorded in Application Insights. All Trace messages can also be viewed in the Power Apps Monitor tool, which will help in debugging or identifying issues for real-time diagnostic sessions for your app.
20
22
21
23
## Syntax
22
24
23
-
*Trace(message)*
25
+
*Trace(message, severity, custom_record )*
24
26
25
-
-*Message* – Required. A text value that creates a record in the Traces table in the TestCaseResult record.
27
+
-*Message* – Required. The information to be traced. In tests, this creates a record in the Traces table in the TestCaseResult record.
28
+
-*Severity* - Optional. The severity level of the Trace recorded in Application Insights. Options are Information, Warning or Error.
29
+
-*custom_record* - Optional. A record containing custom data that will be recorded in Application Insights.
0 commit comments