Changelog

Every release of TrailsBI, newest first. The current version is 1.6.0, released 13 November 2026. Update with:

pip install -U trailsbi

  • --split writes one page per semantic model, with every report that uses it, into one folder, so each model's owner gets a page of their own. Reports on models the folders don't hold get a page per published model. It works with several workspaces and with --model, --report, --workspace and --include.

  • updated detail panel for workspace view
  • Multiple workspaces Give TrailsBI more than one workspaces folders, and it builds one report covering everything from all workspaces.
  • Cards, the details pane and --list show each item's workspace.
  • Scope groups models and reports by workspace, with an option to pick a whole workspace.
  • -w/--workspace NAME builds the reports and models of one workspace.

  • Workspace lineage. Point TrailsBI at a folder with several reports and semantic models, such as the Git folder a Power BI or Fabric workspace syncs to, and it builds one report for all of them.
  • Scope in the toolbar picks the semantic models and reports that the lineage, the model, the report pages and the findings show.
  • Build part of a folder with --model, --report, --with-reports or --include; names may be display names or paths and may use wildcards. --list shows what the folder holds.

  • Graph view. Lineage has a new Map | Graph switch. Graph shows the same items and links as a circular graph.
    • Uses the map's type filters, view options, search and selection, and the details pane; an item selected in one view stays selected in the other.
  • Report measures. A report connected live to a semantic model can add measures of its own. TrailsBI now shows them in the lineage as report measures, apart from the model's measures.

  • Function help in code. Point at a DAX or Power Query function in any code block to see its syntax and what it does, with a link to its page on Microsoft Learn.
  • Dark theme. The page follows the system's light or dark setting. The new button in the header switches between them, and the page remembers your choice.

  • --embed writes the TrailsBI table with just one column, Chunk. A TrailsBI table or page from an earlier --embed is switched over when you run it again.
  • --embed adds the TrailsBI visual 1.0.1: one field, Power BI's right-click menu, and a copy button on code.
  • The HTML report: every DAX and M code block has a copy button at its top right when the pointer is over it.

  • --embed adds the TrailsBI visual 1.0.0

  • --embed now also adds a TrailsBI page to the report, hidden in view mode, with the TrailsBI visual on it and its fields already set. The visual (0.9.2) ships with trailsbi and is saved inside the report the way Power BI Desktop saves a visual imported from a file, so there is nothing to import or drag. Running it again keeps the page as you left it and updates the visual. PBIR reports only: for an older report, --embed writes the table and says why it left the page out.

  • Recognises the TrailsBI visual's new, shorter ID (from visual 0.9.1) as well as the old one, and leaves both out of the analysis. Without it, the visual's Part and Chunk fields show in Health as fields missing from the model.
  • --embed: the TrailsBI visual could fail with "Cannot read properties of undefined (reading 'push')" on larger models. Power BI trims trailing spaces when it loads text, and a part that ended with a space inside a name lost it. Parts now never start or end with whitespace. Run --embed again and refresh.

  • --embed writes the page data into the project's semantic model as a hidden TrailsBI table (TMDL or model.bim), for the TrailsBI visual to show the report inside Power BI. Running it again replaces the table. Without -o or --open, no HTML page is written.
  • The TrailsBI table and the TrailsBI visual are left out of the analysis.

  • Install with uv as well as pip: uv tool install trailsbi
  • Help for Windows when pip installs the trailsbi command outside PATH (Microsoft Store or install manager Python): add the Scripts folder to your user PATH once. Guide at https://trailsbi.com/setup/

First public release.

  • One offline HTML page per Power BI project (PBIP), with five views:
    • Lineage: column- and measure-level lineage from data sources through tables, columns and measures to visuals and pages. Upstream draws in navy, downstream in teal; compact and detailed cards; fit to screen
    • Model: every table, column, measure and relationship with DAX and Power Query, and a relationship diagram with automatic layout. Export as PNG or SVG, with names hidden if you like
    • Reports: each page drawn as a canvas preview, with filters at page, report and visual level, and the fields every visual uses by role. Show in lineage and Show in Model from any field
    • Health: Microsoft's Best Practice Analyzer rules evaluated from the model files, plus lineage checks such as unused columns and measures and report fields missing from the model
    • AI Readiness: how well Copilot and data agents will understand the model, as a score with the findings behind it
  • Reads TMDL and model.bim models, PBIR and legacy report.json reports, and reports live-connected to a published semantic model
  • trailsbi with no argument builds the project in the current folder; -o takes a file or a folder; --open opens the page when it is ready
  • The page is saved as "TrailsBI Report - <project> - <date time>.html"
  • The same project gives the same page on every run
  • Python 3.9 or later, no dependencies. pip install trailsbi, or the single-file trailsbi.pyz from the release page
  • Runs entirely on your machine: reads metadata files only, makes no network calls, sends no telemetry and never writes to your project

The full history, with links to each release's downloads and checksums, is on GitHub releases.