Fix the selector of a UI element
This content is archived and is not being updated. For the latest documentation, go to What's new in Power Automate?. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
|Enabled for||Public preview||Early access||General availability|
|Admins, makers, marketers, or analysts, automatically||-||-||May 15, 2023|
You can now create desktop flows that perform UI and browser automation and don't fail due to a lack of ability to locate the UI elements in every execution.
UI and browser automation in desktop flows interact with UI elements. When you capture a UI element, a selector gets generated and specifies the UI element. A selector is the address of the UI element, and Power Automate for desktop can locate the UI element while running the desktop flow.
In many cases, the selector of a UI element is dynamic, meaning that it can be slightly different every time the window or webpage is loaded. This scenario may cause a UI/browser automation action to fail during running time, as the selector is no longer the same as at the time of capturing.
You can capture a UI element multiple times using a wizard, and Power Automate for desktop will compare all captured selector information and suggest a new one that is more dynamic and robust and can be used for addressing the specific UI element.