# 2.11 This release expands the Datalogz control layer across more BI platforms, with a new connector, a major upgrade to BI Similarity, and richer executive and usage insights. We've expanded core parts of the platform to: * Bring a new BI tool — Sigma — into the Control Tower * Extend cross-tool similarity detection beyond Power BI * Give executives a clearer, department-aware view of BI performance * Help BI Ops teams spot unused and declining Power BI reports faster ## What's New ### Sigma Connector (Private Preview) [Sigma](/guides/organizational-setup/bi-connectors/sigma.md) is now a first-class BI platform inside Datalogz. * Sigma assets are ingested into Datalogz and mapped into the common BI metadata model * Sigma dashboards, workbooks, and datasets show up in Global Inventory alongside Power BI, Tableau, and Qlik * Foundation in place for future Sigma activity tracking, monitors, similarity, and lineage Result: Customers running Sigma can now manage it inside the same Control Tower they use for the rest of their BI environment. ### BI Similarity — Redesigned, with Tableau Support (Private Preview) The [BI Similarity](/guides/bi-similarity.md) experience has been redesigned, and now supports Tableau (preview) in addition to Power BI. * Refreshed Cluster Map and similarity views for faster duplicate exploration and consolidation decisions * A new recommendation box that helps you decide what to do with similar reports or datasets * Tableau data sources scored for similarity using the same model as Power BI * Sets the foundation for cross-platform deduplication across Power BI and Tableau Result: Faster identification and cleanup of duplicate or overlapping reports. ### BI 360 with Department-Level Insights [BI 360](/guides/bi-360.md) now gives executives a deeper, department-aware view of their BI environment. * Department-level rollups for usage, adoption, cost, and risk so leaders can see performance by team * Expanded executive visualizations and a refreshed Executive Summary * New current vs. historical toggle to compare today against past performance * Connector-level rollups to see KPIs by BI platform Result: Clearer, more accountable executive visibility; leaders can see exactly which departments and tools are driving usage, cost, and risk. ### Usage Insights for Power BI Reports Power BI reports now have richer [usage analytics](/guides/inventory/usage-analytics.md) inside Inventory. * Usage views across 30, 60, and 90-day rolling windows * Trend indicators in BI 360 showing whether usage is growing, declining, or flat * Easier identification of unused, low-value, or rapidly changing reports Result: BI Ops teams can prioritize cleanup, consolidation, and ownership decisions on Power BI reports with real evidence of how they're actually being used. ## Enhancements ### Inventory Enhancements We've continued evolving Inventory into the BI system of record. * Improved asset detail sections with a cleaner, more consistent layout * Inventory now covers Sigma assets in addition to existing platforms Result: A more complete, more usable single source of truth for BI assets across tools. ## Platform Stability & Performance Ongoing stability work to keep the platform fast and reliable as coverage expands. * Performance improvements across the platform * Reliability fixes carried in from the prior release * Code quality improvements supporting the new connector and similarity work Result: A faster, more stable platform as you scale Datalogz across more BI tools. Check out our updated docs to see Sigma setup, Tableau Similarity, and the new Power BI usage views in action. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.datalogz.io/guides/release-notes/2.11.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.