Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Microsoft Power BI (File) - New Beta Bridge

Bridge Specifications

Vendor Microsoft
Tool Name Power BI
Tool Version 2.x
Tool Web Site https://powerbi.microsoft.com/
Supported Methodology [Business Intelligence] Data Store (Physical Data Model, OLAP Dimensional Model), BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via PBIX File

BRIDGE INFORMATION
Import tool: Microsoft Power BI 2.x (https://powerbi.microsoft.com/)
Import interface: [Business Intelligence] Data Store (Physical Data Model, OLAP Dimensional Model), BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via PBIX File from Microsoft Power BI (File) - New Beta Bridge
Import bridge: 'MicrosoftPowerBIFile' 11.0.0

BRIDGE DOCUMENTATION
This bridge imports metadata from a Microsoft Power BI file in PBIX or PBIT format.

KNOWN LIMITATIONS

The PBIX file format usually does not expose the report Tabular Object Model (TOM) metadata definition.
As a result, the bridge cannot import some of the report metadata (e.g. calculated tables, columns, measures expressed in DAX language).

The PBIT file format usually contains the report Tabular Object Model (TOM) metadata definition, leading to more complete report lineage.
However each Table Query in PowerQuery M language is written slightly differently in PBIT format than how they appear in the PowerBI Desktop tool.

For both PBIX and PBIT file formats, the bridge relies on a PowerQuery M language parser to understand the lineage of each Table Query.
Some concepts in the PowerQuery language may not be well supported:
- not all functions are supported (data access functions, data manipulation functions)
- complex queries that rely on sub-queries, parameters, or custom/lambda functions
- queries that rely on third party scripts (R, Python languages)


Bridge Parameters

Parameter Name Description Type Values Default Scope
File Select the PowerBI file to import. FILE
*.pbix
*.pbit
  Mandatory
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -m 4G

-v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces").
-jre {path to java executable} to specify a custom Java Runtime Environment. It could be an absolute path to javaw.exe on Windows or a link/script path on Linux.
for example: -jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"
-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G).
-pc propagate columns discovered while parsing PowerQuery M script steps toward the source tables
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Mon, 23 Mar 2020 17:37:49

Copyright © Meta Integration Technology, Inc. 1997-2019 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.