Unanswered

Last week PAD update(5/18) and IF window

(3) Share

Report

Posted on by Laktech

I have several flows that had been running perfectly until the most recent update in which the UI automation action "if window" broke. In this new update it is passing true values where the value should be false and now I have to change all the if windows to if window contains but that seems like a hell storm to replace them all. Is anyone else having this issue?

Is it possible to run a previous version of PAD? I can only assume that this is a bug and will be fixed in a month or so and want to just use the previous version until it is resolved. Thanks in advance.

Categories:

Power Automate Desktop

All responses (4)

Answers (0)

Sort by

VJR 7,635 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Laktech

You can use the previous version of PAD only if you have the executable of it and are able to install it.

Until then if it is causing too much trouble then you can copy the "If window" PAD actions into a Text file and replace it with the corresponding "If window contains" within the text file itself and then paste the replaced text back into the Flow editor. Do take a backup of the original flow or do it in a dummy flow.

For ex:

If you copy (Ctrl C) the "If window" action into notepad it shows as below

IF (UIAutomation.IfWindow.IsOpen Window: `some element here`) THEN

and "If window contains" as below
IF (UIAutomation.IfWindowContains.WindowContainsElement Element: `some element here`) THEN

Would be like a Find & Replace in one go versus having to do it manually within PAD at all places.
Kresimir_RPA 286 on at

Like
a
(0)

Report
Copy link

Link copied!

That's why I'm still running 2.16 PAD version. It is stable and it is to big risk to update to a new version and risk all my flows to stop working.
Isabella Ramare 8 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm having the samme issue. All my "Wait for window" actions stopped working as well 😞
Mibsk 49 on at

Like
a
(1)

Report
Copy link

Link copied!

Im pretty sure that the developers have corrected a bug, where we could choose Window controls where we only should be able to choose window content controls.

I think its a correction of a bug, because ive been working with ProcessRobot for years before it became PowerAutomate Desktop.
And in ProcessRobot we where not able to use the a Window control like you mention.
(i could be wrong though)