Skip to content

Commit fccd19f

Browse files
committed
manual edits
1 parent 09884bc commit fccd19f

1 file changed

Lines changed: 21 additions & 26 deletions

File tree

support/power-platform/power-automate/desktop-flows/ui-automation/elementpicker-cannot-see-elements.md

Lines changed: 21 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,49 @@
11
---
2-
title: UI element picker or Recorder cannot view UI elements in desktop applications
3-
description: Learn how to resolve issues when Power Automate for desktop cannot view or interact with specific UI elements in desktop applications.
2+
title: Troubleshoot UI Element Visibility Issues in Power Automate for Desktop
3+
description: Troubleshoot Power Automate for desktop when it can't interact with specific UI elements. Explore solutions like OCR, image actions, and more.
44
ms.date: 11/05/2025
5-
ms.custom: sap:Desktop flows\UI automation
6-
ms.reviewer: nimoutzo
7-
ms.author: iomimtso
5+
ms.custom: sap:Desktop flows\UI or browser automation
6+
ms.reviewer: iomimtso, nimoutzo, v-shaywood
87
---
98

10-
This article provides solutions for situations where Power Automate for desktop cannot view or interact with specific UI elements in a desktop application.
9+
# UI element picker or Recorder cannot view UI elements in desktop applications
10+
11+
This article provides troubleshooting guidance for an issue that can occur where Power Automate for desktop cannot view or interact with specific UI elements in a desktop application.
1112

1213
## Symptoms
1314

1415
When using Power Automate for desktop, the element picker tool cannot detect or "see" certain UI elements within desktop applications. This issue prevents you from selecting elements for automation tasks.
1516

1617
## Cause
1718

18-
Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with standard accessibility APIs that Power Automate for desktop relies on. This can make certain elements invisible to the element picker.
19-
20-
## Resolution
19+
Some desktop applications use custom UI frameworks or rendering methods that aren't compatible with the standard accessibility APIs that Power Automate for desktop relies on. This can make certain elements invisible to the element picker.
2120

22-
Use one of the following workarounds to interact with UI elements that cannot be detected by the element picker.
21+
> [!IMPORTANT]
22+
> For coordinate-based solutions (Solutions [3](#solution-3-use-the-recorder-with-coordinates) and [4](#solution-4-use-move-mouse-and-send-mouse-click-actions)) to work reliably:
23+
>
24+
> - The screen configuration (resolution, DPI settings, scaling) must remain static at runtime and match the configuration used during development.
25+
> - Changes to the application's user interface structure may affect the effectiveness of these workarounds.
26+
> - Test your flows thoroughly when deploying to different machines or environments.
2327
24-
### Solution 1: Use Move mouse to image action
28+
## Solution 1: Use Move mouse to image action
2529

2630
1. Add a **Move mouse to image** action to your flow.
2731
2. Capture an image of the UI element you want to interact with.
2832
3. Enable the **Send a click after moving mouse** option.
2933
4. Configure any additional settings as needed.
3034

31-
The action moves the mouse to the first occurrence of the specified image and sends a left click.
35+
This action moves the mouse to the first occurrence of the specified image and sends a left click.
3236

33-
### Solution 2: Use Move mouse to text on screen (OCR) action
37+
## Solution 2: Use Move mouse to text on screen (OCR) action
3438

3539
1. Add a **Move mouse to text on screen (OCR)** action to your flow.
3640
2. Specify the text that appears on or near the UI element you want to interact with.
3741
3. Enable the **Send a click after moving mouse** option.
3842
4. Configure OCR settings and click options as needed.
3943

40-
The action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
44+
This action uses Optical Character Recognition (OCR) to locate text on the screen or foreground window and sends a mouse click to that location.
4145

42-
### Solution 3: Use the recorder with coordinates
46+
## Solution 3: Use the recorder with coordinates
4347

4448
1. Open Power Automate for desktop and create a new flow.
4549
2. Select **Recorder** from the toolbar.
@@ -48,23 +52,14 @@ The action uses Optical Character Recognition (OCR) to locate text on the screen
4852

4953
The recorder creates a **Click UI element in window** action with coordinate-based input parameters populated with the respective values from your click action.
5054

51-
### Solution 4: Use Move mouse and Send mouse click actions
55+
## Solution 4: Use Move mouse and Send mouse click actions
5256

5357
1. Add a **Move mouse** action to your flow.
5458
2. Configure the action to move the mouse to the specific coordinates of the target element.
5559
3. Add a **Send mouse click** action immediately after the Move mouse action.
5660
4. Configure the Send mouse click action to perform the desired click (left, right, or double-click).
5761

58-
## Important considerations
59-
60-
> [!IMPORTANT]
61-
> For coordinate-based solutions (Solutions 3 and 4) to work reliably:
62-
>
63-
> - The screen configuration (resolution, DPI settings, scaling) must remain static at runtime and match the configuration used during development.
64-
> - Changes to the application's user interface structure may affect the effectiveness of these workarounds.
65-
> - Test your flows thoroughly when deploying to different machines or environments.
66-
67-
## See also
62+
## Related content
6863

6964
- [UI automation in Power Automate for desktop](/power-automate/desktop-flows/ui-elements)
7065
- [Use the recorder in Power Automate for desktop](/power-automate/desktop-flows/recording-flow)

0 commit comments

Comments
 (0)