You are viewing limited content. For full access, please sign in.

Question

Question

Validating a pdf that was uploaded in a form or in repository

asked on October 22, 2020

We receive bids electronically and the are tagged as SEALED which no one can open until the bid opening.  I have had several bids that were uploaded and the pdf was corrupted.  Technically they cannot resubmit because the solicitation is closed.  Any ideas on validated the pdf upon receipt or storage in the repository?

0 0

Replies

replied on October 22, 2020

Hi Jim, 

Where are these PDF files coming in from? E.g. Form file upload.

Knowing how they're getting to the repo may help guide what PDF validation options are feasible.

0 0
replied on October 26, 2020

Form File Upload

0 0
replied on October 23, 2020

What kind of corruption did you experience? Some kinds would be easier to detect with an automated process than others.

0 0
replied on October 26, 2020

I dont know what kind.  When trying to open a error is supplied saying file cant be opened - corrupted.

0 0
replied on October 26, 2020

The reason I ask is that preventing the corruption may end up being easier than detecting it. Maybe you want to pursue both approaches, I'd suggest working with your SP to open a support case.

In terms of detecting, there isn't anything built-in that I'm aware of. You could potentially do something with Workflow, but it would probably involve writing code to try to open the file with a PDF library and see if it succeeds. If it's as seriously broken as that error message makes it sound, that might be all you  need to do, if it's more subtly corrupted it could be more work to detect.

1 0
replied on November 4, 2020

Maybe passing it to Workflow and seeing if you can download the electronic document on the corrupted one?

If that fails then you could use try-catch logic to catch corrupted ones and get notified or some alternative.

Not sure if this is a solution, but sounds worth a try?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.