Keyboard input doesn't work with Web Browser

(0) Share

Report

Posted on by daydinho10

124

Hi,

I am running power automate with SAP. what I wanted to do is to put the TCOD in the TCOD input box and then hit Enter. It has been working fine in the past. However, it stop working recently. I test it with Power Automate Desktop and it works. My requriement is to shedule it to run from MS flow. That is when the keyboard input doesn't work. I try the work around with double click but not successfull.

Could somebody help?

Thanks

Categories:

Power Automate Desktop

I have the same question (0)

All responses (4)

Answers (0)

Sort by

VJR 7,635 on at

Like (0)

Report
Copy link

Link copied!

Hi @daydinho10

You mentioned - I test it with Power Automate Desktop and it works.
Does it run from inside the Flow editor?
Or does it also work when you click the play button from the screen which shows all the list of flows (marked below)?

If you are using Sendkeys make sure to use Wait actions and Focus appropriate Window wherever applicable.

Was this reply helpful? Yes No
daydinho10 124 on at

Like (0)

Report
Copy link

Link copied!

@VJR both of them is working with no problem. my flow also has wait action for sendkeys

Was this reply helpful? Yes No
daydinho10 124 on at

Like (0)

Report
Copy link

Link copied!

The error message is
"Problem while executing action 'Focus'. Element with selector 'iframe[Id="ITSFRAME1"] input[Id="M0:U:::1:34"]' not found."

Was this reply helpful? Yes No
PAD_Explorer 8 on at

Like (0)

Report
Copy link

Link copied!

Hello all,
I have exactly the same problem! I am trying to send an "Enter" and an "F2" to the browser (SAP Web GUI). In Power Automate Desktop development mode it works perfectly. Now when I started the desktop flow normally (without development mode), it doesn't work anymore. No matter if as hardware key or without.

But I don't get a Focus error or similar (like daydinho10 ) but the subsequent wait for web element hits is missing because the commands in the browser don't seem to have arrived/been executed. The error is then the logical consequence.

Any idea?

Was this reply helpful? Yes No