If some child pages don't define a property (e.g., one risk has no Impact ), the report leaves that cell blank. No error occurs.
To ensure your reports remain fast and readable, follow these best practices:
A macro placed on child pages that acts as a container for metadata (key-value pairs, often in a two-column table). confluence page properties report multiple rows
In your report page, create separate Page Properties Report macros, each targeting a specific macro ID. Assign each macro a numeric ID that matches the row number:
: If you want to pull only specific rows into different reports, give each macro a unique Property ID in the macro settings. If some child pages don't define a property (e
Use a clear header row in your Page Properties table so the report knows what to call each column.
If you want to tailor this setup to your exact workflow, let me know: Are you using or Confluence Data Center ? In your report page, create separate Page Properties
The report will now automatically crawl every page bearing that label and display them as in your master table.
If you have multiple Page Properties macros on one page or a multi-row table inside a single macro, the standard report macro often fails to treat them as separate rows, instead merging them into one entry or only displaying the first one. Method 1: The Multiple Macro "ID" Workaround
Behavior and constraints