Simple Tables + Page Properties at scale (2,000+ pages) — does it work with Communardo Metadata?

Daniel Whitmore_vip9qh

We’re using the latest Simple Tables capability to consolidate Page Properties from 2,000+ pages using the Simple Table macro—so we no longer rely on the Page Properties Report, yet we still get sorting, grouping, search, renaming, and exports directly on the roll-up.

In the past we used the Table Filter macro and weren’t planning to change, but after a partner demo we switched. We’re thrilled—plus it runs on Atlassian Forge (no data egress) and, for our use case, it’s free.

My question is: Our company relies on Communardo Metadata to keep taxonomy consistent across many editors. Does Simple Tables read/resolve Communardo Metadata values embedded in Page Properties, so we can group/filter by those fields in the consolidated table? If yes, what’s the recommended setup (field mapping, column config, scale tips for 2k+ pages)? If not, what’s the best workaround—e.g., ensuring metadata is rendered into the Page Properties table so the Simple Table macro can wrap it, or exporting metadata to CSV and importing it into Simple Tables?

Thanks,
D.

Mia Tamm _Simpleasyty_

Hi @Daniel Whitmore 

Thanks for the thoughtful question and for sharing your setup.

First, @Bill Sheboy is absolutely right: the best place for product-specific help is each vendor’s support channel. For Simple Tables you can contact us directly.

About your question: we’re actively working on a native integration with Communardo Metadata. The goal is that metadata values Communardo renders in Page Properties can be read by Simple Tables via our Page Properties integration—so you can use those fields in your consolidated table (group, filter, sort, export) just as you described. We’re collaborating closely with the Communardo team to make sure the integration adds real value and that Simple Tables can recognize which metadata sets/fields are in use.

Hope this helps!

— Mia Tamm