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
Monitor can help you debug and diagnose problems, which help you build faster, more reliable apps. Monitor provides a deep view into how an app runs by providing a log of all activities in your app as the app runs.
24
+
Monitor can help you debug and diagnose problems, which helps you build faster, more reliable apps. Monitor provides a deep view into how an app runs by providing a log of all activities in your app as it runs.
25
25
26
26
When you filter on model-driven app form-related events in Monitor, you can get information about related tables, entities, controls, and components on a form in Monitor as your app runs.
27
27
28
-
There are many situations that you may encounter where access to the information provided by Monitor will help you better understand why a form behaves a certain way. Many form issues are based on business rules, JavaScript, form events, or client API that admins and makers have set. Monitor can also help identify if the issue you experience is designed out-of-the-box or is due to a customization. It provides details that can help you answer the following questions:
28
+
There are many situations that you might encounter where access to the information provided by Monitor will help you better understand why a form behaves a certain way. Many form issues are based on business rules, JavaScript, form events, or client API that admins and makers have set. Monitor can also help identify whether the issue you experience is designed out-of-the-box or is due to a customization. It provides details that can help you answer the following questions:
29
29
30
-
- Why records aren’t showing in the related menu of an entity?
30
+
- Why aren't records showing in the related menu of an entity?
31
31
- Why is a control not editable?
32
32
- Why is a record in a read-only state?
33
33
34
34
## Filter Monitor for form-related issues
35
35
36
36
1. Sign in to [Power Apps](https://make.powerapps.com/), select **Apps**, select the app you want, and then select **Monitor** on the command bar. Follow the instructions on your screen to run the app and join the monitoring session.
37
37
38
-
You can also start a Monitor session from a model-driven app. To do this, append *&monitor=true* to the end of the URL in the browser. This displays the **Monitor** command on the model-driven app global command bar. Select **Monitor** to launch a monitoring session in a new tab.
39
-
38
+
You can also start a Monitor session from a model-driven app. To do this, append *&monitor=true* to the end of the URL in the browser. This displays the **Monitor** command on the model-driven app global command bar. Select **Monitor** to open a monitoring session in a new tab.
39
+
40
40
41
41
2. On the browser window running Monitor, select the three horizontal lines on the **Category** column to open the filter options.
42
42
43
43
> [!div class="mx-imgBorder"]
44
44
> 
45
45
46
-
3. Enter *formchecker* in the topmost **Filter** box. Don’t make any other changes and select**Apply**.
46
+
3. Enter *formchecker* in the topmost **Filter** box. Don't make any other changes. Select**Apply**.
4. Click or tap anywhere outside the filter dialog to close the dialog and refresh the list in Monitor. You can expand the **Operation** column to see the full name of the events that are tracked by selecting and holding the right-side of the column and dragging to the right. As you use the app and open and use a form, Monitor updates the list of events.
50
+
4. Click or tap anywhere outside the filter dialog to close the dialog and refresh the list in Monitor. You can expand the **Operation** column to see the full name of the events that are tracked by selecting and holding the rightside of the column and dragging to the right. As you use the app and open and use a form, Monitor updates the list of events.
51
51
52
52
> [!div class="mx-imgBorder"]
53
53
>
@@ -57,25 +57,26 @@ There are many situations that you may encounter where access to the information
57
57
For each record, you can open and view detailed information about the form event. For example, imagine you have a question about the options in the related menu tab of a form. You go to that form in the app and select the appropriate form component. In this example, the **RelatedMenu** record in the **Operation** column is selected. Next, the **Details** tab, and then **…** are selected to display additional information.
58
58
59
59
> [!div class="mx-imgBorder"]
60
-
> 
60
+
> 
61
61
62
-
To see the full details, select **+** next to the line that displays the word **data** in the title, which is line **5** in the previous screenshot. The expanded details displays all items in the related menu with information that can help you understand why an entity is, or is not, included in the related menu options. There are many types of events that are monitored including the standard form events like onload, onsave, onclose, and so on.
62
+
To see the full details, select **+** next to the line that displays the word **data** in the title, which is line **5** in the previous screenshot. The expanded details displays all items in the related menu with information that can help you understand why an entity is, or isn't, included in the related menu options. There are many types of events that are monitored, including the standard form events like onload, onsave, and onclose.
63
63
64
-
As you continue to use the app that is being monitored, Monitor updates the information in the list of events. For forms, there are many different scenarios that you can troubleshoot and find additional information on the form, control, or entity, you are working with.
64
+
As you continue to use the app that's being monitored, Monitor updates the information in the list of events. For forms, there are many different scenarios that you can troubleshoot and find additional information on the form, control, or entity you're working with.
65
65
66
66
## Supported form checking areas and events
67
67
68
-
Supported areas for form monitoring include:
68
+
Supported areas for form monitoring include the following.
69
69
70
70
|App area |Description |
71
71
|---------|---------|
72
72
|Control state | Details about the state of the visible, enabled, and label source of a control when the form is loaded. |
73
-
|Related menu | Details about the state of related menu items. Examples: <br /> Why is a menu item not displaying? <br /> Where does the menu item come from? |
74
-
|Tab / section / control state change | Details on who (via the callstack) has caused a form component such as a tab, section, or control, to change the component’s visibility and enabled state. |
75
-
|Navigation | Details about what’s causing navigation or unexpected dialogs by tracing the callstack of these Xrm.Navigation client API methods: openAlertDialog(), openConfirmDialog(), openDialog(), openErrorDialog(), navigateTo(), openForm(), openTaskFlow(), openUrl(), openWebResource() |
76
-
|Unsupported customizations | Details about unsupported client API access before the form is ready. Examples: <br /> Accessing parent.Xrm.Page in iFrame before the form is fully loaded. <br /> Accessing Xrm.Page in form web resource outside of form handler contexts using window.setTimeout() to periodically call the form client API. <br /> Accessing Xrm.Page in updateView() method of the Power Apps control framework control code. |
73
+
|Related menu | Details about the state of related menu items. Examples: <br /> Why is a menu item not being displayed? <br /> Where does the menu item come from? |
74
+
|Tab / section / control state change | Details on who (via the callstack) has caused a form component—such as a tab, section, or control—to change the component's visibility and enabled state. |
75
+
|Navigation | Details about what's causing navigation or unexpected dialogs by tracing the callstack of these Xrm.Navigation client API methods: openAlertDialog(), openConfirmDialog(), openDialog(), openErrorDialog(), navigateTo(), openForm(), openTaskFlow(), openUrl(), openWebResource() |
76
+
|Unsupported customizations | Details about unsupported client API access before the form is ready. Examples: <br /> Accessing parent.Xrm.Page in iFrame before the form is fully loaded. <br /> Accessing Xrm.Page in a form web resource outside of form handler contexts using window.setTimeout() to periodically call the form client API. <br /> Accessing Xrm.Page in updateView() method of the Power Apps control framework control code. |
77
+
78
+
Examples of the supported form-related events in Monitor include:
77
79
78
-
Examples of the supported form-related events in Monitor:
79
80
- FormEvents.onsave
80
81
- XrmNavigation
81
82
- FormEvents.onload
@@ -86,4 +87,3 @@ Examples of the supported form-related events in Monitor:
0 commit comments