If you absolutely must use the native Page Properties macro and cannot flatten your data, some users employ visual cheats, though these are unstable.
One method involves formatting the cell data. Instead of using multiple table rows, users use line breaks (<br>) or bullet lists within a single table cell.
Example:
The report will pull this as one massive text block. While it keeps the data together, it destroys your ability to sort or filter by individual skills.
Outcome: Live, editable, filterable rows. confluence page properties report multiple rows
On each page that should become a row in the report:
✅ Each labeled page = one row in the final report.
Clicking any row's page title opens the child page, where you can store additional information outside the Page Properties macro (e.g., long descriptions, attachments, comments).
Whichever method you choose, follow these rules to avoid chaos: If you absolutely must use the native Page
Create a single "template" page that contains the Page Properties macro. Inside this macro, define your columns using tables or labeled lists.
Option A – Using a Table (Recommended for multiple rows of properties per page): Inside the Page Properties macro, insert a 2-column table:
Option B – Using Definition Lists:
Inside the macro, use ;Property Name and :Property Value syntax.
Note: The Page Properties Report will treat each property name as a separate column. The report will pull this as one massive text block
The Page Properties Report macro will treat each Page Properties macro instance on the same page as a separate “row” – because each macro has its own internal table.
Example:
Page: Product Roadmap
Report output: Three rows, all linking back to the same Product Roadmap page.
Limitations:
Best for: Small, stable datasets (e.g., 3–5 rows per page) where you control all content.