Page Properties/Report: Spreading info over parent and child pages
Asked by Aur?lien Thazet:

Hi there,

I'm trying to build this kind of hierarchy in my confluence space for our projects by using Page Properties and Page Properties Report:

![scheme.png](/t5/image/serverpage/image-id/293773i0A151893ACB4B643/image-size/large?v=v2&px=999 "scheme.png")

Here are my needs:

* All the project information is garthered in the **Master Page** thanks to the *Page Properties Report*
* Only **Project Pages** should be editable (that's why there are only *Page Properties* there)
* The **Project Sub-Pages** should only have the info from their parent page (**Project Page** ) and not from other **Project Pages**
* **The Project Page** and the **Project Sub-Pages** will become a template used by many users. So I don't want a system where users have to tweak some elements to get the good spreading info.

*** ** * ** ***

Here is my progress:

* *Page Properties Reports* for **Master Page** works fine
* **Project Page** have all the *Page Properties* needed

*** ** * ** ***

However, I'm struggling with the **Project Sub-Pages**:

* I'm not able to get info only from the parent page (**Project Page**)
* I've tried many filters in the *Pages Properties Report* paramaters but it wasn't working

*** ** * ** ***

Maybe I'm not using the right tools to meet my needs. I've spent many hours on this without a good solution. If you have any suggestions, it would be greatly appreciated.

Many thanks,

Aur?lien


Answers:
author: Stiltsoft support
body: Hi [@Aur?lien Thazet](/t5/user/viewprofilepage/user-id/5373148) ,

Maybe different labels may help?

Then your master page will collect info from pages with different labels (project_1, project_2, progect_3, etc.) and each sub-page will collect only one specific label that refers to its project (project_1 for sub-page 1, project_2 for sub-page 2,...).

comments: author: Aur?lien Thazet
body: Hi [@Stiltsoft support](/t5/user/viewprofilepage/user-id/5062270) ,

Thank you for your help on this tough topic.

This is something I've already been thinking about. It could be a good solution if I could be able to automatically set the labels of each **Project Page** (in my knowledge it could be easily done) and if I could automatically add this label in the parameter of the *Page Properties Report* inside the **Sub-Pages** when I create a new **Project Page** (this is the point that I'm struggling with).


author: Stiltsoft support
body: As I know, labels are preserved in the templates, so the first point is easy indeed.

But you'll need to add the new labels manually inside the Page Properties Report macros.

We develop the [Table Filter and Charts for Confluence](https://marketplace.atlassian.com/apps/27447/table-filter-and-charts-for-confluence?tab=overview&hosting=cloud&utm_source=atl_community&utm_medium=answer&utm_campaign=table-filter-traffic-sources&utm_vendorID=1216111) app, maybe its [Table Excerpt/Table Excerpt Include](https://docs.stiltsoft.com/tfac/cloud/how-to-use-table-excerpt-and-table-excerpt-include-macros-42241623.html?utm_source=atl_community&utm_medium=answer&utm_campaign=table-filter-traffic-sources&utm_vendorID=1216111) macros will help if you create the following structure:

-- Master page

------ Sub-page 1

---------- Project page 1-1

---------- Project page 1-2

------ Sub-page 2

----------- Project page 2-1

----------- Project page 2-2

Then on each Project page you can place the Table Excerpt macro with the same name (for example, "Project"). This macro goes to the template and its name is predefined.

On every sub-page you place the Table Excerpt Include macro and choose to collect excerpts with the name "Project" on the page and its child pages. So, each sub-page will get a combined table only from its child pages.

On the master page you also place the Table Excerpt Include macro but collect excerpts named "Project" from page and its descendants (so, you'll collect all the projects from this page tree).


author: Aur?lien Thazet
body: Hi,

Thank you for your recommandations.

We have already purchased the app and I've been trying to implement your solution. There is only one thing which I can't manage.

I don't want to share all the information from the *Table Excerpts* of the **Project Pages** in all the **Sub-pages** of their parent page. I've tried to create a unique name foreach *Table Excerpt* in the **Project Page** and search them individually in the **Sub-pages** and that works perfectly fine.

But in the meantime, I'm not able to get all the information I'm looking for in the **Master Page** (because my all my *Table Excepts* from my **Project Pages** are no longer named "Project" ).

Do you have any suggestions?


author: Stiltsoft support
body: Got confused of your page structure now. :)

Please share the structure of your page tree like I did in my example.

-- Master page

------ Sub-page 1

---------- Project page 1-1

---------- Project page 1-2

------ Sub-page 2

----------- Project page 2-1

----------- Project page 2-2

As I thought, each Project Page contains an excerpt (one or several - our macros allow you to collect multiple-row tables as well, so you may break your tables into pieces or collect big tables at once).

Every Sub-page collects excerpts from its child pages only. For example, Sub-page 1 will only "grab" excerpts from Project page 1-1 and Project page 1-2.

The Master page collects all the excerpts (from Project page 1-1, Project page 1-2, Project page 2-1, Project page 2-2).


author: Aur?lien Thazet
body: Apologies for the misunderstanding. Here is the explanation with your page tree:

-- Master page *(w/ Table Excerpt Include to get all information below)*

------ Sub-page 1*(w/ Table Excerpt with different names like "Project - Summary", "Project - Workload", "Project - Allocation")*

---------- Project page 1-1 *(w/ Table Excerpt Include to get "Project - Summary", "Project - Allocation")*

---------- Project page 1-2 *(w/ Table Excerpt Include to get "Project - Workload")*

------ Sub-page 2 *(w/ Table Excerpt with different names like "Project - Summary", "Project - Workload", "Project - Allocation")*

----------- Project page 2-1 *(w/ Table Excerpt Include to get "Project - Summary", "Project - Allocation")*

----------- Project page 2-2 *(w/ Table Excerpt Include to get "Project - Workload")*


author: Stiltsoft support
body: So, I see now.

As best practice, it is always better to keep your excerpts on child pages and collect them on a parent page, then you'll be able to collect excerpts from child pages or all descendants automatically.

What concerns your structure, indeed you may set a sub-page as a page where to find excerpts inside the Table Excerpt Include macro and "pull" them by their names on the project pages. Seems that it works fine for you.

Then you go to the master page and choose to "grab" excerpts from all child pages (it will do for you as your sub-pages are child pages for your Master page).

Here you insert 3 Table Excerpt Include macros (each for its type of excerpts: *"Project - Summary", "Project - Workload", "Project - Allocation"*).


author: Angie Adams
body: Is there a good way to collect core project information at the parent page so that it can be shared on child pages without having to specify the page name or different labels (to keep it easy for non-technical users)?


author: Stiltsoft support
body: The Table Excerpt/Table Excerpt Include macros allow you to collect data from child pages or descendants (child pages and child's child pages) automatically. You'll have these two options in the Table Excerpt Include macro menu.

In these cases you don't need to specify any page names and set any page labels.


Tags: cloud

confluence-cloud

filter

table