Confluence Page Properties Report Multiple Rows

The standard Page Properties Report is an exercise in reductionism. It takes the complex, messy narrative of a wiki page—a tapestry of prose, images, and threaded comments—and flattens it into a single row. One page, one row. This is the "Sovereign Row."

Do not build your pages from scratch every time. Create a master template or standard page blueprint first.

Add your target label (e.g., meeting-action ) to the . The Catch with This Method:

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 page properties report multiple rows

If you absolutely must host multiple data sets on a single page and want them to appear as distinct rows, you must use the ID parameter: Edit a source page and insert two Page Properties macros.

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 add-on.

Place , each representing a distinct row: The standard Page Properties Report is an exercise

Note: This will output two separate tables on your master page, not a single merged table. For a unified, native table experience, sticking to the "one page per row" architecture remains the best practice. Troubleshooting Common Errors

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.

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

This limitation becomes immediately apparent if you try to use it for rich datasets. Known bugs in Atlassian's Jira tracking system highlight the struggles users have faced for years. For instance, issues like CONFCLOUD-42801 serve as an umbrella for problems including Page Properties Report Macro only displays 30 results , pagination failures, and the macro's inability to correctly parse tables that don't conform to a strict vertical or horizontal heading structure. These issues reinforce that the macro is best suited for simple, single-record metadata, not complex, multi-row datasets.

| 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 |

These plugins often extend the functionality of tables, allowing for dynamic aggregation where a single page can spawn multiple rows in a summary report, bypassing the limitations of the native Page Properties macro logic.

: 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)