Indicate Element Issue When Controlling Screen Using Teams

I’m encountering an issue when trying to ‘Indicate Element’ when share screen via Microsoft Teams. UiPath is picking up the Teams cursor or UI elements instead of the actual application elements I want to automate.This prevents me from creating valid selectors.

Has anyone encountered this before, or does anyone have a solution? Could there be a Teams configuration, an UiPath setting, or other workaround?
I’m using Studio version 2024.10.8

I’ve attached a screenshot to illustrate the problem.


Thanks a lot for any help!

Best regards,
Hendaryie

@Hendaryie_Tjoeng

Try to move that away then ideally it would indicate properly

cheers

Thank you for the reply, but I already try it, and doesn’t work, the indicate box always indicate the cursor, can’t move to the button or field I want to indicate

@Hendaryie_Tjoeng

in use app browser did you happen to indicate the window you need?

Alternately try with ui explorer to check..may be teams is active always

cheers

before i can indicate anything in use app browser, the indicate box is already in the teams cursor, for the ui explorer thing, can you give me an example for that?

@Hendaryie_Tjoeng

from studio open ui explorer and try to indicate there

also why is a special requirement to indicate elements via teams sharing?

cheers

the same sir, it happen everytime i try to indicate something, from anywhere.
Usually I use skype share screen to do some fixing for client bot, but since microsoft kill skype, I try to use Teams, but I facing this issue.

@Hendaryie_Tjoeng

got you

try teams or so..looks like the cursor element used by teams is covering the area where we are indicating resulting in issue

we need to try ways..unfortunately I dont have teams currently to check

but one workaround little difficult but would work..when you indicate in ui explorer after indicating in the left top window you would see all the visual elements can select from there too…I know its a long way but thats a work around till we find a resolution

@loginerror - Any help here

cheers

thank you for the time, but I still facing this issue and will try to do some workaround, I will inform you if I found the fix for this

1 Like