Mia Tamm _Simpleasyty_ Atlassian Partner

Hi @Maria Mas , thanks for spelling out the issues you ran into. If you’re still exploring alternatives, I’m with Simpleasyty and we’re currently testing Simple DB for Confluence in a private beta with one of our customers. With Simple DB, you can manage structured records through forms and embed database views directly on…

Hi @Justine Lions, I can see why this is frustrating, especially when the results need to sit alongside explanatory content and look professional enough to share. Which replacement did Rovo suggest? It would help to know whether the extra space comes from the table itself or the container around it. On your security…

Hi @Teresa Felder, That's great news! I'm really glad you found the solution. And thank you for coming back to share what was causing the issue. It's such a small configuration detail, but it can make a huge difference! I also really appreciate that you took the time to share your feedback with the me. Hopefully, that will…

Hi @Teresa J Felder, Thanks for explaining your setup in more detail! That makes perfect sense, especially in larger organizations where introducing new Marketplace apps isn't always straightforward. I can see why this is frustrating. You're trying to solve a relatively simple problem, but the combination of Table Excerpt…

Thanks, @Nicolás De León (Vortex Labs)! These are two really valuable clarifications, especially the distinction between data residency and where processing actually takes place. I also think your point about independently verifiable information is particularly important. For enterprise customers, being able to confirm…

Thanks @Trending Games

Thanks for the clarification, @Erik Johansen and I want to correct something from my earlier reply so the thread is accurate for anyone finding it later. Simple Tables does support joining tables using a common field such as Supplier ID, but today the source tables need to be available on the same Confluence page. Your use…

Hi @Matt Lightbourn, I just read your follow-up about Marketplace pricing and the need to relate records across tables. That adds some important context to your original question. I'm part of the team behind Simpleasyty, and we're currently working on Simple DB for Confluence, focused on managing structured data directly…

Hi @Paul ROUVELLOU, This is an interesting use case because there's an important difference between detecting duplicate values and actually preventing them from being saved. For collaborative data, I think the second approach is particularly important, especially when multiple people are editing records simultaneously. A…

Hi @William Rudy, One other option came to mind that might be closer to what you're looking for, especially if you prefer the simplicity of the original Page Properties approach rather than managing metadata schemas. You could keep things quite simple with Simple Tables for Confluence: On each page, add a Page Properties…

Thanks for clarifying, @William Rudy! Just to make sure I understand, are you looking for the exact same experience as the original Page Properties macro, including the ability to edit a simple key-value table directly on the page? I ask because there are a few differences between that approach and schema-based metadata,…

Hi @William Rudy, I think I understand what you mean, especially your point that Content Properties isn't the same thing as the Page Properties workflow you're looking for. If your goal is to attach structured fields to individual Confluence pages and then report on that metadata across multiple pages, we've actually been…

Hi @Erik Johansen, I'd actually keep those tables separate, especially since different teams are responsible for maintaining them. The key is having a common field, like your Supplier ID, that allows you to bring the information together without manually duplicating it. I'm part of the team behind Simple Tables for…

Great perspective, @Anna Mitina (Stiltsoft)! I completely agree that exporting data to Excel shouldn't always be the default approach when working with Confluence. I'd add one more dimension to this: it's not just about viewing or filtering tables, but about what you can actually do with the data without leaving…

Really useful breakdown, @Anna Mitina (Stiltsoft), especially the point about keeping the summary close to the source data instead of going back and forth with Excel. Another approach we've been exploring with Simple Tables is keeping more of this workflow within the table itself: filtering/grouping the source data and…

Hi @Jesus Nieto, Thanks for the thoughtful questions! These are exactly the kinds of concerns we believe organizations should evaluate before migrating metadata at scale. Let me address both points. On product maturity and enterprise readiness Simple Metadata is already available in production on the Atlassian Marketplace.…

Hello @Jesus Nieto, really interesting discussion here, especially the points about consistency and version history. I'm Mia, part of the team behind Simple Metadata for Confluence, and these are exactly some of the challenges we've been working on. One thing we've noticed is that Page Properties can work well for smaller…

Thanks @Ben Costello! That's really interesting, especially the idea of using Classify to turn AI-generated output into controlled values. I'm part of the team behind Simple Metadata for Confluence, where we're working on structured metadata, reusable schemas and reporting across pages. I can see some interesting…

Very interesting to see classification becoming a structured output rather than just another AI-generated text response. One Confluence use case I'd be particularly interested in is classifying documentation against predefined metadata schemas. For example, assigning a document type, business classification or review…

This is an interesting direction, especially for reports and dashboards that need to remain accessible beyond the original AI conversation. One question around permissions: if an agent generates an artifact using information from restricted Confluence pages or Jira issues, does the artifact inherit any of those access…

I really like the point about content gardening that @Evelin Bayer - codefortynine mentioned . I'm Mia, part of the team behind Simple Metadata for Confluence, and this is actually one of the challenges we've been focusing on. As Confluence grows, keeping track of who owns a page, when it was last reviewed, or whether the…

Hi @Anna Wilson one thing I’d add to the great workflow ideas already shared here is the structure behind the workflow. Once you have hundreds of pages, the hard part isn’t only sending reminders — it’s making sure every page uses the same fields, the same names and the same meaning for things like Owner, Review Date and…

Hi @Mark Pliacnik, I checked this properly now. Incognito is not just a visual hiding option. When a column is marked as Incognito, its values are not available for reuse in calculated columns, derived tables or reports either. So using that table as a source elsewhere does not expose the protected field again. That was…

Hey @Scha Rowo vave you considered whether you actually need a Confluence Database for this use case? Mia here from Simpleasyty. Depending on how you manage the information, there are two approaches worth considering. If your main goal is to present tabular data with configurable columns and views, Simple Tables might be a…

Hi @Teresa J Felder , Quick update on this. The functionality we mentioned above is now live in production in the latest version of Simple Tables for Confluence. You can now automatically hide columns where all values are empty, which should make those large pivot tables much easier to work with without having to manually…

Hi @Teresa J Felder, This is a really interesting use case, especially when dealing with 60+ date columns in a pivot table! We're actually working on this exact functionality in Simple Tables for Confluence, and the good news is that we've already implemented it. We're planning to release it to production later this week.…

Thanks for putting this together, @James Allen! The Cloud Governance Best Practices session looks particularly interesting. As more organizations move from Data Center to Cloud, I think information governance and keeping content structured and manageable at scale is becoming a much bigger part of the conversation.…

I like the idea, although I'd be careful with reducing it to a single 0–100 score. “Health” is really several different things: complexity, freshness, maintainability and governance. A 20,000-word runbook can be perfectly healthy, while a 500-word policy with no owner, no review date and stale links may not be. I'd rather…

Hey @Manas Shukla one modelling detail worth calling out here: once the Assets join becomes one-to-many, Count(work item key) and Count distinct(work item key) answer two different questions. The first counts relationships; the second counts actual work items. Does the custom metric builder currently support distinct…

Hi @Tina-Louise Allaire, just curious, what are you trying to achieve by putting the table inside the Expand? Is it mainly to keep the page compact / hide the table until it’s needed, or is there another reason? There might be another way to achieve the same result in the new editor. Thanks