Unable to capture web Element

[Anonymous]

Hi Team,

I am trying to capture a web UI element but when i capture it, it is considered as Windows UI element. Please help me to overcome this issue

[MichaelAnnis]

What scenario are you concerned about that it matters?  You have it captured, so when you have to use it, you should be able to use the Window version of the command.  Example:

I want to click this button...instead of using "Press button on web page" you will use "press button in window"

[Anonymous]

@MichaelAnnis thanks for your reply.

That is a text field on the web page. When i captured the element, it starts with :desktop > Element

but it is web element for sure.

[MichaelAnnis]

Right, but are you trying to enter text into the text field.  If you use "Populate text field in window" or 1) "Focus text field in window" and then 2) "Send keys", I bet it will work.  I don't know why they sometimes flip flop between the two, but typically if it captures it as a window element versus a web element, then it will put it back where it captured it from if you use the right command that can find the element.

If you have tried that, and it's not working, then it's possible that the web window is not html and is running some underlying program.  Ex.  

In the image above, everything above the red line is html, but everything below it is a combination of java and .net.  I cannot capture the elements using web capture on the text fields.  If this is the case, as stupid as it sounds, I recommend finding alternatives to get to your text field.

One common solution is to Send Keys {Tab} as many tabs as needed to get to the text field.  A last resort would be image recognition using "Move mouse to image".  The warning about anything image related is it will fail if you ever use a computer with different resolution, different monitors, or typically if you are trying to remote in.

Best of Luck!

[Anonymous]

@MichaelAnnis Thanks.

I have been using WinAutomation tool for nearly 2 years. I also know that WinAutomation tool was acquired by the Microsoft and Power Automate Desktop is almost replica of WinAutomation. I am able to capture the element using  "Populate text field on web page action" in WinAutomation but in Power Automate Desktop it is able to capture it as Window element (exact same web page). I think there is some issue with this tool which needs to fixed.

Send Keys will not be reliable in my case, so i can not use it

[Pavel_NaNoi]

Think this issue arises when the UI Element Anchor selector gets botched (the page that contains the UI Element), check it, see if you can reselect it.

[Anonymous]

i can select it but every time it considers it as window element only

[Anonymous]

correct, i am also frustrated, right now i am working on four applications and PAD capture element as window elements. I am struggling to get right attributes using window actions. somehow manage to automate using window actions.

[Pavel_NaNoi]

Sometimes its just a compatibility issue unfortunately.