Macros inside Page Properties

[Deleted user]

I would like to create the properties for my page by combining two tables with the Table Transformer macro. I did this inside of a Page Properties macro and it appears fine on the page, but on another page with a Page Properties Report macro that page's properties appear as if they were empty.

Is there any way to make a "computed" table work inside of a Page Properties? (a similar thing would be to use a Multiexcerpt Include inside of a Page Properties - that also does not work in exactly the same way).

Thanks,

David

[Victor Mutambuki]

David,

See how to use Table Transformer with Page Properties Macro.

https://docs.stiltsoft.com/display/public/TFAC/How+to+use+the+app+with+the+Page+Properties+Report+macro

Victor

[Deleted user]

Hi Victor - thanks for the quick reply. However, that's kind of the opposite of what I'm trying to do, right? That is taking a normal table in a Page Properties macro and then applying the Table Transformer to the Page Properties REPORT table. I'll play with this, but I don't think it is going to satisfy my use case.

[Mike Uveges]

I agree.  This answer does not answer the question asked.  I share David's question.  Should the Page Properties macro be able to return the results of a Table Transformer macro as input to the Page Properties Report macro?

[Katerina Kovriga _Stiltsoft_]

Hi @Mike Uveges ,

Use the Table Excerpt/Table Excerpt Include macros instead of the Page Properties/Page Properties Report macros.

These macros are also provided by the Table Filter and Charts for Confluence app and they support nesting and dynamic content.

The Table Excerpt/Table Excerpt Include macros work pretty similar to the standard Page Properties: allow you to show source page meta data such as page title and collect excerpts by page labels. And you'll be also able to collect multiple-row tables as well.

And as you are using our app, note that we've recently released the Table Spreadsheet macro - please check out its documentation and get even more Excel functionality in Confluence.

[Mike Uveges]

I don't want tables as my output.  I want the user experience of the Page Properties report.  If I wanted tables, I would not have this issue to begin with.  Also, I'm not sure the table excerpt include offers the same flexibility of settings that I get with the Page Properties report.  But given that the Stiltsoft product is not compatible with the Page Properties report, I may have no other choice but to give my users data presented as a table.

[Katerina Kovriga _Stiltsoft_]

And what exactly are you collecting with the Page Properties Report? As far as I know, it's used to collect one-row (horizontal or vertical) tables into one big summary report table.

And I don't think that the Page Properties macro supports any other macros with bodies as an input.

The Table Excerpt/Table Excerpt Include macros work pretty similar to the Page Properties/Page Properties Report macros, allow you to collect multiple-row tables and text abstracts, grab other macros via the Table Excerpt (and the Table Transformer macro as well).

[Mike Uveges]

I don't know why anyone would expect the "properties" of a page to span multiple rows in a table.  My collection of pages has a one-row table that is populated with the "properties" associated with that page.  I want to create a page that contains a listing of pages and their associated properties.  This is exactly what the page properties report was created to do.

In my use case, I was trying to create a positive user experience where one role enters properties it owns in to its table on the page and another role enters the properties it owns in to its table.  Then I use table transformer (or table excerpt include) to join the two tables into a single, one-row  (or in my case, one-column since I am using a vertical orientation) table that I wrap with the page properties macro.

Seemed like a simple thing to do, and it was until I got to the Page Properties part.  Now my one hour template creation task has turned into a multi-day task.  In the end, I will compromise and live with an ugly table on my report page.  But I should not have to.

[Katerina Kovriga _Stiltsoft_]

I see now, but unfortunately we can't influence on the standard macros. 

I mean that we maintain compliance with the output of the standard macros (Page Properties Report, Content Report Table, etc.) and support all the possible variants of nesting between our own macros, but I'm afraid we can do nothing with the compliance with the input of the Atlassian macros.