Documentation · Version 2.1.0 · Confluence Cloud
Wrap the macro around a table you already have, and it gains a search box, per-column filters, sorting and per-column totals. Nothing is imported and nothing is copied — the table stays in your page, exactly where you wrote it.
Exakind Tables is a Confluence Cloud macro. It reads the table inside its own macro body and draws the controls that table is missing. It is not a spreadsheet and not a database view: there is no cell editing, no formula engine and no pivot tables. It reads your table; it never writes to it.
Edit the page, open the macro picker and choose Tables — Filter, Sort & Search. The macro appears with an empty body. Put a table in that body — paste one from a spreadsheet, build one with Confluence's own table tools, or drag a table you already have on the page into it.
Publish the page. The controls appear above the table, and the search box is on screen and empty when the page loads.
Type in it and the table narrows as you type, matching across every column at once. The row count beside it updates to show how many rows are still showing.
Clear all appears as soon as anything is set. It resets the search, the column filters and the sort — see section 07 for the one thing it deliberately leaves alone.
Open the column filters and each column gets the control that suits the values in it:
Filters combine: set several and a row must satisfy all of them. The search box applies on top of whatever the filters have already narrowed.
Click a column to sort by it, again to reverse, and again to return to the table's own
order. Numbers sort as numbers and dates as dates — 1.234,56 is not sorted as
text that happens to begin with a one.
Merged cells do not stop it. A table with merged cells in the header or in the body still sorts and still filters; the columns still resolve and the order still holds. When the app finds merged cells it says so beneath the table: “This table has merged cells. Sorting and filtering still apply.”
Every column read as a number gets a Sum and an Average, shown as two rows at the foot of the table, under the columns they total and set flush right so the decimal separators line up. They are calculated over the rows still showing — narrow the table and they narrow with it.
A value the number format cannot read is left out of the total, and the app says so rather than quietly summing around it. A line such as “Qty: 57 of 60 values” means three cells in that column could not be read as numbers.
Totals are printed in the table's own detected format, so a table written as
1.234,56 is totalled as 62.424,90, not 62,424.90.
Three things are inferred from your table rather than configured by you, and each one is named in the interface with an override sitting beside it:
The app works out how your numbers and dates are written by looking at the values
themselves. A column containing 1.001,37 can only be read one way, and that
evidence settles the whole table. The app names the value that settled it.
There are three formats it can tell apart:
1,234.56 · 12/31/20261,234.56 · 31/12/20261.234,56 · 31/12/2026Your table lives in the Confluence page itself, not inside this app, so it is never held hostage. After uninstalling, the page shows an extension error where the macro was until an editor opens it. Two recovery routes, both verified before release:
The app declares an empty permission list, stores nothing and makes no outbound network calls. Your table arrives in the macro's own extension context, is read in memory, and nothing is kept. How that is built and enforced is set out in the privacy policy.
Questions, problems and a table that reads wrong are all welcome at support@exakind.com. A table that the app reads incorrectly is the most useful thing you can send: it usually means one of the three inferences in section 07 met a case worth handling.