Confluence Page Properties Report: Handling Multiple Rows
The Confluence Page Properties Report macro is a powerful tool for displaying metadata from pages in a table format. However, one common challenge users face is dealing with multiple rows in the report when a page has multiple property values. In this article, we'll explore how to effectively manage and display multiple rows in a Confluence Page Properties Report.
Understanding the Issue
When you add a Page Properties Report macro to a Confluence page, it retrieves property values from the pages that match the specified criteria. If a page has multiple values for a property, the report will display multiple rows for that page, one for each property value. This can lead to a cluttered and confusing report, especially if you're dealing with a large number of pages or complex property values.
Configuring the Page Properties Report
To handle multiple rows in a Page Properties Report, you can try the following configurations:
- Use a delimiter: If you're using a property with multiple values, you can specify a delimiter (e.g., comma, semicolon) to separate the values. This will display all values in a single cell, rather than creating multiple rows.
- Group by page: Make sure the "Group by page" option is enabled in the report macro settings. This will ensure that each page is only listed once in the report, even if it has multiple property values.
- Use a custom template: Confluence allows you to create custom templates for the Page Properties Report. You can design a template that handles multiple rows or values more elegantly.
Alternative Solutions
If the above configurations don't meet your needs, consider the following alternative solutions:
- Use a different macro: Confluence offers other macros, such as the Page Properties macro, that can help you display metadata in a more flexible way.
- Create a custom report: If you have specific reporting requirements, you can create a custom report using Confluence's API or a third-party plugin.
Best Practices
To avoid issues with multiple rows in your Page Properties Report:
- Plan your property structure: Before creating a report, think about how you'll structure your property values. Consider using delimiters or separate properties for different values.
- Test your report: Always test your report with sample data to ensure it displays as expected.
- Document your setup: Keep a record of your report configuration and any custom templates or solutions you implement.
By following these tips and best practices, you can effectively manage multiple rows in your Confluence Page Properties Report and create informative, easy-to-read tables that meet your needs.
In Confluence, the Page Properties Report macro is designed to aggregate data from multiple pages into a single table, with each page typically representing one row in the final report. This limitation can be a hurdle for users who need to display multiple distinct records or rows originating from a single page. Understanding the Limitation
The native Page Properties macro is optimized for "key-value" pairs (like Status: Active, Owner: Sarah). When you use a Page Properties Report, Confluence scans pages for specific labels and pulls the first row of data it finds within a Page Properties macro on those pages.
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
You can include multiple Page Properties macros on a single page, but to report on them effectively, you must assign each a unique ID.
Duplicated rows in page properties report - Atlassian Community
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)
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
In Confluence, the Page Properties Report macro is designed to display one row per page. If you need to show multiple rows for a single page, you must use specific workarounds or third-party apps, as the standard macro is intended for rolling up singular instances of metadata across multiple pages. Native Workarounds
If you do not have access to third-party apps, you can try these native structural changes: Multiple Page Properties Macros : You can add several Page Properties macros to a single page. If they share the same label, the Page Properties Report will display them as separate rows. Vertical Table Formatting Page Properties macro Insert a table and remove the last column. Table Options Header Row Header Column
The left column (Header Column) acts as your property names, and the right column contains your values. Nested Tables (Visual Trick)
: Place a single-row table inside the Page Properties macro, but create a nested table
within the value cell to display multiple data points in that single row. Advanced Solutions (Third-Party Apps)
For more robust reporting without manual restructuring, third-party apps provide specialized macros:
Confluence Page Properties Report: How to Display Multiple Rows
Confluence is a powerful collaboration platform that enables teams to create, share, and manage content. One of its most useful features is the Page Properties Report macro, which allows users to create a table that displays properties from multiple pages. However, one common limitation of this macro is that it only displays a single row of data. In this article, we'll explore how to display multiple rows in a Confluence Page Properties Report.
What is a Confluence Page Properties Report?
A Page Properties Report is a macro in Confluence that enables users to create a table that displays properties from multiple pages. This macro is useful for creating reports, dashboards, and other types of pages that require data from multiple sources. With a Page Properties Report, users can easily create a table that displays information such as page titles, authors, creation dates, and more.
The Limitation: Single Row Display
By default, the Page Properties Report macro only displays a single row of data. This can be limiting when you need to display data from multiple pages. For example, if you have a report that needs to display data from 10 different pages, you would need to create 10 separate Page Properties Report macros, each displaying a single row of data. This can be cumbersome and make your page look cluttered.
Solution: Using the Page Properties Report with Multiple Rows
So, how can you display multiple rows in a Confluence Page Properties Report? The solution involves using a combination of Confluence macros and some clever configuration. Here are the steps:
Step 1: Create a Table on Each Page
To display multiple rows in a Page Properties Report, you need to create a table on each page that contains the data you want to display. This table should have a single row with the properties you want to display. For example, if you want to display the page title, author, and creation date, your table might look like this:
| Page Title | Author | Creation Date | | --- | --- | --- | | My Page | John Doe | 2022-01-01 |
Step 2: Add the Page Properties Macro
On each page, add the Page Properties macro to the table you created in Step 1. This macro will allow you to specify the properties that you want to display in the report.
Step 3: Add the Page Properties Report Macro
On the page where you want to display the report, add the Page Properties Report macro. This macro will allow you to specify the pages that you want to include in the report.
Step 4: Configure the Page Properties Report Macro
To display multiple rows in the report, you need to configure the Page Properties Report macro to use a specific layout. To do this, follow these steps:
- In the Page Properties Report macro, select the Table layout.
- In the Table columns field, specify the columns that you want to display. For example, if you want to display the page title, author, and creation date, enter
Page Title, Author, Creation Date. - In the Rows field, select Multiple rows.
Step 5: Add Pages to the Report
To add pages to the report, click the Add pages button and select the pages that you want to include. You can select multiple pages by holding down the Ctrl key (Windows) or Command key (Mac).
Step 6: Save and View the Report
Save the page and view the report. The Page Properties Report macro should now display multiple rows of data, one for each page that you selected.
Tips and Variations
Here are some tips and variations to help you get the most out of the Page Properties Report macro:
- Use a template: If you have multiple pages with the same properties, you can create a template that includes the Page Properties macro and the table. This will save you time and ensure consistency across your pages.
- Use a query: If you have a large number of pages and want to display only a subset of them, you can use a query to filter the pages. For example, you can use a query to display only pages that were created in the last month.
- Customize the layout: You can customize the layout of the report by using CSS styles or by creating a custom template.
Conclusion
Displaying multiple rows in a Confluence Page Properties Report is a powerful way to create reports and dashboards that showcase data from multiple pages. By following the steps outlined in this article, you can create a report that displays multiple rows of data, making it easier to analyze and visualize your data. Whether you're a Confluence power user or just starting out, this article has provided you with the knowledge and skills to take your reporting to the next level.
Here’s a clear write-up explaining how to display multiple rows using the Page Properties Report macro in Confluence.
Method 5: Marketplace Add-Ons (For Serious Multi-Row Needs)
If you don’t have Premium or need advanced reporting, Atlassian Marketplace offers several apps that extend Page Properties:
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.
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.
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.
What happens?
The Page Properties Report macro will treat each Page Properties macro instance on the same page as a separate “row” – because each macro has its own internal table.
Example:
Page: Product Roadmap
- Macro 1:
Feature: Login | Priority: High - Macro 2:
Feature: Dashboard | Priority: Medium - Macro 3:
Feature: Reports | Priority: Low
Report output: Three rows, all linking back to the same Product Roadmap page.
Limitations:
- No native way to label individual macros for filtering.
- Editing is messy – you must scroll through multiple macros on one page.
- Can confuse team members who expect one macro per page.
Best for: Small, stable datasets (e.g., 3–5 rows per page) where you control all content.
Real-World Example: Building a Multi-Row Risk Register
Let’s build a Risk Register where a single project page has 5 risks, and you want all 5 to appear in a company-wide report.
Conclusion
The Page Properties + Page Properties Report combination is a hidden gem in Confluence. By structuring data across multiple child pages—each containing a Page Properties macro—you can generate a multi-row report that stays synchronized automatically. Add a new child page, and your report grows by one row. Edit a property on any child page, and the report updates instantly.
This approach is ideal for:
- Risk registers
- Decision logs
- Asset inventories
- Meeting action trackers
- Simple CRM or project trackers
Start small: create two child pages, see the two rows appear, then scale up to dozens or hundreds. No code, no plugins—just smart macro usage.
Last updated: March 2025 – Compatible with Confluence Data Center and Cloud (standard macros).
In Confluence, the Page Properties Report is natively designed to display one row per page. If you need to report on multiple rows from a single source page, you must use specific workarounds, as the macro typically only pulls the first row of data it finds. Option 1: Native "Multiple Macros" Workaround
To get multiple rows for one page in your report, you can add multiple Page Properties macros to that page.
Setup: Place each row of data into its own individual Page Properties macro on the source page.
Configuration: In the Page Properties Report macro settings, specify the Label used on those pages.
Behavior: The report will then show one row for every macro found on that page. Note that if the macros share a common header, they may still be split into multiple rows in the report. Option 2: Restructure to Key-Value Pairs
The most reliable native method is to use a two-column table where the left column is the header (the "Key") and the right is the "Value". Insert the Page Properties macro. Create a table with two columns. Make the left column a Header Column.
Enter your property names on the left and values on the right. Option 3: Third-Party Apps (Advanced)
Unlocking the Power of Multi-Row Reports in Confluence Have you ever tried to create a master dashboard in Confluence using the Page Properties Report
macro, only to find that it only pulls in one row of data per page? It is a common frustration for teams trying to summarize complex project details or multi-part status updates.
The standard Page Properties macro is primarily designed to handle "key-value pairs" (like "Status: In Progress"), resulting in a single row per page in your final report. However, there are a few clever ways to bypass this limitation and display multiple rows from a single page in your report. 1. The Native Hack: Multiple Macros with Unique IDs
The simplest way to get multiple rows in a report without third-party apps is to use multiple Page Properties macros on your source page. How it works:
Each Page Properties macro you add to a page counts as a new entry for the report. The Pro Tip: To keep things organized, use the
parameter in the macro settings. You can then configure your Page Properties Report macro to only pull in specific IDs, or leave it blank to pull every macro on that page as its own row. Limitation:
This can be manual and tedious if you have dozens of rows to track. 2. The Power User Choice: Third-Party Apps
If your team needs to report on large, dynamic tables with many rows, the native macro often falls short. Many Atlassian Community members recommend the Table Filter and Charts for Confluence The Macro: Table Excerpt Table Excerpt Include The Benefit:
Unlike the native version, these macros are specifically built to "scrape" entire multi-row tables from one page and display them fully on another. Official Marketplace Link: You can find these tools on the Atlassian Marketplace 3. Alternative: The "Child Page" Strategy
If you want to stick to native Confluence features but find multiple macros too messy, try the "Child Page" architecture. Structure:
Create one "Parent" page for your project and individual "Child" pages for each item or task. Execution: Place a single Page Properties macro on every child page.
When you run the Page Properties Report on your parent page, it will automatically generate one row for every child page, creating a clean, automated multi-row list. Troubleshooting Common Row Issues Page Properties Report Macro | Confluence Data Center 10.2
Strategy 3: Third-Party App Add-ons
For organizations heavily reliant on this functionality, the native Confluence macros often fall short. This is one of the primary drivers for add-ons like Aura or Table Filter and Charts.
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.
1. Always define a primary key.
If you use multiple pages (Method 1), ensure each page title or a dedicated column (e.g., ID) is unique.