I am trying to use the activity “Element Exists” on a JavaScript Modal, and it’s not working. I’m using IE because it’s not even supported in Firefox or Chrome yet, though they seem to be working on it (even though modals are older than UIPath).
As far as the selector, I have tried all 3 different blocks that the selection tool recognizes (whole window, main pane, text in the middle), and they always fail.
I see a lot of people complaining about this, but I don’t see many solutions. Why doesn’t this work? Is it not going to work at all? I don’t understand why this is not working properly.
The validate and highlight buttons give me feedback such that the bot should work.
You need to make the selector work for all possible scenarios. In your case, Copy the selector to the notepad and run again, when it fails use indicate element and copy the selector again to the notepad. Now, Compare both definitively there may be a difference. Make it generic then the bot will work fine.
But sadly, I had already been keeping on eye on the selector to see if it would change, so in this case, the selector works fine, and is identical when I run it again.
@Robot.Builder.9001 Whenever you fail to get results with element exists,try using get attribute activity…It gives more robust answers as it has many attributes to arrive at decisions…
After a few other things today, I tried that, and it’s not working. I also tried looking for the exclamation mark icon (as an image and as an element), and using text exists.
I don’t understand why it’s so hard to work with javascript modals. This is impossible-level for a training course. This is the kind of thing that the UIPath developers would be doing / would have done as they are building UIpath studio and the first generation activities.
I don’t think I’m off in the weeds, but this sure seems like it.