> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.md).

# Power BI Metadata Extracted

### What does Secoda extract from PowerBI?

* Groups
  * Name
* Reports
  * Name
  * Description
  * Owners
  * Usage (Number of views in PowerBI)
  * URL
  * Tags
  * Preview
* Tiles
  * Name
  * Description
  * Owners
  * URL
  * Tags
* Pages
  * Name
  * Tags
* Datasets
  * Name
* Tables
  * Name
  * Tags
* Measures
  * Name
* Dashboards
  * Name
  * Description
  * Owners
  * URL
  * Tags
  * Preview
* DAX
* Dataflows
  * Name
  * Description
  * Owner

{% hint style="info" %}
You must fully enable metadata scanning in order for DAX expressions to be returned. For more information, see [Enable tenant settings for metadata scanning](https://learn.microsoft.com/en-us/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning).
{% endhint %}

* Pages (Pages are referred to as Charts in Secoda)
  * Page Name
* Lineage
  * PowerBI Table <-> PowerBI Report
  * PowerBI Tile <-> PowerBI Dashboard
  * PowerBI Tile <-> PowerBI Report

{% hint style="info" %}
To determine lineage from PowerBI, we use the relationships and dependencies provided from the PowerBI APIs. If using Non Admin APIs we will not be able to show lineage to other resources (ex Snowflake tables), but lineage within PowerBI will be visible.
{% endhint %}


---

# 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.secoda.co/integrations/data-visualization-tools/power-bi/metadata-extracted.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.