> 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/archive/2.9.md). # 2.9 ## What's new ### BI 360 We are excited to introduce [**BI 360**](/guides/bi-360.md), a revamped executive dashboard that delivers a complete 360 degree view of BI usage, adoption, and licensing across your organization. BI 360 brings together insights that were previously fragmented into one streamlined, executive ready experience. BI 360 offers the following featues: #### **Cross Tool Insights** * Compare key asset layers across BI tools to understand where you have the most assets. * Instant visibility into BI health at the tenant or server level #### **Global BI Inventory** * Centralized inventory of BI assets across connected tools * Browse and search reports, dashboards, datasets, and folders from one place * Foundation for deduplication and cleanup initiatives ### Inventory: Workspaces & Visibility * Power BI Inventory now includes Workspace-level insights with: * Workspace details * Refresh heatmap * Improved filtering reliability across inventory views. * Filter unhealthy assets by alert category. ## Fixes * Inventory filter issues resolved. * Global Inventory search now refreshes correctly after clearing search terms. * Fixed inconsistencies in alert visibility across the platform. * Improved handling of inactive Power BI reports in edge cases. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.datalogz.io/guides/release-notes/archive/2.9.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.