Confluence Page Properties Report Multiple Rows [OFFICIAL]

By creating multiple child pages, each with its own Page Properties macro, the Report macro will automatically generate multiple rows in a table—one row per child page.

In the macro settings, under Columns to show, enter a comma-separated list (no spaces):
Status,Owner,Due Date

On each page that should become a row in the report:

✅ Each labeled page = one row in the final report.

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.

If you need a Page Properties Report that shows multiple rows (one row per child page) from Page Properties macros on child pages, use the built-in Page Properties Report macro configured like this:

|| Key || Value ||
| Status | In Progress |
| Owner  | Alice      |
| Due    | 2026-04-15 |

Notes:

If you want, I can generate the exact macro code snippet or a template table for your child pages — tell me the property keys you use.

The Confluence Page Properties Report macro is one of the most powerful tools for project management and tracking. It allows teams to aggregate data from multiple child pages into a single "master" view. However, users often encounter a specific structural limitation: how to handle scenarios where a single page contains multiple rows of data. confluence page properties report multiple rows

If you have ever tried to report on a table inside a Page Properties macro that has more than one row, you know the frustration. By default, the Page Properties Report is designed to extract only the first row of data it finds. This creates a flat, one-to-one relationship between the page and the report entry.

So, how do you manage "one-to-many" data relationships? Below we explore the problem, the workarounds, and best practices.

Summary

Why multiple rows is requested

Behavior and constraints

Workarounds and patterns

Implementation checklist (one-per-child approach)

Tips and best practices

Recommended next steps

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

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.

The standard Page Properties macro is primarily designed to handle "key-value pairs" (like "Status: In Progress"), resulting in a single row per page in your final report. However, there are a few clever ways to bypass this limitation and display multiple rows from a single page in your report. 1. The Native Hack: Multiple Macros with Unique IDs

The simplest way to get multiple rows in a report without third-party apps is to use multiple Page Properties macros on your source page. How it works:

Each Page Properties macro you add to a page counts as a new entry for the report. The Pro Tip: To keep things organized, use the

parameter in the macro settings. You can then configure your Page Properties Report macro to only pull in specific IDs, or leave it blank to pull every macro on that page as its own row. Limitation:

This can be manual and tedious if you have dozens of rows to track. 2. The Power User Choice: Third-Party Apps ✅ Each labeled page = one row in the final report

If your team needs to report on large, dynamic tables with many rows, the native macro often falls short. Many Atlassian Community members recommend the Table Filter and Charts for Confluence The Macro: Table Excerpt Table Excerpt Include The Benefit:

Unlike the native version, these macros are specifically built to "scrape" entire multi-row tables from one page and display them fully on another. Official Marketplace Link: You can find these tools on the Atlassian Marketplace 3. Alternative: The "Child Page" Strategy

If you want to stick to native Confluence features but find multiple macros too messy, try the "Child Page" architecture. Structure:

Create one "Parent" page for your project and individual "Child" pages for each item or task. Execution: Place a single Page Properties macro on every child page.

When you run the Page Properties Report on your parent page, it will automatically generate one row for every child page, creating a clean, automated multi-row list. Troubleshooting Common Row Issues Page Properties Report Macro | Confluence Data Center 10.2

In Confluence, the Page Properties Report macro is natively designed to display only one row per page. If a single Page Properties macro contains a table with multiple rows, the report will typically only display the first one.

To display multiple rows in a report from a single source page, you can use these official methods and common community workarounds: Official Methods

Multiple Page Properties Macros: You can place several Page Properties macros on one page. If they have different header names, the report may display them in one row; however, if they share common headers, the report will split them into multiple rows for that same page.

Use Unique IDs: Assign a unique Page Properties ID to each macro on your source page. In your Page Properties Report, you can then specify which specific IDs to include, or leave it blank to report on all of them as separate entries.

Create a single page that explains: “Rows come from child pages under /Data, labeled with project-alpha.” Future you will thank you.