This comprehensive guide will show you exactly how to configure your Confluence space to generate a flawless Page Properties Report with multiple rows. How the Page Properties Landscape Works

To take your multi-row dashboards to the next level, experiment with the report macro settings:

In the field, enter the label you used on your child pages (e.g., project-status ).

18;write_to_target_document1b;_ciPuabL2OOfP2roP5bu40A0_100;6;

Small, stable datasets (e.g., 3–5 rows per page) where you control all content.

: The report will then show one row for every macro found on that page. Note that if the macros share a common header, they may still be split into multiple rows in the report. Option 2: Restructure to Key-Value Pairs

Ensure every page intended for the report uses the exact same label.

Normally, if you have 10 child pages, the report shows 10 rows. However, you might have a single page that contains: A list of risks (Risk A, Risk B, Risk C). A set of user stories. Multiple deliverables with different statuses.

In the field, type your designated label: project-status-2026 . Click Save and publish the page.

Used on individual child pages, this macro contains a table (often a two-column key-value pair) that holds data you want to report on.

To display multiple rows in the report, you need to configure the Page Properties Report macro to use a specific layout. To do this, follow these steps:

macro, only to find that it only pulls in one row of data per page? It is a common frustration for teams trying to summarize complex project details or multi-part status updates.

Here’s a clever trick: You can place on a single Confluence page, each representing a “virtual row.”

While possible, native Confluence Page Properties Report can sometimes struggle with complex, multi-row structures. If the report only shows the first row, you may need to reconsider your data structure. Alternatives for Complex Reporting

When you run the report, the output will typically only show: . The subsequent rows are ignored because the report structure expects a unique set of metadata keys per page.

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

println reportHtml

You can place Jira issue macros inside the right-hand column of your child pages. The Page Properties Report will dynamically pull and display the live Jira status directly inside your multi-row table.