Unanswered

RPA suddently stop recognizing UI elements

(1) Share

Report

Posted on by ossanchezm

Hello!

I've created a flow in Power Automate Desktop to automatically download an xlsx report daily from a table in Power BI. The flow involves opening a published Power BI dashboard, which contains a table and some slicers.

This setup worked flawlessly for about 2 weeks. However, recently, it stopped recognizing the UI elements, specifically the arrows in the slicers used to apply filters.

I've used the "Add UI Element" feature in Power Automate Desktop to identify these UI elements and haven't modified any properties. I'm wondering if the ID of the UI elements in Power BI changes periodically or if there's another underlying issue.

Has anyone encountered this or knows what might be the cause?

Thank you for your assistance!

Categories:

Power Automate Desktop

All responses (3)

Answers (0)

Sort by

trice602 16,679 Super User 2026 Season 2 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @ossanchezm ,

Yes, most likely the ID and details of the UI elements changed, and this has happened to me too. Now, when I have a desktop flow that runs for months without any issue and then all of a suddenly stops, more often than not, it's something like the ID or similar. So yes, I would definitely dig in and investigate that in detail. Let me know.
Nived_Nambiar 18,138 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @ossanchezm

As @trice602 said, may be you need to change the attribute values of UI Elements to make it work again. If this issues occurs frequently, then try to see the possibility of using cloud flow actions which helps to download the report 🙂

That would be stable 🙂

Thanks & Regards,
Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌
Agnius Bartninkas Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

This can easily be caused by an update to Power BI, as it does receive updates quite frequently, similarly to the rest of MS apps. I suggest that you try to modify your selectors so that they do not rely on IDs or similar values that may change over time.

The best way to figure out what changed is to capture the elements again and see what the selector looks like, and compare it against what you had previously. Then remove whatever has changed and select something else as identifiers. See here for more reference on how to modify selectors: https://learn.microsoft.com/en-us/power-automate/desktop-flows/build-custom-selectors#use-variables-in-a-custom-selector

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.