Power BI Documentation

Document Power BI reports and data models so they stay traceable

MetricsMap imports existing model metadata from .bim files and connects tables, relationships and DAX measures to a shared KPI glossary.

See the workflow

Traceable metadata

Definition

What does the entry mean?

Ownership

Who reviews and decides?

Technical trail

Which sources belong to it?

Current product scope: Today MetricsMap imports metadata from .bim files. .pbix files are not parsed; .pbip/TMDL is planned as the next import path. No raw data is ever stored.

The starting point

Why scattered documentation is not enough

Logic is trapped in the model

DAX measures and relationships exist technically, but their business meaning is barely discoverable outside the file itself.

Reports are explained in isolation

Documentation describes individual pages or visuals without surfacing the reused measures and data models behind them.

Manual re-entry costs time

Copying tables, columns, relationships and measures into a wiki again quickly creates outdated, duplicated maintenance.

The approach

From a single entry to documentation you can rely on

01
Import .bim metadata
Bring in tables, columns, relationships and DAX measures from the model, without transferring any raw business data.
02
Give measures business context
Add plain-language KPI definitions, owners, status and synonyms to the technical expressions that already exist.
03
Connect models and KPIs
Map source tables and dependencies so users can navigate from a metric to the technical model structure behind it.
04
Close gaps deliberately
Check for missing descriptions, missing owners and unconnected tables, instead of rewriting the whole documentation.

MetricsMap

Features for a metadata foundation you can trace

.bim metadata import

Tables, columns, relationships and DAX measures are imported as documentable metadata.

Data model catalog

Tables and fields sit in one shared structure with schema, description and relationships.

KPI linking

Measures can be described in business terms and connected to other KPIs and their sources.

Metadata only

The import brings in model descriptions and logic, but no records from the Power BI model.

Example: Sales model

After the .bim import, FactSales, DimCustomer, their relationships and existing measures are visible. For Revenue, the team adds a business definition, an owner and the approval status.

Tell the terms apart

.bim: A JSON-based tabular model format whose metadata MetricsMap can currently import.
.pbix: The Power BI Desktop file, which MetricsMap does not open or analyze.
.pbip/TMDL: A text-based project and model path planned as the future primary import.

How to document Power BI reports How to document data models

Frequently asked questions

Can MetricsMap read .pbix files?

No. .pbix files are not parsed. The current import uses .bim metadata; .pbip/TMDL is planned as a further import path.

What comes out of a .bim file?

Model metadata such as tables, columns, relationships and DAX measures. Business definitions and ownership are added by the team afterwards.

Is Power BI data stored in MetricsMap?

No. MetricsMap stores only metadata and calculation logic, no rows from the model, and it runs no queries against the BI system.

Connect Power BI metadata with KPI knowledge

Import a .bim file and add the business documentation exactly where the model leaves it out.

Start your Power BI documentation