> 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.10.0.md). # 2026.10.0 Release date: October 14, 2026 This release is about going deeper on every platform you connect. Databricks gains a Users tab, workspace access and lineage, BI Similarity now covers Sigma workbooks and data models, and Power BI dataflows appear in lineage. Semantic Intelligence also reaches the MCP server, so AI agents can ask what a measure means and who computes it differently. This release helps your teams to: * See who can reach each Databricks workspace and how data moves through Unity Catalog * Find rebuilt Sigma workbooks and data models next to the rest of their duplicates * Trace Power BI reports back through the dataflows that feed them ### **What’s New** #### **Databricks: users, access and lineage** Databricks inventory now shows who has access and how data moves, not only what exists. * A **Users** tab for Unity Catalog principals, with removed principals hidden * An **Access** column on workspaces, and only the Genie workspaces Datalogz can reach are listed * Lineage captured as connections between assets, with first seen and last seen dates * Choose your Databricks cloud during connector setup, so workspace links open in the right place **Result:** Who can reach a workspace, and what depends on a table, are answered from the same inventory. #### **BI Similarity for Sigma** Sigma joins Power BI, Tableau and SharePoint in BI Similarity. * Workbook to workbook comparison * Data model similarity **Result:** A Sigma workbook rebuilt from another one shows up in the same place as every other duplicate. #### **Power BI dataflow lineage** * Dataflows now appear in inventory and in lineage **Result:** You can follow a report back through the dataflows that feed it, instead of stopping at the semantic model. ### **In Preview** #### **Semantic Intelligence (available on request)** Available to customers on request while we finish the experience. * Users with access to a connector can now open Semantic Intelligence; the Exclusions tab stays limited to connector managers * The MCP server can now answer definition questions: what a measure means, where it is defined, which teams compute it differently, and its lineage * Semantic Intelligence tabs now match the layout of Inventory ### **Enhancements** * **Unsaved changes:** leaving a page with unsaved edits now asks first and offers to save * **Consistent navigation:** detail pages share one back link and the same margins * **Top Team Reports:** the Inventory Summary panel has a chart view * **Tableau Webpage URL:** workbook and datasource side panels link straight to the asset in Tableau * **Power BI Inventory:** the full gateway ID is shown with a copy button, plus accessibility and wording fixes from a UI review ### **Platform Stability & Performance** * Power BI processing on large tenants is faster and more reliable, after a sweep of query plans, timeouts and indexes * Databricks syncs stop early with a clear error when credentials expire, and keep retrying temporary errors * Sigma extraction handles very large workbooks without running out of memory and respects Sigma’s rate limits * Tableau managed and Edge connectors now share one processing path, and reprocessing a snapshot is safe ### **Bug Fixes** * **Tableau:** embedded lineage and upstream table details were missing for some datasources, and content usage was incomplete on large sites * **Tableau:** some published datasources were classified incorrectly * **Alerts:** the active alert count could differ from the alerts in the list * **Refresh Heatmap:** schedules set in some Windows time zones appeared at the wrong hour * **Databricks:** workspace links assumed AWS for accounts on other clouds * **Teams:** a saved team description did not appear on the team details page * **Inventory:** datasource card tooltips opened behind the side panel --- # 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.10.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.