Problem

Customers need consistent results on PDF Export using the App 'Scroll PDF Exporter,' with pages containing transformed tables.

• These tables are related to the 'Table Toolbox' from another App ('Table Filter, Charts & Spreadsheets for Confluence').

Different vendors don't have the ability to collect the rendered information from a page via API because they are using the below endpoint to collect data:

• API V2 endpoint:

  https://<instance-url>.atlassian.net/wiki/api/v2/pages/<page-id>?body-format=export_view
  

However, the endpoint above only provides static content, not meeting the vendor's needs and consequently affecting customers.

Currently, there's no possibility to obtain the correct rendered view of a page from an API or external perspective. Therefore other Applications could be affected by this limitation on collecting the exact rendered view, please add a comment below for additional reference.

Suggested Solution

The idea would be to find a way to retrieve the content as seen in view mode so Scroll PDF can manipulate it and add it to the exported file. 

Why This Is Important

The native PDF export in Confluence has several different limitations, and Apps are required for features like custom PDF formatting, custom templates, workflow management

Workaround

Currently, there's no workaround available for such limitations on the API. And the customers have to rely on the native PDF export.

Considering that Confluence native PDF export uses an internal library, which creates a target file with styles and the code is not available for 3rd party app developers.
As a possible workaround, developers might need to create their own web-based renderer service, which will add styles/renders to the page, like the AUI service (https://aui.atlassian.com/).

Notes

Documentation:

• Atlassian Developer > Dynamic Content Macro

Steps to reproduce:

1. Create a page in confluence using the Table Toolbox Macro to merge two different Jira Issues (Merge tables, Lookup Tables, or Custom Transformation);
2. Create two other Table Transformer options with Jira Macros inside it;
3. Use the Custom Transformation option, then proceed with SQL Query to rename the Table fields, for example:

   SELECT
   T1.'Key' AS 'Requirement Key',
   T1.'Summary' AS 'Requirement Summary',
   T1.'Description' AS 'Requirement Description'
   FROM T1
   

• Export this page using the option "Export with Scroll PDF Exporter" on the three dots option, using any template (e.g., the default ones)

Then, if we compare this exported PDF with the PDF from Confluence, we will notice that the Macro shown on the page is different from the exported one by the App:

• The 'rename' made by the 'SQL Query' is ignored;
• The table transformation is ignored, exporting the Jira Macro entirely.