Power BI Include/Exclude Options
The options in your IBM Manta Data Lineage Power BI connection to include or exclude give users the ability to limit the scope of workspaces and reports that will be included in the scan for lineage content. This document details the use of properties that filter reports extracted by the Power BI scanner. If you are interested in all the reports available, leave these properties blank.
Included and Excluded Reports
In each extraction mode, there are two properties that can be used to filter the reports to be extracted.
-
For Azure extraction:
-
Extracted workspace/report names (
powerbi.azure.include
) -
Excluded workspace/report names (
powerbi.azure.exclude
)
-
-
For local extraction:
-
Extracted reports (
powerbi.local.include
) -
Excluded reports (
powerbi.local.exclude
)
-
All these fields use Java regular expressions to determine whether a report or workspace is matched. By default, matching is case-sensitive
(can be changed by using case insensitive modifier (?i)
at the beginning of the regular expression) and special characters behave
differently than what might be expected (as per regular expression syntax). The following examples show how to match case-insensitively and escape special characters.
Leaving the Include field empty matches all reports. Leaving the Exclude field empty does not exclude any reports. So, the default (both properties being empty) matches all accessible reports.
The Exclude field takes higher precedence over the Include field, meaning that a report matched by both fields will be excluded.
Examples
Here are some examples of what can be entered in the Extracted Reports and Excluded Reports properties.
.*
—Matches all reports in all folders/workspaces. For Extracted Reports, this is the same as leaving the field blank.
-
Some Place/.*
—Matches all reports in theSome Place
folder/workspace. -
.*/SomeReport
—Matches all reports namedSomeReport
in any folder/workspace. -
Some Place/SomeReport
—Matches a single report namedSomeReport
in theSome Place
folder/workspace. -
Some Place/.*SomeReport
—Matches all reports with names ending inSomeReport
inSome Place
, including a report named justSomeReport
, if it exists. In local extractions, it matches any such report in the subfolders ofSome Place
as well. -
Some Place/SomeReport|Other Place/OtherReport
—Matches two reports—one namedSomeReport
and another namedOtherReport
—inSome Place
andOther Place
, respectively. -
Some Place/(SomeReport|OtherReport)
—Matches two reports—one namedSomeReport
and another namedOtherReport
—both inSome Place
. -
(?i)SOME PLace/someREPorT
—Matches in case-insensitive mode. MeaningSome Place/SomeReport
will be matched as well asSOME PLACE/SOMEREPORT
, disregarding capitalization. -
Some Place/Some\.Strange\*Report\?
—Matches a report namedSome.Strange*Report?
inSome Place
. Since the characters used are reserved for regular expressions, such characters must be prefixed with\
to indicate that the literal character is intended. Other characters that must be escaped in this manner include, but are not limited to:[
,]
,(
,)
,+
,|
,$
,^
, and\
itself, which must become\\
.
The Difference between Azure and Local Extraction Mode
In terms of the include/exclude options, the difference lies in the path to the report.
-
In Azure extraction, the options are matched with the workspace/report. For example,
Some Workspace/.*SomeReport
would match any report ending inSomeReport
in the workspaceSome Workspace
. -
In local extraction, there is no concept of a workspace, but there are folders. So, the path/report is used instead. For example,
TestFolder/.*SomeReport
would match all reports ending inSomeReport
in any subfolder ofTestFolder
.
This may not seem like a big difference, but despite the fact that Power BI Azure’s workspaces cannot contain more workspaces, the folders may contain folders. Additionally, note that although Power BI Azure allows report names to contain /
,
this currently is not supported by Manta Data Lineage.