Report Multiple Rows !!exclusive!! - Confluence Page Properties

To display multiple rows in a Page Properties Report, you must have multiple Page Properties macros on the source page(s) or multiple pages with the same label. 

By default, the report lists each page as a single row. If you need a single page to contribute multiple rows to a report, follow these steps:  1. Use Multiple Page Properties Macros 

Insert multiple macros: On your source page, add multiple Page Properties macros.

Unique IDs (Optional): If you want to pull only specific rows into different reports, give each macro a unique Property ID in the macro settings.

Standard Table: Inside each macro, insert a two-column table where the left column is the "Header" (key) and the right is the "Value" (data).  2. Configure the Report Macro 

Match Labels: Ensure the Page Properties Report macro is configured to look for the specific Label applied to your source pages.

Show All: If you have multiple Page Properties macros on one page, the report will automatically create a separate row for each macro instance found on that page.  3. Alternative: Table Excerpt (For complex tables)  confluence page properties report multiple rows

If you are trying to report on rows from a standard large table rather than key-value pairs, the native Page Properties macro is limited. Instead, you can use the Table Excerpt and Table Excerpt Include macros from third-party apps like StiltSoft to sync and filter specific table rows across pages.  Best Practices 

Consistent Headers: Use the exact same column headers in every Page Properties macro to ensure the report columns align correctly.

Hidden Macros: If you don't want the data tables visible on the source page, check the Hidden box in the Page Properties macro settings.

Page Labels: Remember that the report only finds pages that have the correct Label applied at the page level.  Page Properties Report Macro | Confluence Data Center 10.2

Strategy 2: The Task Report Macro Alternative

If your data is truly dynamic—meaning you don't know if there will be 3 rows or 30—and a "flat" structure isn't feasible, the Page Properties macro may be the wrong tool for the job.

In this case, you should pivot to using Confluence Tasks. To display multiple rows in a Page Properties

Instead of a table inside a Page Properties macro, have users create Task items (using the [] checkbox syntax) on their pages.

• Task: [ ] Learn Java
• Task: [x] Master Python

You can then use the Task Report Macro. This macro creates a one-to-many relationship naturally. One page (John Doe) can spawn multiple rows in the report (one for each task).

Pros:

• Naturally supports multiple rows per page.
• Allows for status tracking (complete/incomplete).

Cons:

• You lose the ability to have custom columns (like "Status: Expert vs Intermediate") unless you work them into the task description text.

Example: Project Risk Register

Parent Page: Risk Dashboard
Child Pages: Risk 001, Risk 002, Risk 003 (each labeled project-risk)

| Page Title | Status | Owner | Due Date | Impact | |------------|--------|-------|----------|--------| | Risk 001 | Open | Alice | 2025-05-01 | High | | Risk 002 | In Progress | Bob | 2025-04-15 | Medium | | Risk 003 | Closed | Alice | 2025-03-30 | Low | Strategy 2: The Task Report Macro Alternative If

This table is generated automatically. Adding a fourth child page creates a fourth row instantly.

3. Avoid nesting Page Properties macros.

Confluence sometimes crashes or fails to render nested macros. Keep them at the same level.

The Illusion of Linear Narrative: A Treatise on the Confluence Page Properties Report and the Fracture of the Row

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.

Step-by-Step:

1. Create a template with the Page Properties macro. Define your columns (e.g., Feature, Priority, Status).
2. For each data row (e.g., each feature or task), create a new page using that template.
3. Label each page with a common identifier (e.g., feature-log and release-2.0).
4. On your dashboard page, insert a Page Properties Report macro.
5. Filter by the common label (release-2.0).

Result: You see multiple rows – each row is one child page.
Pros: Native, no plugins, works forever.
Cons: Creates many pages; can clutter your space if not organized in a parent page or tree.

Pro tip: Use the Children Display macro alongside the Page Properties Report to keep your hierarchy clean. Store all “row pages” under a single parent called “Hidden Data Pages” and exclude that parent from search/navigation.