PDF with named destinations hosted on webserver doesn't navigate to some destinations via URL anchor

[muijiu]

I have a PDF that contains named destinations. It is hosted on a web server. When I navigate to the PDF using #nameddest=[named destination name] or #[named destination name] appended to the URL, most of the destinations work, and they are properly navigated to; but, there are some that don't. There does not appear to be any difference between the ones that do and the ones that don't. The naming convention for the destinations is standard, all lowercase, with words divided by a dash "-". I receive the same result in both Edge and Chrome. Double-clicking on the destinations that do not work in the browser in Acrobat Pro DC work as expected.

Any help would be greatly appreciated.

Thanks

[david_9803]

I'm having the same issue. Is there a workaround or a fix for this issue yet?

[Meenakshi Negi]

Hi david_9803,

Thank you for reaching out.

Could you please share more information about this issue? It would be helpful to share the screen recording showing what is happening. Also, please confirm whether the problem occurs with Acrobat. 

Thanks,

Meenakshi

[david_9803]

Hello Meenakshi,

Thank you for looking into this issue. I unfortunately will not be able to share a screen recording due to company privacy.

The issue I have is that my company uses Microsoft SharePoint as their web host. When a PDF file is uploaded to the SharePoint, the hyperlinks do not function as they should.

The PDF file in question (let's name it MainPDF) is meant to open 3 other PDF's (lets name it RefPDF) when clicked on their respective links. My initial approach was to link MainPDF with named destinations while my RefPDF was on SharePoint. Having the hyperlink URL set to nameddest=xy did not function as expected through SharePoint. The hyperlinks kept opening the first page of RefPDF but did not navigate to the named destination.

My secondary approach was to have my MainPDF uploaded in SharePoint and to have my RefPDF originate from Adobe cloud, however the links still did not function as they should on SharePoint (or Acrobat for that matter as the link only took me to the first page of the RefPDF). 

Finally, RefPDF was added as an attachement under MainPDF to be able to utilize linking, and everything functioned as it should within the Adobe Application. However, iploading this document to SharePoint does not retain the same functionaility when it's used through a web-browser. The end client needs to download the PDF file to be able to utlize the links.

Is there a way I can upload MainPDF to SharePoint and have the everything function as they should through the web-browser, or am I limited to being able to use MainPDF excluisively through the Adobe application?

Also just to confirm, there is no issue with Abrobat.

Thank you,

David