Skip to content

Commit 82408d5

Browse files
Live publish for 07 August 2024.
2 parents 9da98f0 + 6df64c1 commit 82408d5

File tree

9 files changed

+150
-110
lines changed

9 files changed

+150
-110
lines changed

powerapps-docs/developer/data-platform/asynchronous-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -589,7 +589,7 @@ Here's what to look for in the results:
589589

590590
### Queries for file storage
591591

592-
When the [Data column](reference/entities/asyncoperation.md#BKMK_Data) of the `AsyncOperation` table is larger than 4 MB, the data in that column is saved in file storage. The [DataBlobId column](reference/entities/asyncoperation.md#BKMK_DataBlobId) has a value when the row uses file storage. To save space, you might want to identify and delete these records. Use the following queries to discover these records
592+
Depending on the size of the [Data column](reference/entities/asyncoperation.md#BKMK_Data) of the `AsyncOperation` table, the data in that column may be saved in file storage. The [DataBlobId column](reference/entities/asyncoperation.md#BKMK_DataBlobId) has a value when the row uses file storage. To save space, you might want to identify and delete these records. Use the following queries to discover these records
593593

594594
#### AsyncOperation file storage datablobid count
595595

powerapps-docs/developer/model-driven-apps/clientapi/debug-JavaScript-code.md

Lines changed: 30 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ applies_to:
66
- "Dynamics 365 (online)"
77
author: adrianorth
88
ms.author: aorth
9-
ms.date: 01/31/2023
9+
ms.date: 08/07/2024
1010
ms.reviewer: jdaly
1111
search.audienceType:
1212
- developer
@@ -18,11 +18,12 @@ contributors:
1818

1919
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.
2020

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.
2222

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:
2424

2525
- [Debug JavaScript in mobile apps on Android](#debug-javascript-in-mobile-apps-on-android)
26+
- [Debug JavaScript in mobile apps on iOS](#debug-javascript-in-mobile-apps-on-ios)
2627
- [Debug JavaScript in the Windows desktop app](#debug-javascript-in-the-windows-desktop-app)
2728

2829
> [!NOTE]
@@ -32,7 +33,7 @@ Model-driven apps viewed using mobile apps on Android, or the Windows desktop ap
3233
3334
More information:
3435

35-
- [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).
3637

3738
- [Microsoft Edge Sources](/microsoft-edge/devtools-guide-chromium/sources/)
3839
- [Google Chrome Sources](https://developer.chrome.com/docs/devtools/sources/)
@@ -45,7 +46,7 @@ When an event handler causes a script error in a model-driven app, the following
4546

4647
:::image type="content" source="media/script-error-dialog.png" alt-text="Script error dialog":::
4748

48-
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.
4950

5051
```
5152
Xrm.Navigation.openalertDialog is not a function
@@ -68,10 +69,7 @@ In this case, the name of the function was incorrect, `openalertDialog` should b
6869

6970
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.
7071

71-
> [!NOTE]
72-
> It is not currently possible to debug devices using iOS.
73-
74-
To debug JavaScript in mobile apps, you must complete the three steps below:
72+
To debug JavaScript in mobile apps on Android, you must complete the following three steps:
7573

7674
### 1. Configure your device
7775

@@ -88,12 +86,7 @@ To debug JavaScript in mobile apps, you must complete the three steps below:
8886

8987
1. In the mobile app, go to the list of Power Apps and select on the menu button.
9088
1. Make sure that the toggle **Enable remote debugging for model-driven apps** is on.
91-
92-
:::image type="content" source="media/field-service-mobile-app-settings.png" alt-text="Field service mobile app settings":::
93-
94-
1. When enabling this option, there's a confirmation dialog. Select **Confirm**.
95-
96-
:::image type="content" source="media/field-service-mobile-app-settings-confirm-remote-debugging.png" alt-text="Confirm remote debugging dialog":::
89+
1. There's a confirmation dialog when you enable this option. Select **Confirm**.
9790

9891
### 3. Debug from your development machine
9992

@@ -103,10 +96,29 @@ To debug JavaScript in mobile apps, you must complete the three steps below:
10396

10497
:::image type="content" source="media/edge-inspect-devices.png" alt-text="Edge DevTools Devices screen":::
10598

106-
1. Click on **inspect**.
99+
1. Select on **inspect**.
107100

108101
More information: [Microsoft Edge: Remotely debug Android devices](/microsoft-edge/devtools-guide-chromium/remote-debugging/)
109102

103+
## Debug JavaScript in mobile apps on iOS
104+
105+
You can use Safari on a Mac to debug JavaScript web resources on iOS.
106+
107+
To debug JavaScript in mobile apps on iOS, you must complete the following two steps:
108+
109+
### 1. Configure the mobile application
110+
111+
1. In the mobile app, go to the list of Power Apps and select on the menu button.
112+
1. Make sure that the toggle **Enable remote debugging for model-driven apps** is on.
113+
114+
### 2. Debug from your Mac
115+
116+
1. Connect your iPhone or iPad to your Mac.
117+
1. Launch Safari on your Mac.
118+
1. In the **Develop** menu, find your connected iPhone or iPad, and then look for **Power Apps** or **Field Service**.
119+
120+
More information: [Inspecting iOS and iPadOS | Apple Developer Documentation](https://developer.apple.com/documentation/safari-developer-tools/inspecting-ios)
121+
110122
## Debug JavaScript in the Windows desktop app
111123

112124
To debug JavaScript on Windows, you must first install the prerequisite applications.
@@ -125,7 +137,7 @@ To debug JavaScript on Windows, you must first install the prerequisite applicat
125137

126138
1. Open **Windows Settings** > **Privacy & security** > **For developers**.
127139
1. Enable **Device Portal**.
128-
1. Click **Yes** to install Windows Developer Mode package when prompted.
140+
1. Select **Yes** to install Windows Developer Mode package when prompted.
129141
1. Once Device Portal is enabled, **note the URL you will use to connect using localhost**. On most devices, it's `https://localhost:50080`
130142
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)
131143

@@ -150,7 +162,7 @@ Use the **Run command** (shortcut is `Windows + R`) and use the following deep l
150162

151163
:::image type="content" source="media/devtools-configuration-for-windows.png" alt-text="Inspect in the DevTools screen":::
152164

153-
1. Click **inspect** and the DevTools will open.
165+
1. Select **inspect** and the DevTools opens.
154166

155167
### Related articles
156168

powerapps-docs/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ metadata:
1010
ms.topic: hub-page # Required
1111
author: tapanm-msft #Required; your GitHub user alias, with correct capitalization.
1212
ms.author: tapanm #Required; microsoft alias of author; optional team alias.
13-
ms.date: 06/30/2023 #Required; mm/dd/yyyy format.
13+
ms.date: 08/07/2024 #Required; mm/dd/yyyy format.
1414
ms.custom: bap-template
1515
hide_bc: true
1616

@@ -35,7 +35,7 @@ highlightedContent:
3535

3636
# Card
3737
- title: Troubleshoot
38-
itemType: concept
38+
itemType: how-to-guide
3939
url: /troubleshoot/power-platform/power-apps/welcome-power-apps
4040

4141
additionalContent:

0 commit comments

Comments
 (0)