Confluence Cloud guide
Page Properties with multiple rows or several tables on one page
In short: The report reads one row of values from each Page Properties table, so extra rows of values in a horizontal table don't show up. Several Page Properties macros on one page are combined into one row when their names differ; Atlassian says the report shows several rows when they repeat the same names. To report on just one of the tables, give it a Page Properties ID and enter the same ID in the report.
One row of values per table
A Page Properties table is meant to hold one record: names in one row or column, values in the next. Atlassian's documentation says the table "can have a header row or a header column, but not both," and that the report "can extract data for only one header row or column per content properties macro."
So if you build a horizontal table with names in the header row and several rows of values below it, such as a list of risks, the report doesn't give you a row for each. An open suggestion, CONFCLOUD-40835, describes the current behavior: the macro "only pulls the first column or row from the table." The same goes for a vertical table with more than one column of values.
Several Page Properties macros on one page
A page can have more than one Page Properties macro. Without an ID, the report reads all of them:
- Different names in each, say Owner and Status in one macro and Budget in another: they are combined into one row for that page (CONFCLOUD-34141, CONFCLOUD-70478).
- The same names in each: the report shows that page in several rows. Atlassian said so when it fixed CONFCLOUD-34141 in July 2022: the report "will show multiple rows when the page has multiple properties with the same key," as in Server and Data Center. A few users reported in 2024 that this worked only some of the time, so test it on your site.
That second case is the built-in way to get several rows from one page: instead of one table with several rows of values, use one Page Properties macro per item, each with the same names.
Report on one table with a Page Properties ID
- Edit the page, open the settings of the Page Properties macro you want, and enter an ID, for example
risks. (Atlassian's Cloud docs call the field Content Properties ID.) - Check that the page has the report's label. The label is on the page, so it covers every macro on it.
- In the report's settings, enter the same label and the same ID.
The report then reads only the macros with that ID. A report takes one ID, so for two kinds of table use two reports, each with its own ID.
Tables migrated from Data Center
In Confluence Data Center, a Page Properties table can have a header row and a header column at the same time. Cloud allows only one of them. When such pages are migrated, the Cloud report shows empty columns. The workaround Atlassian gives in CONFCLOUD-82829 is to remove the header row from the Page Properties table.
Ways around the one-row limit
- One macro per item, with the same names in each, as described above.
- One page per item. If every risk or deliverable needs its own row, give each one a child page with its own Page Properties table. Then report on them with With ancestor or With parent plus their label.
- Numbered names. For a few items, use Risk 1, Risk 2 and Risk 3 as names in one vertical table. Each name becomes its own column.
- Several reports with IDs, when one page holds different kinds of record.
How our app reads these tables
We make Page Properties Report & Export for Confluence, so this part describes our own product. It doesn't solve the multiple-rows case:
- It lists one row per page and reads the same two layouts: a vertical table, or a header row with one row of values below it.
- It reads every Page Properties macro on a page, or only those with the Page Properties ID you enter.
- Property names match ignoring case and extra spaces, so "Owner" and "owner " share a column. If a name appears twice on one page, the first value is used.
So the one-macro-per-item trick above gives several rows in the built-in report but one row in ours. What our app adds is sorting every row, filtering and Excel or CSV downloads. The details are in the user guide.
Frequently asked questions
Can a Page Properties table have more than one row of values?
You can type them, but the report reads one row of values per table. Use one Page Properties macro per item, or one page per item, if each item needs its own row in the report.
What does the report show for a page with two Page Properties macros?
One row with all the properties when the macros use different names. When they repeat the same names, Atlassian says the report shows the page in several rows. Give a macro a Page Properties ID to report on it alone.
What is the Page Properties ID for?
It tells Page Properties macros on a page apart. A report with an ID reads only the macros with that ID. A report takes one ID.
Why are my report's columns empty after migrating from Data Center?
Data Center allows a header row and a header column in the same Page Properties table, but Cloud allows only one. Atlassian's workaround is to remove the header row from the table (CONFCLOUD-82829).
Read next
Sources
- Insert the content properties macro — Atlassian Support, Confluence Cloud: horizontal tables, several macros on a page, the ID, "one header row or column"
- Insert the content properties report macro — Atlassian Support, Confluence Cloud: the report's ID option
- CONFCLOUD-40835: Have Page Properties Macro pull multiple columns/rows from one macro — Suggestion, gathering interest
- CONFCLOUD-34141: Page Properties Report Macro fails to show all Page Properties in the same page with matching keys — Bug, fixed July 28, 2022; Atlassian's comment on that date
- CONFCLOUD-70478: Page Property report macro renders page information in different rows if multiple page property macro is used on a page — Bug, fixed July 2020
- CONFCLOUD-82829: Report on Page Properties macro migrated from Confluence DC containing both header row and header column — Suggestion, gathering interest