After converting MS word file in to PDF internal hyperlinks are not working (Including TOC too!)

%3CLINGO-SUB%20id%3D%22lingo-sub-2861183%22%20slang%3D%22en-US%22%3EAfter%20converting%20MS%20word%20file%20in%20to%20PDF%20internal%20hyperlinks%20are%20not%20working%20(Including%20TOC%20too!)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2861183%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20week%20i%20started%20facing%20problem.%3C%2FP%3E%3CP%3EAfter%20converting%20MS%20word%20file%20in%20to%20PDF%20internal%20%3CSTRONG%3Ehyperlinks%20are%20not%20working%3C%2FSTRONG%3E%20(Including%20TOC%20too!)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20you%20please%20provide%20soultion%20on%20this.%3C%2FP%3E%3CP%3EAll%20of%20our%20technical%20writers%20facing%20the%20same%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2861183%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2865242%22%20slang%3D%22en-US%22%3ERe%3A%20After%20converting%20MS%20word%20file%20in%20to%20PDF%20internal%20hyperlinks%20are%20not%20working%20(Including%20TOC%20too!)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2865242%22%20slang%3D%22en-US%22%3EI%20believe%20this%20issue%20was%20introduced%20on%20the%20Sept%2028%20Build%2014430.20234%20in%20Current%20Channel%20-%20one%20of%20the%20%22fixes%22%20in%20there%20is%20to%20PDF%20and%20XPS%20export.%3CBR%20%2F%3E%3CBR%20%2F%3ESwitching%20to%20the%20Semi%20Annual%20Enterprise%20Channel%20and%20using%20build%2013801.21004%20does%20not%20exhibit%20this%20problem.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2870207%22%20slang%3D%22en-US%22%3ERe%3A%20After%20converting%20MS%20word%20file%20in%20to%20PDF%20internal%20hyperlinks%20are%20not%20working%20(Including%20TOC%20too!)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2870207%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1190880%22%20target%3D%22_blank%22%3E%40vittala%3C%2FA%3E%26nbsp%3BIt's%20not%20possible%20to%20downgrade%20to%20a%20different%20version%20or%20switch%20to%20whatever%20the%20Semi%20Annual%20thing%20is%20-%20I%20work%20in%20a%20large%20enterprise%20and%20the%20IT%20department%20control%20all%20enterprise%20software%20updates%20and%20upgrades%20-%20it's%20just%20not%20possible%20to%20do%20what%20you%20suggest.%20Meantime%2C%20I%20can't%20distribute%20any%20technical%20product%20documentation%20because%20none%20of%20the%20links%20in%20the%20documents%20work.%3C%2FP%3E%3CP%3EWhat%20are%20you%20doing%20to%20fix%20this%2C%20Microsoft%3F%20It%20is%20absolutely%20catastrophic%20for%20Technical%20documentation%20departments.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

This week i started facing problem.

After converting MS word file in to PDF internal hyperlinks are not working (Including TOC too!)

 

Could you please provide soultion on this.

All of our technical writers facing the same issue.

4 Replies
I believe this issue was introduced on the Sept 28 Build 14430.20234 in Current Channel - one of the "fixes" in there is to PDF and XPS export.

Switching to the Semi Annual Enterprise Channel and using build 13801.21004 does not exhibit this problem.

@vittala It's not possible to downgrade to a different version or switch to whatever the Semi Annual thing is - I work in a large enterprise and the IT department control all enterprise software updates and upgrades - it's just not possible to do what you suggest. Meantime, I can't distribute any technical product documentation because none of the links in the documents work.

What are you doing to fix this, Microsoft? It is absolutely catastrophic for Technical documentation departments.

@Jallen666Agree with you there. The changing versions work-around is only for people who have full control and what's happened is a pretty fundamental regression in Word functionality. I raised a ticket with MS, but the "switch to semi annual" response was what I got back.

 

However, I'm not even sure semi annual will be a long term fix - the XPS/PDF export "fix" that I suspect caused the problem was in the semi annual preview channel build for Sept 14 (Build 14326.20404), so the problem may crop up in the semi annual channel in March 2022.

Actually, according to this thread (https://answers.microsoft.com/en-us/msoffice/forum/all/cross-reference-links-eg-table-of-content-tab...) the issue has been resolved in the latest Current channel.

The Oct 14 release, coming just 2 days after the previous release does seem to be an attempt to patch this regression.