Difference between Advanced Tables for Confluence Data Center and Cloud version
Description
This page describes what you need to consider:
When migrating from Confluence Data Center (DC) to Cloud, and you are using the Advanced Tables for Confluence app on pages in your instance.
When using Advanced Tables for cloud and you are seeing some differences in behavior from the documentation.
Related article
Atlassian's Confluence migration instructions
What will be different?
The macros involved are:
The key differences in behavior are:
The Confluence Data Center and Cloud versions have different macro editor experiences. The Data Center version has a new custom macro editor, while the cloud version has the default Confluence macro editor.
The cloud version supports a new macro, the Advanced Table Viewer.
The cloud version supports all the macros available in the Data Center except the JQL Table macro
Macros render in the background in the cloud version and then appear as the data becomes available.
The performance of the macro rendering in the cloud version is mostly dependent on the performance of the user's client machine, as a majority of the processing is now done using the browser's JavaScript engine. The way the connect architecture in Confluence cloud works is that macros get loaded dynamically AFTER the page is rendered and displayed. This allows the page to be displayed to the user somewhat quicker, but then there can be a delay on each macro loading. The loading time is dependent on client JavaScript speed (some browsers may be better than others) and network connections. This is a permanent restriction of the architecture.
There may be a difference in behavior with some interactions with other page elements or macros. The Atlassian Confluence development team continues to improve the integration and interactions of macros in the connect environment.
There are some known issues and incompatibilities.
Differences between the Data Center and cloud versions
The following table lists the macros' parameters and features that work differently in the Data Center and cloud:
This table was last updated on July 21, 2025.
Parameter/Feature | Data Center | Cloud | Notes |
|---|---|---|---|
URL whitelisting | Supported natively by Confluence and configured using the Global Configuration page | Not supported | For more information, refer to CLOUD-2636. |
Plain text macros are not supported (JSON macro and CSV macro) in Cloud with the new editor experience. | Supported | Not supported | Confluence Cloud does not support this. For more information, refer to CONFCLOUD-65717. |
Inter-operability between macros | Supported | Not supported | Confluence Cloud does not support this. For more information, refer to CONFCLOUD-41551. |
Anchor macros within Advanced Tables macros | Supported | Not supported | Confluence Cloud does not support this. For more information, refer to CE-886. |
Sorting inline tasks in macros | Supported | Not supported | For more information, refer to CONF-45450. |
Preview in the macro editor | Supported | Not supported | For more information, refer to CE-13. |
Export to PDF or Word | Supported | Not supported | Due to certain technical issues, the app does not support this feature in cloud. |
Excerpt include macro in Advanced Tables macros | Supported | Not supported | Confluence Cloud does not support this. For more information, refer to CE-876. |
Jira Issue/Filter macro in Advanced Tables macros | Supported | Not supported | Due to certain technical issues, the app does not support this feature in cloud. For more information, refer to CE-1047. |
Page Properties Report macro in Advanced Tables macros | Supported | Not supported | Due to certain technical issues, the app does not support this feature in cloud. |
Using customized CSS for tables in macros | Supported | Not supported | Confluence Cloud does not support this feature. |
Please note that all the other parameters function the same in both versions of the app.
Problem reporting
If you experience any unexpected problems or behavior changes, do not hesitate to open a support ticket. This helps us identify and prioritize fixes and improvements.
Need support? Create a request with our support team.
