Confluence Page Properties Report Multiple Rows ((link)) ◆ ❲High-Quality❳

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.

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.

In these cases, using a Page Properties macro would force you to flatten your data. You would have to create separate pages for each risk or expense, or dump all the data into a single text field, making it impossible to sort or filter effectively.

The fundamental issue stems from a design choice in Atlassian's macro architecture: Each page in your report corresponds to a single Page Properties macro instance. If you place multiple tables or rows within a single Page Properties macro, the report will only capture the first one. confluence page properties report multiple rows

On each page that should become a in the report:

You place this macro on a child page. Inside it, you create a two-column table. The left column contains your keys (e.g., Status , Owner ), and the right column contains the values (e.g., In Progress , John Doe ).

Enter your property names on the left and values on the right. Option 3: Third-Party Apps (Advanced) Normally, if you have 10 child pages, the

: Inside each macro, insert a two-column table where the left column is the "Header" (key) and the right is the "Value" (data). 2. Configure the Report Macro

This comprehensive guide covers how the Page Properties Report works, why it defaults to one row, and the exact workarounds you can use to display multiple rows of data seamlessly. Understanding the Core Limitation

On your overview page, insert the macro to pull the table from the child page. Multiple deliverables with different statuses

The standard Page Properties Report is an exercise in reductionism. It takes the complex, messy narrative of a wiki page—a tapestry of prose, images, and threaded comments—and flattens it into a single row. One page, one row. This is the "Sovereign Row."

The struggle with multiple rows is a struggle against the medium.

SELECT p.title AS service, cp.var_name, cp.var_value FROM pages p, child_properties cp WHERE p.id = cp.page_id AND cp.property_set = 'env-vars'

But creating 45 pages (3 env vars × 15 services) was overkill. Instead, Alex found a cleaner method:

: If you want to pull only specific rows into different reports, give each macro a unique Property ID in the macro settings.