For Each UI Element needs to show its stored data

Feedback Activities
, ,
1

I have a For Each UI Element that works when I initially configure it and then doesn’t work again, so I need to be able to see the selector/filter for the UI elements it’s looking for. All the activity appears to show is the selector of the container object. How can I see the rest of the details for this activity so I can actually make it work?

When I use Find Children, I can easily see the selectors and filter and modify them manually to make it work. When I use For Each UI Element, if it doesn’t work automatically it appears there’s no way to make manual adjustments.

1 Like
3

Can you post a print of the activity? Or give more details?

4

Not sure what you’re asking for. You can try the For Each UI Element activity yourself and see that it doesn’t show the selector and filters the way Find Children does.

6

How is this still no solved? I’m just wondering if I need to go back to Find Children and not use shiny new modern activity :smiling_face_with_tear:
Edit: @postwick
This is still possible, but it’s inconvenient. You can open xaml file in a code editor.
Search for line for For Each UI Element activity. In there you’ll find ExtractDataSettings and ExtractMetadata properties.

The image shows a snippet of a code editor with XML-like markup, specifically configuring settings for UI elements extraction in a structured format. (Captioned by AI)
The image shows a snippet of a code editor with XML-like markup, specifically configuring settings for UI elements extraction in a structured format. (Captioned by AI)1735×143 28.2 KB

These have most likely the same syntax as those in Extract Table Data activity:
This is a screenshot of the Properties pane for the "Extract Table Data" activity in UiPath, displaying settings and input fields for configuring data extraction. (Captioned by AI)
This is a screenshot of the Properties pane for the "Extract Table Data" activity in UiPath, displaying settings and input fields for configuring data extraction. (Captioned by AI)547×313 8.04 KB

Though they are encoded, I use this website to encode/decode them: HTML entity encoder/decoder
After decoding and formatting they look like this:
The image shows a code snippet in XML format specifying data extraction settings and metadata with a structured table, including elements like columns and web control tags. (Captioned by AI)
The image shows a code snippet in XML format specifying data extraction settings and metadata with a structured table, including elements like columns and web control tags. (Captioned by AI)988×485 25.2 KB

To summarize - it’s possible to edit properties but it’s much harder than for example Extract Table Data, and it’s easier to break something. I think I’ll just stick to Find Children for now even if it’s much older activity.

7

Ouch.

I’d like to add it would be nice to be able to get the elements out as a collection instead of needing to loop over them as you don’t always want to loop.

To me this activity should have been a direct replacement for Find Children and we can use the generic loop activity with the list of UiElements if we wanted to loop.

1 Like
8

If we already confessing our dreams I’d like to have documentation on UiElement… You can also do a lot with this one. But you have to figure out things yourself.