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/developer/model-driven-apps/clientapi/debug-JavaScript-code.md
+10-10Lines changed: 10 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ contributors:
18
18
19
19
Custom logic using JavaScript in model-driven apps are contained within JavaScript web resources. JavaScript web resources provide the libraries that define functions developers register as event handlers.
20
20
21
-
In a model-driven app viewed within a web browser, you can use developer tools that all modern browsers provide. With these tools you can locate the JavaScript libraries loaded in the model-driven application, set break points and debug your code using common methods.
21
+
In a model-driven app viewed within a web browser, you can use developer tools that all modern browsers provide. With these tools you can locate the JavaScript libraries loaded in the model-driven application, set break points, and debug your code using common methods.
22
22
23
-
Model-driven apps viewed using mobile apps on Android, or the Windows desktop app require some additional steps. See:
23
+
Model-driven apps viewed using mobile apps on Android, or the Windows desktop app require some more steps. See:
24
24
25
25
-[Debug JavaScript in mobile apps on Android](#debug-javascript-in-mobile-apps-on-android)
26
26
-[Debug JavaScript in mobile apps on iOS](#debug-javascript-in-mobile-apps-on-ios)
@@ -33,7 +33,7 @@ Model-driven apps viewed using mobile apps on Android, or the Windows desktop ap
33
33
34
34
More information:
35
35
36
-
-[mdn web docs: What are browser developer tools?](https://developer.mozilla.org/docs/Learn/Common_questions/What_are_browser_developer_tools).
36
+
-[Mdn web docs: What are browser developer tools?](https://developer.mozilla.org/docs/Learn/Common_questions/What_are_browser_developer_tools).
If you click the **Show Details** link, you can find the details that include: event name, function name, web resource name, solution name, and publisher name.
49
+
If you select the **Show Details** link, you can find the details that include: event name, function name, web resource name, solution name, and publisher name.
50
50
51
51
```
52
52
Xrm.Navigation.openalertDialog is not a function
@@ -69,7 +69,7 @@ In this case, the name of the function was incorrect, `openalertDialog` should b
69
69
70
70
While using JavaScript web resources for mobile scenarios, you can use your Android device to debug your mobile-specific code and ensure it works as expected.
71
71
72
-
To debug JavaScript in mobile apps on Android, you must complete the three steps below:
72
+
To debug JavaScript in mobile apps on Android, you must complete the following three steps:
73
73
74
74
### 1. Configure your device
75
75
@@ -86,7 +86,7 @@ To debug JavaScript in mobile apps on Android, you must complete the three steps
86
86
87
87
1. In the mobile app, go to the list of Power Apps and select on the menu button.
88
88
1. Make sure that the toggle **Enable remote debugging for model-driven apps** is on.
89
-
1.When enabling this option, there's a confirmation dialog. Select **Confirm**.
89
+
1.There's a confirmation dialog when you enable this option. Select **Confirm**.
90
90
91
91
### 3. Debug from your development machine
92
92
@@ -96,15 +96,15 @@ To debug JavaScript in mobile apps on Android, you must complete the three steps
1.Click**Yes** to install Windows Developer Mode package when prompted.
140
+
1.Select**Yes** to install Windows Developer Mode package when prompted.
141
141
1. Once Device Portal is enabled, **note the URL you will use to connect using localhost**. On most devices, it's `https://localhost:50080`
142
142
1. For debugging Power Apps / Field Service Mobile locally, you can continue with **Restrict to loopback connections only** enabled and **Authentication** disabled (otherwise you need to set a user password)
143
143
@@ -162,7 +162,7 @@ Use the **Run command** (shortcut is `Windows + R`) and use the following deep l
162
162
163
163
:::image type="content" source="media/devtools-configuration-for-windows.png" alt-text="Inspect in the DevTools screen":::
0 commit comments