If you put a multi-row table inside a single Page Properties macro, Confluence will often bunch that data up or fail to display it as distinct rows in the master report. Method 1: The Multi-Page Approach (The Standard Way)
Use a clear header row in your Page Properties table so the report knows what to call each column.
Using the Page Properties Report macro is one of the best ways to build dynamic dashboards in Confluence. However, users often run into a common frustration: the macro only pulls a single row of data per page.
By creating multiple child pages, each with its own Page Properties macro, the Report macro will automatically generate in a table—one row per child page. confluence page properties report multiple rows
Add the Page Properties Report to display all data.
Add your target label (e.g., meeting-action ) to the . The Catch with This Method:
I can provide a step-by-step blueprint or code snippet tailored exactly to your environment. Share public link If you put a multi-row table inside a
Label all your child pages (e.g., project-risk ).
You put a standard table with multiple rows inside your Page Properties macro.
Insert the ( /page properties report ).
Confluence headers are case-sensitive. If your table column on the source page is named Due Date , but your report configuration looks for due date , the column will return empty.
In the left column, put your metadata keys: Status , Owner , Due Date , Impact . In the right column, enter the specific data for this item.
| Page Title | Status | Owner | Due Date | |---------------------|--------------|-------|----------| | Design homepage | Done | Alice | Jan 10 | | Write API docs | In Progress | Bob | Jan 15 | However, users often run into a common frustration: