nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why Page Properties Report macro only pick up first row of Page Properties macro's multi-row table.

Chien-sheng Tsai

I have 13 parent pages, with 5 sub-pages each. One of the 5 sub-pages is designated as an Issues List page, whereby outstanding issues are listed. I used a Page Properties macro on this Issues List page, and inserted a 6 Column by 10 Row (6C x 10R) table within the Page Properties macro.

Some of the 13 Issues List Pages have Issues listed in a certain time frame/period, and some do not, depending upon circumstances–users populate the issues list, and it should be dynamic,

Then I go to my Space Summary Page, which captures and summarizes matters from the 13 Parent pages and their child pages. I wish to automatically transfer the Issues cited on the 13 individual Issues List pages.

So I intend to incorporate 13 Page Properties Report macros on the Space Summary Page, each one capturing select Columns but all the (populated) Rows of the individual tables resident on the respective Issues List pages.

And herein lies the problem: The individual Issues List page (with the Page Properties macro) does present all the Column and the Rows of each table, but the linked Page Properties Report macro only picks up the First Row of this table. I tested with a second Page Properties Report macro, and it also only picks up the First Row.

Question: How can the Page Properties Report macro be made to pick up all the (populated) Rows of the

related table, or is this not possible? (Note: I do not want to show all the Columns, and it was OK to show only selected Columns).

Accepted answers

All comments

Davin Studer

That is not how the page properties macro works. It expects to find key/value pairs in it. Like this ...

image2015-4-9 13:29:16.png

or this

image2015-4-9 13:30:2.png

It is meant to convey properties about that page alone which are then aggregated on the report macro.

image2015-4-9 13:29:16.png

image2015-4-9 13:30:2.png

Chien-sheng Tsai

Transfer of Rows into Column, thus only one Resultant Row. I see. This is what I have. I could not upload an image due to corporate data transfer restriction. Page Properties: A_Header B_Header C_Header D_Header E_Header F_Header Row 1 Row 1 Row 1 Row 1 Row 1 Row 1 Row 2 Row 2 Row 2 Row 2 Row 2 Row 2 Row 3 Row 3 Row 3 Row 3 Row 3 Row 3 Row 4 Row 4 Row 4 Row 4 Row 4 Row 4 Page Properties Report (I only select 4 of the 6 columns, and the headers were OK): Title A_Header B_Header D_Header E_Header PageName Row 1 Row 1 Row 1 Row 1 Per above, if it is as you indicated, I should have ended up with this: A_Header Row 1 Row 2 Row 3 Row 4 B_Header Row 1 Row 2 Row 3 Row 4 But I did not. How to explain??

Chien-sheng Tsai

Aside from the Page Properties Report macro, what can I use to get what I want, a summary list of outstanding issues, generated automatically off of a different page that has all the details and where the issues are input? Thanks, All.

Davin Studer

If you look at the screen shots above the keys are in either a header row or column. You can see this visually based on the color difference. When you edit a table there are two buttons in the edit bar to toggle the column or row as a header. That is why both of my screenshots work. There is one header that contains the keys and one body that contains the values. This is also why you are seeing what you are seeing. The first row in your table is a header row. The next row are the values. The rest of the rows are ignored. You are not using the page properties macro the way it was meant to be used. It is meant to convey key/value pairs of meta data about the page that it is on.