> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/release-notes/2026.09.0.md). # 2026.09.0 Release date: September 2, 2026 This release is about trusting the numbers on the page. Inventory Summary now covers Qlik Sense, Sigma and Spotfire with a Start Here view that tells you where to look first, and SharePoint workbooks are compared against other workbooks so you can see where the same report has been rebuilt in a spreadsheet. The MCP server also moves onto our semantic layer, so AI agents can ask deeper questions and follow data lineage. ### What's New #### **Inventory Summary for Qlik Sense, Sigma and Spotfire** The [summary](/guides/inventory/inventory-summary.md) experience that Power BI and Tableau already had now covers three more tools, with wording that matches each one. * A Summary tab for all three, with Asset Health and the tool's own activity measure: Active Streams for Qlik Sense, Active Workspaces for Sigma, Active Library Folders for Spotfire * A new **Start Here** section with Recently Created and Recently Updated tiles that deep-link into the exact rows they count * Favourites and Top Reports are paginated, with counts on each tab **Result:** Every card on the page is either a real number or an explicit statement that the number is not available. #### **SharePoint workbook similarity** Spreadsheets are where governed reporting goes to be quietly rebuilt. This release compares SharePoint workbooks against each other. * SharePoint workbook to workbook comparison. * Workbooks are grouped into semantic clusters and given a classification, shown in the similarity grid. * Where a workbook fits more than one class, every class is shown and the primary one is styled more strongly. **Result:** You can see which parts of your governed estate have been copied into spreadsheets, and what kind of content those spreadsheets hold. #### **MCP server: deeper questions and lineage** The [MCP server](/guides/datalogz-mcp-servers.md) now runs on the same semantic layer the product uses, rather than its own set of narrow tools. * Agents query through a single semantic query interface instead of a long list of one-purpose inventory tools. * Lineage is available through that interface, replacing the previous per-asset downstream impact tools. * The cap on how much an agent could read back in one answer has been removed, so large questions no longer return truncated results. **Result:** An agent can follow a question across assets and lineage in one pass, and its answers stay consistent with what the product shows. **Connect an AI client to the MCP server without manual setup** * The OAuth server supports Dynamic Client Registration, so a compatible AI client can register itself. * Standard OpenID configuration discovery is published, so clients can find the endpoints themselves. * Self-registered clients are listed and distinguishable from clients you created by hand. ### In Preview #### **Semantic Intelligence (available on request)** Available to customers on request while we finish the experience. * Search across semantic concepts, with matches highlighted in the results * Lineage in the metric catalogue from dataset through to the report or dashboard, with every node in the graph linked into inventory * Cross-links between Semantic Intelligence, the inventory and the metric catalogue, in both directions * Volatile and low-value measures are filtered out of scoring, which improves accuracy ### Enhancements * **CC on alert notifications:** alert emails can now copy additional recipients * **Compact summary rows:** the Summary panels use a tighter row density, consistent asset-type icons, and Start Here reads as a single section * **Simplified roles:** the role model has been consolidated. Existing access is preserved and no action is needed. End-user documentation for the new model is in progress ### **Platform Stability & Performance** * The home page no longer stalls on large tenants. Database calls in asynchronous request handlers were serialising every request through two event loops, which could push the page past 30 seconds; those calls plus an additional index have resolved it * Power BI activity extraction no longer fails on very large tenants, where a single activity file could exceed the 5 GB limit for a one-shot upload. Large files are now uploaded in parts * Power BI user records are de-duplicated correctly where activity data varies the casing of a user id, which was failing the daily activity merge * Spotfire membership filters no longer fail silently: a filter that cannot be honoured warns rather than dropping out of the query, and a metadata reflection failure leaves you with a usable view * Frontend deployments are now zero-downtime, and the production environment has completed its migration to ARM #### **Bug Fixes** * **Inventory:** the Asset Health card over-counted on Tableau and Qlik Sense teams, in some cases reporting several thousand assets against a few hundred in the list * **Inventory:** asset tab counts ignored the applied filter on every tab except Reports * **Inventory:** Start Here disappeared entirely when it had nothing to show, instead of holding its place with an empty state * **Spotfire:** inventory showed duplicate assets, because the extractor combined two source schemas and the modelling layer dropped the information needed to de-duplicate them * **Workflows:** running a workflow with no workflow selected made the run button disappear * **Saved views:** a filter cleared inside a saved view could reappear after the grid refreshed, and clearing one filter chip could discard the others --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.datalogz.io/guides/release-notes/2026.09.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.