Named destinations do not work in Acrobat

[HC de Jong]

I have two PDF files (testfile.pdf and styles.pdf, stored in the same folder on my local drive), with links from one file to the other.

- PDF link using file name only: this works: Acrobat opens the PDF

- link using page number: Acrobat says "could not open styles.pdf#page=3"

- link using destination: Acrobat says "could not open styles.pdf#ID_403"

When I open the URL in a browser, these links do work:

file:///C:/testfolder/styles.pdf#page=3

 opens the PDF at the correct page,

file:///C:/testfolder/styles.pdf#ID_304

 opens the PDF at the correct named destination.

This confirms the destinations exist and are accessible via these URLs.

So what could cause these links to not work in Acrobat?

This is with the current version of Acrobat from Creative Cloud.

[try67]

You can link a Named Destination (even in another file) directly, without using a URL (which is not a good idea anyway, since it won't work if the files are moved to another folder, for example). To do so create a Link and set its action to "Go to a page view". A floating window will open with a "Set Action" button. Switch to the other file, open the Destinations panel and double-click the Destination you want the link to point it, and it will do so. The floating window will disappear and if you examine the properties of the link you should see it says "Go to a page in another document", with the path of the file and the destination name you clicked on below it.

Note that although the path seems absolute, it is in fact relative, so if you move both files to another folder (or another computer), the link will still work.

[HC de Jong · Accepted solution]

It turns out I had to make a change in the application that creates the PDF (Antennahouse Formatter). This change is not visible when I examine the links in Acrobat, but it has the desired result: links to a page number or named destination now work correctly.

[Sudheendra38267568byus]

I have a similler situation with book1.pdf and book2.pdf. 

named destination with book2.pdf#id_1234 added in book1.pdf works perfectly fine when these PDFs accessed via http protocal in browser.

but, in acrobat application, it is taking to first page of the book2.pdf.

intermediate xsl-fo temp file shows the named destination link correctly as below.

<fo:basic-link show-destination="new" indicate-destination="true" external-destination="book2.pdf#id_1234" fox:alt-text=" "><fo:inline font-style="italic"/></fo:basic-link></fo:inline></fo:block>

need your suggestion how Acrobat Application handles the named destination.

thanks,

sudhe

[HC de Jong]

I had to set the axf:action-type attribute:

axf:action-type="gotor'

https://www.antenna.co.jp/AHF/help/en/ahf-ext.html#axf.action-type