Automation Browser Upgrade, UI Buttons stopped working

(0) Share

Report

Posted on by DamoBird365

8,942 Microsoft Employee

Hi everyone,

I upgraded to the latest version of PAD v 2.12.171.21216 and the UI Buttons on my PAD Flow stopped being recognized. The first thing that I spotted is that the Automation Browser title has changed

But this is also reflected in the UI Element explorer with the old vs new capture:

I have re-captured and the problem has been resolved but I dread the next update. Anyone experience of the latest version and unexpected results with buttons? I just hope this isn't reverted back in the next version!

Also, I have enabled ScreenDefaultResolutionEnabled=true for unattended mode so that the resolution matches that of the capture/attended. When I performed the upgrade, the software overwrote the true setting. This is unexpected behavior for a software upgrade. Something to watch out for if you are configuring your environment.

Set screen resolution on unattended mode - Power Automate | Microsoft Docs

Damien

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (0)

Sort by

NikosMoutzou Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @DamoBird365 !
May I ask which version of Power Automate Desktop was previously installed in order to check the case from our side?
Moreover, I would like to note that I have observed from your screenshot of the UI elements that the captured elements are Window (Desktop) related and not Web related. The difference is that the parent element is 'Window' while for Web elements the parent is 'Web Page'. Example:
This is exactly the same element in the Automation browser. The first one is a Desktop element, captured either through an action of UI Automation module or with the Desktop recorder. The second one is a Web element, captured either through UI element repository or with the Web recorder.
Regarding your second remark, I will forward your feedback to the respective team.

Was this reply helpful? Yes No
DamoBird365 8,942 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @NikosMoutzou

Thanks for taking the time to reply and pass on my feedback. It is Window Elements that I had problems with, existing Web Elements appeared to work fine post upgrade. My screenshot shows the non working (top) and the new working (bottom) capture of the same button. Normally during a recapture at a later date the Window is called 2,3,4 etc but the post-fix of the window is different, almost like the internal name (PAD.Automation.Robot -> PAD.Robot) of the automation browser has changed between versions.

The version I had previously was a variant of 2.11 but I cannot be exact as I cannot see an installation log in the C:\Program Files (x86)\Power Automate Desktop folder to confirm exactly.

Thanks again, Damien

Was this reply helpful? Yes No
DamoBird365 8,942 Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @NikosMoutzou

The client has upgraded PAD and again the value of Microsoft.Flow.RPA.UIFlowService.ScreenDefaultResolutionEnabled has reset back to false, causing the Desktop flow to fail. The only way to diagnose this is to capture a screenshot at the point of failure when in unattended mode and only then is it obvious the resolution is lower and the on screen application buttons are out of visibility. Is there any way to cater for this event? Is there a plan for the product team to stop overwriting the settings when an upgrade is done? This is not logical behavior.

Set screen resolution on unattended mode - Power Automate | Microsoft Docs

Damien

Was this reply helpful? Yes No