Unable to scrape pdf elements

selector
pdf
studio

#1

Scenario:

Unable to scrap pdf elements

Steps to reproduce:

Current Behavior:

unable to identify elements in the PDF file

Expected Behavior:

its worked few days ago and I completed the bot based on that data. now its throwing error. I tried through UI explorer. few days ago its worked, now not working

Studio/Robot/Orchestrator Version:

Studio version: 2016.2.6274

Last stable behavior:
Last stable version:
OS Version: windows 7

Others if Relevant: (workflow, logs, .net version, service pack, etc):


#2

I opened the file through Foxit reader. still its not recognized


#3

do you have accessibility options in Acrobat Reader enabled?

image


#4

thanks @Gabriel_Tatu, i’ll check


#5

its enabled @Gabriel_Tatu


#6

what changed then, if you say it worked a few days ago?


#7

image

after this popup only I can find elements. but this popup will shown during the development only. when I try to find element during the development, PDF will render and returning the elements. in production getting error stated that, element not found. :disappointed_relieved:


#8

Hi Team,

I am facing the same issue. When robot trying to scrape the table data from PDF using selector then same pop-up occures.
Please provide the resolution @badita, @Vikas.Jain.

Thanks!!


#9

Can you share the pdf?


#10

I have been having the same issue since v2016 not able to read PDF’s… I was able to get it working by changing some settings in adobe reader like checking and unchecking “Use document structure for tab order when no explicit tab order is specified” and “Enable assistive technology support”. I was hoping that 2018 would solve this issue. Now if and when it’s working I get the same pop up but I am only getting it during development. When I actually go and execute the script it fails because it can not read the PDF. This issue is really impacting some projects.


#11

@ovi : we had something written for pdf, can you share it here?


#12

Is there a better workaround then this??


#14

Thats it !


#15

This is the best workaround I have found for now. It would be great if there was a proper fix for this problem.


#16

We are working on something new, but we can detect elements inside as much as adobe lets us. The problem is with their assistive technology, we did our best so far using what they give us.


#17

This has worked for me thanks!