Unlocking the Power of Multi-Row Reports in Confluence Have you ever tried to create a master dashboard in Confluence using the Page Properties Report
Commonly, users expect a one-to-one relationship: one page equals one row in a report. However, there are many scenarios where you need a single Confluence page to output to a report. Whether you are tracking multiple action items on one meeting note or listing several software requirements on a single specs page, here is how you master the "multiple rows" setup. The Fundamentals: How the Macros Talk to Each Other confluence page properties report multiple rows
: Ensure your Report macro is configured to look across the correct spaces. If your source pages are spread across "Marketing" and "Product" spaces, but your report is limited to "Marketing," you will miss half your rows. Unlocking the Power of Multi-Row Reports in Confluence
So, how do you manage "one-to-many" data relationships? Below we explore the problem, the workarounds, and best practices. The Fundamentals: How the Macros Talk to Each
Alex realized: The treats each page as one row by default, merging all properties into that row. To get multiple rows from one page, you must split each data item into its own separate page – or use a different approach.
3 rows in the report.
The short answer is . By default, if you place three separate Page Properties macros on a single page, the Page Properties Report macro will merge all the data into a single row for that page. It treats the page as the atomic unit of data. The Workaround: Multiple Macros with Unique IDs
