EAP Release of 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

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.