Page Properties Report Not Showing All

[Debbie]

Hi everyone!

I really need the help if you have experience using Page Properties and Report on confluence. To give context, I want to use this as tracker for any action item from meeting notes and I already make my meeting notes from different pages but same parent and the same table format with page properties capability. 

But whenever I try to run report on it, it only show the first row of each table 

[Jan Kuntscher - appanvil - Aura Karma Mantra · Accepted solution]

Hi,

in Confluence the Page Properties macro only works with one row per page. If your table has multiple rows, the Page Properties Report will only ever show the first one - that’s the expected behavior.

Atlassian’s docs describe it here:
https://support.atlassian.com/confluence-cloud/docs/insert-the-page-properties-report-macro/

Best regards,

Jan

[Debbie]

Hi Jan!

Thank you for your respond.

I checked the article, but I dont find the statement of not able showing multiple rows, could you point out? 

Additionally, do you have any suggestion which macro to use to able to show all content?

[Jan Kuntscher - appanvil - Aura Karma Mantra]

Hi,

sorry, the link was for the properties report, but what you need is the properties macro itself: https://support.atlassian.com/confluence-cloud/docs/insert-the-page-properties-macro/

This is already the correct macro for what you want to achieve, however you need to restructure it to a two column design.

Best regards,

Jan

[Alex Dengler]

In the DC version this worked fine and well, right. So this is another thing that the cloud version lacks. It would be good to bring that ability back because what do you do if you have a list of items of the same type you have in a single page that you like to report. Example:

You describe a set of config keys for a feature X (Table with horizontal spread). In DC version you could create a table with header horizontally and it worked well and intuitively. Now I need to use a content property macro per config value. Technically this makes no sense but, from UX perspective this is horrible.