Confluence Page Properties Report Multiple Rows ^new^ -

Mastering Confluence: How to Create a Page Properties Report with Multiple Rows

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.

1. Create Labeled Pages with Page Properties

On each page that should become a row in the report: confluence page properties report multiple rows

• Insert the Page Properties macro.
• Inside it, use the Page Properties Edit macro to define columns (e.g., Status, Owner, Due Date).
• Add your data values.
• Apply a common label to every such page (e.g., project-task).

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

Common Pitfalls & Solutions

| Problem | Likely Cause | Fix | |---------|--------------|-----| | No rows appear | Wrong label or parent page | Check label spelling; ensure child pages are descendants | | Columns missing or misaligned | Inconsistent property names | Use the exact same property names in every Page Properties macro | | Values not updating | Confluence cache | Refresh the page; clear browser cache | | Extra empty rows | Pages with the label but no Page Properties macro | Remove label from those pages | Mastering Confluence: How to Create a Page Properties

Understanding the Limitation: One Page ≠ Multiple Rows (Natively)

Before we solve the problem, let’s clarify the default behavior.

• Page Properties Macro: Acts like a database table on a single page. You define column headers (e.g., Task, Owner, Status) and a single row of values.
• Page Properties Report Macro: Aggregates the first property row from multiple pages. It looks at each page that contains a Page Properties macro, extracts that one row, and stacks the pages as rows in the report.

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. Insert the Page Properties macro

This is by design. Confluence treats each page as a single entity, not a spreadsheet.

---

Method 1: The Native Workaround – One Page Per Row (But Hide Them)

The simplest native solution is counterintuitive: Don’t put multiple rows on one page. Create one page per row, and then use labels and the Page Properties Report to group them.

Step 1: Create a Labeling Strategy

Decide on a unique label to group your data pages. For example, if you are tracking project risks, use the label risk-item. This ensures the Report macro only pulls the correct pages.