Cross referencing when exporting to word or pdf

[Chris Pearson]

I have created a scroll document in Confluence which has a series of figures. These figures are in the text as captioned items and cross referenced in the text using caption reference. When the document is viewed in Confluence these cross references appear correct such as "as can seen in Figure 1". However when the document is exported to a pdf or to word the format of the cross referencing changes. For a pdf it now appears as "as can be seen in 4W1LB(see figure 1)" where the 4W1LB is the figure anchor name. Is there a way without having to manually edit each time to get the cross references to show correctly in a pdf or word. 

[Kris Klima _K15t_]

Hi @Chris Pearson 

This is Kris from K15t, maker of the Scroll apps.

As @Arkadiusz Wroblewski said, if his remedies fail, do get in touch with our support team.

[Arkadiusz Wroblewski]

Hello @Chris Pearson 

Can you provide more information?

You using Data Center or Confluence Cloud ? 

[Chris Pearson]

Sorry not quite sure which bit of Confluence im using, says Confluence 9.2.4 if that helps. Is there an easy way to find out?

[Arkadiusz Wroblewski]

@Chris Pearson 

Since you’re on Confluence 9.2.4, you’re on Data Center. What you’re seeing (4W1LB(see figure 1)) is usually the exporter leaking the internal anchor ID into the output.

In many cases that happens because the Scroll export template is configured to optimize links for printing (or similar “print-friendly link” behavior). When that’s enabled, the exporter may append internal IDs/targets so the link is traceable on paper which is exactly the junk you don’t want in a PDF/Word deliverable.

So, combining the practical next steps:

Check your Scroll PDF/Word exporter template settings for anything like “optimize links for printing” and the figure/caption link label settings. If it’s enabled, disable it or adjust the label pattern so it outputs clean text like “Figure 1” without the anchor token.

Check you’re on a current exporter version compatible with Confluence 9.2.x. A lot of these edge cases get fixed or improved in exporter updates, and Confluence 9.x compatibility matters.

If after toggling the template/link-label settings it still prints the anchor, then I’d treat it as an exporter rendering limitation/bug and raise it with K15t/Scroll support, because you’re right: “manually fix every export” isn’t a solution.