Confluence Page Properties: Report Multiple Rows
Confluence’s Page Properties Report is designed for unique metadata per page (One Page = One Report Row). If you need One Page = Multiple Report Rows, the native functionality fights against you.
The best practice is usually Strategy 1 (Flattening): Rename your rows to Item 1, Item 2, Item 3. While this makes your source table slightly more verbose, it results in a robust, sortable report that captures all your data without requiring expensive add-ons or switching to the Task Report system.
Confluence Page Properties Report: Handling Multiple Rows
The Confluence Page Properties Report macro is a powerful tool for displaying metadata from pages in a table format. However, one common challenge users face is dealing with multiple rows in the report when a page has multiple property values. In this article, we'll explore how to effectively manage and display multiple rows in a Confluence Page Properties Report.
Understanding the Issue
When you add a Page Properties Report macro to a Confluence page, it retrieves property values from the pages that match the specified criteria. If a page has multiple values for a property, the report will display multiple rows for that page, one for each property value. This can lead to a cluttered and confusing report, especially if you're dealing with a large number of pages or complex property values.
Configuring the Page Properties Report
To handle multiple rows in a Page Properties Report, you can try the following configurations:
Alternative Solutions
If the above configurations don't meet your needs, consider the following alternative solutions: confluence page properties report multiple rows
Best Practices
To avoid issues with multiple rows in your Page Properties Report:
By following these tips and best practices, you can effectively manage multiple rows in your Confluence Page Properties Report and create informative, easy-to-read tables that meet your needs.
Page Properties Report macro is natively designed to roll up key-value pairs from multiple pages, showing one row per source page
. If you need to display multiple rows from a single page in your report, you have three primary options: Atlassian Community 1. The Multi-Macro Workaround (Native) You can place multiple Page Properties macros
on a single page. If they share the same table headers and page label, they will appear as separate rows in your report. Atlassian Documentation Page Properties Macro for each row you want to report. Ensure each macro contains a table with a Header Column on the left and data on the right. Assign a unique
to each macro in its settings if you need to filter specific ones. Label the page and use that label in your Page Properties Report Macro Atlassian Documentation 2. Nested Table "Trick" (Visual Only)
If you want the report to technically stay as one row but display a full list of items: Confluence page properties and page properties report.
Here’s a clear write-up explaining how to display multiple rows using the Page Properties Report macro in Confluence. Confluence’s Page Properties Report is designed for unique
Pros: Native, powerful, replaces the need for Page Properties Report for tabular data.
Cons: Requires Confluence Premium; not yet available in Standard or Free plans (as of 2025).
If you have access to Databases, stop using Page Properties for multi-row data. Migrate immediately.
If you’ve ever tried to build a dynamic dashboard, a team directory, or a product feature list in Confluence, you’ve likely stumbled upon two powerful macros: Page Properties and Page Properties Report.
At first glance, these macros seem simple. You add a Page Properties macro to a page, fill in a few fields, and then use the Page Properties Report macro on another page to pull that data. But a common question arises when users try to scale this system:
"How do I get the Page Properties Report to show multiple rows of data from the same page?"
By default, the Page Properties macro is designed to hold one set of metadata per page (like a header row). So, when you run a report, you typically see one row per page. However, with the right techniques, you can display multiple rows from a single source page.
This article will walk you through exactly how to achieve that, covering native workarounds, add-ons, and best practices for managing structured data in Confluence.
The struggle with multiple rows is a struggle against the medium.
If you have too many rows (duplication), you are witnessing the friction of "Unstructured Wiki" meeting "Structured Data." Confluence is permissive; it allows text to be entered in lists, tables, and macros interchangeably. The Page Properties Report is strict; it demands discrete key-value pairs. When the report attempts to map the permissive to the strict, it generates duplicates. It is the system saying, "You thought this was a document, but you tried to make it a spreadsheet. This is the price." Alternative Solutions If the above configurations don't meet
If you have too few rows (the inability to generate multiple rows from one source), you are hitting the ceiling of Confluence's design. The tool was built to organize documents about processes, not the processes themselves. It creates static artifacts, not dynamic entities.
The macro generates a table where:
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.
To understand the solution, we must understand the mechanism. The Page Properties macro looks for metadata defined on a page. When the Page Properties Report macro scans that page, it maps the Rank (first column of your properties table) to the Value (second column).
Example Scenario: Imagine you are managing a "Team Skills Matrix." You have a page for "John Doe." On his page, you have a table listing three skills:
When you run the report, the output will typically only show: John Doe | Java | Expert. The subsequent rows are ignored because the report structure expects a unique set of metadata keys per page.
