> 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/2.12.md).

# 2.12

This release delivers a rebuilt Tableau connector with full multi-host and multi-site support, expanded asset mapping workflows in User Directory for Power BI and Tableau, and significant improvements to BI360 department-level reporting. This release also broadens Power BI inventory with capacity, domain, gateway, and usage analytics, extends Sigma with lineage, and includes performance improvements across alerts, monitoring, and BI Similarity.

## What's New

* **Tableau Multi-Site Support**: You can now connect multiple Tableau hosts and sites within a single connector setup. Site discovery, per-site authentication, and per-site management are all handled from one place and if a sync partially fails, you'll see exactly which site had the issue and where it came from.
* **Asset Mapping for Power BI and Tableau**: Administrators can now upload a mapping file to associate Power BI and Tableau assets with departments or custom groups. Once uploaded, Datalogz handles the sync automatically, and you can track status, re-sync on demand, or update the file at any time.
* **BI360 Department Health**: BI360 now shows health snapshots for each department, including which are most active and which are at risk. You can drill into department ownership across all your BI tools, including Tableau, and see adoption broken down by connector.
* **Power BI Capacities**: A new Capacities tab in Power BI inventory shows how workspaces, reports, and semantic models are distributed across your capacity. Datasource cards now include connection details and gateway health so you can quickly spot configuration issues.
* **Sigma Lineage**: Lineage is now available for Sigma, covering workbooks, reports, and data models, including connections back to underlying data sources.

## Enhancements

* **Tableau Inventory**: Tableau assets now show host, site, and owner information, making it easier to understand where assets live in large multi-site environments. Dashboards, worksheets, and stories appear as distinct asset types, and team scoping can now filter by host and site.
* **BI360**: The global inventory now includes Pillars, and Cost Management links have been updated to reflect pillar-based alerting. BI360 views are better scoped to the connectors your organization actually uses.
* **Power BI Domains and Usage**: Workspace domain information is now surfaced in inventory with filtering support. Report usage analytics are available so you can see which reports are being used and by whom.
* **Sigma**: Personal document display and naming have been improved for a cleaner inventory experience.

## Platform Stability & Performance

* Alert and monitor breakdowns load faster thanks to smarter caching. Caches update automatically when you change monitor settings or workflows, so you're always seeing current data.
* BI Similarity graphs render more reliably and cancel cleanly when navigating away.

## Bug Fixes

* Fixed a Power BI issue with domain parsing that affected workspace filtering.
* Fixed pagination in Sigma workspace and member lists.


---

# 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/2.12.md?ask=<question>&goal=<endgoal>
```

`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.