You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, I have been working on an API catalogue of sorts.
Initially just using a page properties report, but then adding filtering
Worked really well and looked good.
I then wanted to pull in lifecycle info from Jira into the same table , so created a Jira issues table and using table transformer to merge the tables got what I wanted.
Unfortunately there was one slight issue, the Description Column was pulling through the expand macro
that contained the description text (some descriptions were quite lengthy so needed to make the layout concise in the table view) and the expand macro no longer opens to display the description.
The query used is
T2.'Consumer Contract With',
T2.'WS Communication Protocol',
ON T1.'Summary' = T2.'URI'
Is this a limitation I have hit? or is there anything that can be done to perform the table merge between the page properties report and the Jira Issues table without losing the Expand macro functionality containing the description (the descriptions are too large to just put as free text, as it messes up the layout of the table)
Hi @Craig.Harley ,
The issue seems to be in Cloud Confluence itself: as I see, your tags point to Cloud and you use the Table Toolbox macro to nest macros.
In comparison with Server/Data Center, Confluence Cloud doesn't allow to nest macros. You can't wrap macros directly one into another.
That's why the Table Toolbox macro was designed, otherwise you won't be able to create macro sequences at all.
So, seems that's the reason why your Expand macro breaks.
so let me just summarise what you are saying here for my understanding
Each of my page properties uses the expand macro as well as Jira, Status and Date
This all gets pulled into a page properties report and then into a Table Toolbox, Table Filter everything works without issue
However, if i do exactly the same with page properties, join a Jira Issues table to it using Table Toolbox, Table Transformer and then embed this within Table Filter, only the expand macro stops working and this is due to using Confluence Cloud and it not allowing the nesting of Macro's?
If this is correct, do I need to take this up with Atlassian?
Yes, you got it correct. You may raise a support ticket with us and attach the page storage format (upper right corner -> menu ... -> View storage format) of the master page and the page with your Page Properties macro, we'll try to look into the macro conflict.
Hi @Craig.Harley ,
Meanwhile, I've tried to reproduce the issue: I've collected my Page Properties Report macro (had two Page Properties that contained Expand macros and Jira Issue macros as a single issue) and inserted the Jira macro in a tabular view.
Then I wrapped these two macros in the Table Toolbox macro and wrapped them into the Table Transformer macro for joining and then in the Table Filter macro for filtering.
The Expands are always opening for me.
So, it seems that we really need your data to investigate the issue.
Please also check where Expands break for you: do they work properly if you remove the Table Filter macro and leave only the Table Transformer macro?
Please refer to our support then.
I indeed have the similar query inside my Table Transformer macro:
FROM T1 JOIN T2 ON T1.'Key' = T2.'ID'
And for me the Expand macro opens just right: