Skip to main content
cenkusyus
Participant
February 29, 2024
Answered

Button links are breaking after ToC updated

  • February 29, 2024
  • 3 replies
  • 383 views

Hello

I searched and couldn't found any solution about this. Seems like an old issue and still not solved.

 

I have Table of Contents and it creates bookmarks in project file when I updated the ToC.

I also have buttons in my master pages (or parent pages). So these buttons link to each other master pages to quickly switch between subjects. When I create the button I pick the target from the bookmark list that ToC created. 

It works well until I update the ToC!

All button links are breaking and in the project file all buttons automatically select the first bookmark from the bookmark list. None of any button is working.

 

The only way, I update ToC first and re-link all buttons and then export to pdf file.

Do you have any idea or solution?

 

Thanks

 

Correct answer James Gifford—NitroPress

TOC links are somewhat ephemeral, I believe. That is, if you generate a TOC, then make various edits or changes, and generate the TOC again, none of the links are guaranteed to be the same as before. So if you assign an existing TOC destination to a button, and then update the TOC, the destination link for the button may no longer exist.

 

The systems really aren't meant to work in step. The solution is to create permanent text anchors for your buttons.

3 replies

Dave Creamer of IDEAS
Community Expert
Community Expert
November 18, 2025

How are you exporting the file (format and settings)?

 

David Creamer: Community Expert (ACI and ACE 1995-2023)
Participant
November 18, 2025

I am exporting to Adobe PDF (Interactive) with these settings (I don't change Advanced or Security):

Participant
November 17, 2025

@cenkusyus 

I ran into this same issue with a VERY important white paper (it was super frustrating). The Table of Contents (TOC) links completely stop working you I update the TOC, which I always do before creating the PDF for distribution.

I found a workaround (manual fix). Here are the instructions:

  1. Highlight the text or button that you would like to link to and go to Window > Hyperlinks.
  2. From the Hyperlinks panel menu (three lines in the upper right corner) choose New Hyperlink Destination…
  3. Add a number or prefix in front of the name (that way you can tell the difference between the TOC Bookmark/Hyperlink and the Hyperlink Destination you are manually creating). I used the page number.
  4. In the Buttons panel, create and name your button.
  5. Hit the + next to Actions.
  6. Choose Go To Destination.
  7. In the middle of the panel you will see the Destination choice popup, click to choose the destination with the number prefix.
  8. Add a Description for rollover and accessibility text (optional).

    Below are screenshots of each step.

 

  • Security contacts is the Hyperlink Destination I created. 
  • 12 is the page number that I used as a prefix. 
  • In the last screen shot you will see Security contacts (without a prefix) which was automatically created by the TOC. The prefix prevents you from choosing that one. 
  • The pop up that shows 12-Security contacts is from Destination in the Buttons and Forms panel.
  • Also, for some main headings I used a prefix of just "A" (as a differentiator).

 

Note: I had to blur most of the company sensitive information in the screenshots.


James Gifford—NitroPress
Legend
February 29, 2024

TOC links are somewhat ephemeral, I believe. That is, if you generate a TOC, then make various edits or changes, and generate the TOC again, none of the links are guaranteed to be the same as before. So if you assign an existing TOC destination to a button, and then update the TOC, the destination link for the button may no longer exist.

 

The systems really aren't meant to work in step. The solution is to create permanent text anchors for your buttons.

cenkusyus
cenkusyusAuthor
Participant
February 29, 2024

Thank you James!

That is the only way that linking to text anchors for the buttons without any ToC update problem.

I already done this as you suggested.