Confluence Page Properties Report Multiple Rows [top] -
If your report is merging all your data into a single row, check your table orientation. The Page Properties Report expects the first column of your container table to hold the keys (headers) and the second column to hold the values. If you oriented your container table horizontally, Confluence will read it incorrectly. Missing Rows in the Report
Page Properties and Page Properties Report work together through . When you insert a Page Properties macro on a page, Confluence automatically adds a label to that page. The report macro then pulls data from all pages that carry that same label, regardless of how many Page Properties macros exist on those pages.
table-excerpt:name=risk-register ||Risk ID||Description||Status||Owner|| |R001|Database outage|Open|jsmith| |R002|API latency|In Review|mjones| table-excerpt confluence page properties report multiple rows
But here’s the catch: The report usually shows (each page’s properties in one row). Jordan needed multiple rows per page because some services had multiple critical environment variables, each requiring its own row for test tracking.
If you use a multi-row table, the report will often try to cram all that data into a single cell or fail to parse it correctly. If you need a true "database" feel with many rows, is significantly more reliable. Common Issues and How to Fix Them 1. Rows Aren't Appearing If your report is merging all your data
18;write_to_target_document1b;_ciPuabL2OOfP2roP5bu40A0_100;4ae;0;6b3; 0;26c;0;7f0;
This approach keeps the information compact within the single row constraint. Missing Rows in the Report Page Properties and
: Each row in your report must correspond to a distinct Confluence page. If you have multiple "Page Properties" macros on a single page, the report will often merge them into one row or only display the first one. To get ten rows of data, you generally need ten separate pages.
For the audit requirement, Jordan used (via the official SQL for Confluence add-on) to query page properties across all pages and output true multiple rows per source page. Example query:
