Answered

UI elements not found

(0) Share

Report

Posted on by Saiko

Hi everyone,

So I've build a desktop RPA flow in a test version of a native application. When this worked fine I taught it was the moment to test my flow in the real environment. But when I tried this the RPA stopped identifying my user interface elements. At first it was because my window config was still on the old version, but apparently i should reconfigure all of the UI-elements in the other version of the application. That seems like a lot of work to me. So my question is if there is an easier way to do this

Kind regards.

Categories:

Power Automate Desktop

All responses (9)

Answers (1)

Sort by

OkanMTL 703 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

You could check your UI-Element Selector values and see what is different between the Test and Production application.

I'm guessing most of the Root will be the same but the header will be different. So you can try unchecking some of you UI-elements selectors and trying again. Or you can change the value of the selectors from test to production.

So try:

1. Put one UI-element (one from production and one from test) and the values of the selectors side by side

2. Check the differences

3. Edit your selectors so that it matches or works with the selector from the Test space.

And also, why did you need to build the flow in the test version?

Interested in other solutions. So i'll be reading.

Good luck.
Saiko 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

So, the reason we did this is because we wanted to make sure we could make RPA work inside the organisation.
To do this we used a version of the application that was linked to our sandbox database to make sure that no mistakes were made.

This is the code of the test version: > pane > window[Id="ContentForm"] > pane[Id="ucPersoonPrestatieOverzicht"] > pane[Id="m_Panel_Content"] > pane[Id="m_ucPersoonSelector"] > pane[Id="TableLayoutPanel_Content"] > edit[Id="m_LookUpEdit_Persoon"] > edit:eq(1)

the code of the live environment: > tab[Name="Prestatie overzicht per persoon"] > window[Id="ContentForm"] > pane[Id="ucPersoonPrestatieOverzicht"] > pane[Id="m_Panel_Content"] > pane[Id="m_ucPersoonSelector"] > pane[Id="TableLayoutPanel_Content"] > combobox[Id="m_LookUpEdit_Persoon"] > edit

there are two big differences if you ask me:
- the new capture sees the tab as a individual thing
- the new capture ads the combobox thing

I don't now what it makes it so different.
Saiko 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Update: when i do this with another element only the tab (> tab[Name="Prestatie overzicht per persoon"]) seems to be different. Which is weird because both of the programs have that same tab.
OkanMTL 703 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

They're actually quite similar.

- Your first point about the individual thing: I guess you mean it only captures the whole page and not individual elements? I'm guessing that is because your test |Selector is longer than the Live environment, which doesn't contain of a window. And if it can't find a window it can't find the selector. I'm not sure if this is what you mean btw.

- About the combobox, this doesn't change much in the end, you could have a element with combobox or edit and it will work the same, but prefereable you should look if Edit also exists in your live environment.

Adding on to your second comment about the tab that is different, this one i can see back in your live environment? How is it different? This tab is presumable the table in which you are getting pane[Id="ucPersoonPrestatieOverzicht"] from and you haven't caught it in your test environment.

Good luck, and if you wan't we can have a quick call shoulnd't be too long for me to explain (im also from the netherlands)
Saiko 21 on at

Like
a
(1)

Report
Copy link

Link copied!

maybe it's better if we have a quick call, i think it would be easier to express myself in dutch
Verified answer

Saiko 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Problem solved: It was due to an update that made the names of the elements change.
OkanMTL 703 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Classic
Saiko 21 on at

Like
a
(0)

Report
Copy link

Link copied!

Yeah, but it has some problems in the long term. It is due to updates from DevExpress that the names of some elements have changed. So now is the question how we can make sure that when an update happens the RPA still recognizes the elements.
Shiv2347 5 on at

Like
a
(0)

Report
Copy link

Link copied!

Is it resolved for you?