|
|
If you’ve ever tried to build a dynamic dashboard, a team directory, or a product feature list in Confluence, you’ve likely stumbled upon two powerful macros: Page Properties and Page Properties Report .
Have a unique use case? Share it in the Atlassian Community forums – the collective wisdom of Confluence admins is unmatched. confluence page properties report multiple rows
By default, the Page Properties macro is designed to hold one set of metadata per page (like a header row). So, when you run a report, you typically see one row per page. However, with the right techniques, you display multiple rows from a single source page. If you’ve ever tried to build a dynamic
| Method | Best For | Native? | Complexity | |--------|----------|---------|-------------| | One page per row | Scalable, clean data | Yes | Low | | Multiple macros per page | Small, fixed datasets | Yes | Medium | | Confluence Databases (Premium) | Modern teams, large data | Yes (new) | Low | | Marketplace add-ons | Legacy Confluence without Premium | No | Medium | By default, the Page Properties macro is designed
- Item 1 - Item 2 - Item 3 In list mode, the Page Properties Report will render these as a bullet list for that page. It’s still one row per page, but the row contains multiple lines.
This is by design. Confluence treats each page as a single entity, not a spreadsheet. To choose the right solution, ask yourself: What am I trying to track?
At first glance, these macros seem simple. You add a Page Properties macro to a page, fill in a few fields, and then use the Page Properties Report macro on another page to pull that data. But a common question arises when users try to scale this system:
| Â |