hi every body.
I have the same problem.
But I have one more doubt, because in my case when it reaches the last page, instead of finishing the process, it goes back 2 pages, and extracts the same elements again. Shouldn’t it stop data extraction when the “next page” icon disappears?
That particular issue is not happening at my end. Please check the below xaml:
Sequence14.xaml (15.9 KB)
Hope it helps!!
Sounds like the selector for the Next button is wrong, and it’s finding another button and thinking it’s the Next button.
That is, the behavior works correctly. Check all the pages by pressing the “next” button, on the last page, as there are no more pages the button disappears, ergo, you will not find it. I understand that the “Table extraction” activity works that way, when the button disappears on the last screen then it should terminate the activity, however, here it tries to continue going back 2 pages (I don’t understand why 2 and not more or less ) and repeats the operation until it reaches the last one and the same thing happens again, and enters an infinite loop
can you show a screenshot of the next button selector from ui explorer?
may be there is a similar button on it…try to differentiate it using the selector
cheers
Unless you’re using fuzzy selectors and when the Next button disappears there’s another button where the selector is close enough that it thinks it’s the Next button.
I just noticed that what’s actually happening is CV is finding it. Turn off CV. You shouldn’t use CV for a web page or app that has regular selectors. CV is for image-based automation where you can’t get selectors.
Well, I followed @postwick 's advice, removed CV, and improved (I think) the strict selector, add the “>” symbol, which is what appears on the “next” button, to differentiate it from the other buttons.
On the last page it told me that I couldn’t find the button and it came out correctly. I’m a little afraid that it will break since I don’t find that selector very reliable, but time will tell.
Thank you very much for your answers
the selector:
selector not found on de last page:
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.