EAP Release of Table Extensibility

:new: Update: You might noticed some changes in your Editor experience. Table Extensibility has been fully rolled out now to all production users. Please continue to let me know if you’d like to join the EAP group where you can discuss with other partners who are also implementing solutions with Table Extensibility.

Hello Developer Community :wave:

We are pleased to announce the release of Table Extensibility through an Early Access Program (EAP). This feature brings data referentiality to Confluence Cloud in the Fabric Editor, and will open up new possibilities for using data on pages. It refines the Referentiality feature using the Contextual Toolbar and updates it with a new Connected Data Panel, that showcases a macro’s data chain.

What does it do?

Table Extensibility allows a data macro node to act as the source of another node. Confluence Cloud users can then create transformer macros, such as pivot tables, or build visual charts that reference the data in a source table. Additionally, users can chain multiple macros together to create a more complex relationship between multiple sets of data. This allows realtime viewing of the visualization as the data changes.

Using the Connect Data toolbar item available in supported Connect macros, users can open the Connected Data Panel. In the panel, users will be able view and configure connections and create macro data chains on a page.

Currently three types of data chains are supported:

  1. Native Table to Connect Macro
  2. Connect Macro to Native Chart
  3. Connect Macro to Connect Macro

Try it out

There are a few actions you need to take before you get started on your own app. Check out our initial release and make sure you’re part of the EAP. You can take a look at the demo app that showcases the above data flow our team created on Bitbucket.

There’s added setup instructions within the README to help set up the app in your tenant with accompanying GIFs: Table → Connect Macro → Chart data flow chain

And for macros with bodied content, ensure that your bodied macro is able to parse cxhtml containing fragment mark elements. We’ve seen cases where older parsers are unable to parse this cxhtml.

Interested in joining the EAP?

Table Extensibility is available thru this EAP today. This program gives you a chance to try our new Table Extensibility feature to unblock your Connect macros and access to table data in ADF or JSON format to build extensible solutions. You’ll also be providing us critical feedback that will help us to help you migrate your Connect app.

Access to this EAP is controlled via a feature flag that is set per tenant. If you would like to try out this feature, please reply to this topic with the name of your site where you would like the feature to be enabled.

If you do not wish to share your site name in a public forum, you may also message it to me privately here on the Atlassian Developer Community and I’ll add you to the EAP group.

EAP participants will be added to a private category on the developer community, which is the primary channel for feedback from EAP participants.

By signing up for this Early Access Program (EAP), you acknowledge the Atlassian Privacy Policy and that use of the EAP products is governed by the Atlassian Cloud Terms of Service (“TOS”). The EAP products are considered “Beta Versions”, as set forth in Section 14 of the TOS and are subject to applicable terms, conditions, and disclaimers.

Let us know what you think!

We’d like to hear your initial feedback both on the apps we’ve created and your own use of Table Extensibility. EAP participants will be added to a private category on the developer community, which will be the primary channel for feedback from EAP participants. Let us know what you’d like to build and any issues you have working with this new feature. We’re excited to see what solutions you can create to develop Connect apps that can reference to a table to display data in meaningful ways.


:wave: @GTD sign me up for the private category please. My site already has this enabled.

Hi @GTD, could you please clarify whether/why this EAP seemingly lacks Forge support? I might be misreading the context of this EAP, but the initial release you cross-referenced at least supported Forge as a target for Native and Connect macros.

I’ve actually been hoping that the EAP would add a ‘Forge to …’ row to the ‘Referentiality Connection type Matrix’, indicating Forge can be a source macro as well, rather than seemingly dropping Forge support altogether?


Hi @sopel , That’s a good question. This Connect solution was provided to unblock migrations from server, and to address one of the main feedbacks we have heard in our initial release: the visibility of the macro chain. Forge as a Target, as you rightly mentioned, was possible in the initial release; and as such we’re prioritizing this and the different issues and feature request for our solution. With that said, one of the main goals of this EAP was to get vendor feedback. If you’d like, I can add you to the EAP group where you can describe your use case for Forge.

@GTD can you sign me up for the EAP? Thanks.

Thanks @GTD, please add me to the EAP as well.

Admittedly I had to step back from this topic, because the ask to justify my use case for Forge made me angry:

  1. Atlassian recently introduced Table Visualization as yet another (great and well received) platform feature that should ideally have an SPI for partners.
  2. In your initial release post, you indeed emphasized the use cases that it would be “nice if your macro can extend this commonly used [Chart] macro”, and vice versa if a macro could visualize a table data source and thus complement Atlassian’s own offering.

In other words, I expected table extensibility to provide a decent enough solution for 1 so that partners can provide alternatives to Atlassian’s own solutions as per 2 - great in theory.

I’m now learning that even though Forge keeps being promoted as the future platform while continuing to lack parity with important existing Connect features, it doesn’t even get access to new platform features, where it should be much simpler to cater for both out of the gate. That’s very disappointing and concerning, to say the least.

Happy to elaborate on our resp. use cases in the EAP group.

1 Like

Added, please check your inbox for the invite.

Hi @sopel , added you to the EAP group as well.

I apologize for the confusing experience with the different platform features, we are doing our best to build features that cater to our ecosystem partners and end users. Please share and elaborate on your use case within the group and we can look into how our team can help. And thanks for your patience as we navigate thru this transition period.

Thanks @GTD, I didn’t realize that table extensibility has already moved to GA a few days ago with great fanfare, so I’d rather discuss this here than in a non-public and semantically already closed EAP group.

Before I dive into your value proposition and our use cases, may I ask for a clarification on your respective roadmap? When you say you are “prioritizing [Forge support] and the different issues and feature request for our solution” while navigating through “this transition period”, does this signal that you will deliver Forge support in due course (i.e. after catering for your top priority Connect migrations), or conversely that Forge support may even never materialize?

Hi @sopel,

While I cannot guarantee what makes the prioritization cut and promise delivery of Table Extensibility Forge support, I can say that we have previously allowed for Forge support via the toolbar in our previous release, and that there was more interest in the Connect solution than Forge, and we are strategically addressing the issues as they come. And hence the EAP and request for feedback from partners like yourself who are looking to incorporate TE.

It’s a balancing act for the CC Ecosystem team to build solutions that cater to all our stakeholders, including ecosystem partners, end users and migrating customers. And as stated publicly in the news, Atlassian’s key focus area is on cloud migrations, and our Ecosystem team is focused on working towards that goal.

Thanks for your patience as we continue extending the functionality of Table Extensibility.

@GTD I’m looking for documentation for the relevant APIs and failing. Is this documented at all besides the linked example repos?

Also: in the table referentiality repo, the old referentiality repo is linked. Will that one still work or has it been replaced by this new feature?

1 Like

Awesome feature for Confluence. I’m not exaggerating when I say this is one of the most interesting and useful features I’ve seen in a very long time.

I would like to point out that making Connect support a priority over Forge support strengthens the case for using Connect to develop a new app and at the same time weakens the case for using Forge at all. I feel like this sends a mixed message on the platform strategy. The current fragmentation is incredibly frustrating. Connect is so much stronger as a platform. Forge seems anemic. Decisions like this seem to diminish Forge even more.


I’d like to be in as well. :wave:

Hi @jasonboileau , Yes, both the new repo in Bitbucket , with the new Connect app, and the previous repo in Bitbucket will work . In addition to this blog post and the previous blog post on this topic, you can also find the dynamic content macros documentation here https://developer.atlassian.com/cloud/confluence/modules/dynamic-content-macro/

That’s great to hear! I’ve added you again with the new email address to the group. Table Extensibility has been fully rolled out now to all production users, it might be a good forum to discuss with other partners who are also implementing solutions with it.

:new: Wanted to provide an update to the group. You might noticed some changes in your Editor experience. Table Extensibility has been fully rolled out now to all production users. Please continue to let me know if you’d like to join the EAP group where you can discuss with other partners who are also implementing solutions with Table Extensibility.

@GTD This is awesome to hear.

Is it truly rolled out completely?

My main documentation site isn’t picking up the change and refuses to display the “Manage connected data” icon:

Screenshot 2023-05-22 at 15.43.38

I’ve uninstalled and reinstalled the app.

@GTD Scrub that. Clear browser cache does the job :woman_facepalming:


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.