Before we solve the problem, let’s clarify the default behavior.
Example of the limitation:
You have a page called “Q1 Goals.” Inside the Page Properties macro, you list three goals in three separate rows. When you run a report from another page, Confluence will only show one row (the first one) from the “Q1 Goals” page. The other two are invisible to the report.
This is by design. Confluence treats each page as a single entity, not a spreadsheet.
The need to display multiple rows from a Page Properties Report is one of Confluence’s most frequent power-user requests. While the native tool isn’t built for this, you have several viable paths:
| Method | Best For | Native? | Complexity | |--------|----------|---------|-------------| | One page per row | Scalable, clean data | Yes | Low | | Multiple macros per page | Small, fixed datasets | Yes | Medium | | Confluence Databases (Premium) | Modern teams, large data | Yes (new) | Low | | Marketplace add-ons | Legacy Confluence without Premium | No | Medium |
Final recommendation:
Don’t force Confluence to be Excel. Instead, understand its page-based architecture and work with it – not against it. Once you master these patterns, you’ll build dynamic, multi-row dashboards that impress your team and simplify your workflows.
Next steps:
Try the “one page per row” method today. Create a template, build three child pages, and run a Page Properties Report. Then, explore Confluence Databases if available. You’ll never ask “how do I get multiple rows?” again.
Have a unique use case? Share it in the Atlassian Community forums – the collective wisdom of Confluence admins is unmatched.
Confluence Page Properties Report: Displaying Multiple Rows
The Confluence Page Properties Report macro allows you to display metadata from a page in a table format. However, by default, it only displays a single row of data. If you want to display multiple rows of data, you can use the following approaches:
Method 1: Using the Confluence Page Properties Report macro with multiple page property macros
You can add multiple Page Property macros to a single page, each containing a different set of metadata. Then, use the Confluence Page Properties Report macro to display all the page properties. confluence page properties report multiple rows
Here's an example:
| Page Property Macro 1 | Page Property Macro 2 | ... | | --- | --- | ... | | Property 1: Value 1 | Property 2: Value 2 | ... | | Property 3: Value 3 | Property 4: Value 4 | ... |
Confluence Page Properties Report Macro
| Property | Value | | --- | --- | | Property 1 | Value 1 | | Property 2 | Value 2 | | Property 3 | Value 3 | | Property 4 | Value 4 |
Method 2: Using a Table Macro with multiple rows
Alternatively, you can use a Table macro to create a table with multiple rows. You can then use the Page Property macro to populate the table cells.
Here's an example:
Table Macro
| Property | Value | | --- | --- | | Property 1 | page-property:Property 1 | | Property 2 | page-property:Property 2 | | Property 3 | page-property:Property 3 | | Property 4 | page-property:Property 4 |
In this example, each row of the table displays a different set of metadata.
Method 3: Using a Third-Party Add-on
There are also third-party add-ons available that provide enhanced functionality for displaying multiple rows of data in a Confluence page properties report. One such add-on is the Advanced Page Properties add-on. Before we solve the problem, let’s clarify the
Advanced Page Properties Add-on
This add-on allows you to display multiple rows of data in a page properties report using a simple syntax.
Here's an example:
Advanced Page Properties Macro
| Property | Value | | --- | --- | | advanced-page-properties | | Property 1 | Value 1 | | Property 2 | Value 2 | | Property 3 | Value 3 | | Property 4 | Value 4 | | /advanced-page-properties |
This add-on provides a more flexible and customizable way to display multiple rows of data in a Confluence page properties report.
Conclusion
Displaying multiple rows of data in a Confluence page properties report can be achieved using various methods, including using multiple page property macros, a table macro, or a third-party add-on. Choose the method that best fits your needs and requirements.
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) Example of the limitation: You have a page
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.
In the architectural DNA of Atlassian’s Confluence, there exists a quiet assumption: that a page is a sovereign entity—a singular container of truth, a distinct node in the network. This assumption holds firm until one encounters the Page Properties Report. Here, the monolith of the "Page" is dissolved, distilled into metadata, and rearranged into a grid.
But the system breaks—beautifully, violently—when the user attempts to force the singular to become the plural. The phenomenon of "multiple rows" in a Page Properties Report is not merely a formatting nuisance; it is a collision between the hierarchical nature of knowledge and the relational nature of data.
Confluence is a powerful collaboration tool, but one of its most underutilized features for structured data management is the Page Properties and Page Properties Report macro combination. When used correctly, these macros allow you to build a dynamic database of information—displayed as a clean table with multiple rows—without needing a third-party add-on like Table Filter or (in many cases) Comala Databases.
This article explains how to set up a "master-detail" system where child pages feed data into a single, sortable report on a parent page.
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.
Choose Sort by and optionally a secondary sort. The report supports ascending/descending.
Risk, Impact, Mitigation.project-phoenix-risk.Outcome: 3 rows in the report.