Contents

Connect to data in Power BI

Overview
Data sources in Power BI
What is an on-premises data gateway?
Quickstarts
Connect to data in Power BI Desktop
Tutorials
Shape and combine multiple data sources
Import and analyze webpage data
Analyze sales data from Excel and an OData feed
Analyze Facebook data
Implement row-level security in an Analysis Services tabular model
Connect to a GitHub sample
Use Cognitive Services
Machine Learning integration
Build a Machine Learning model
Refresh data from SQL Server
Concepts
Power BI data sources
Power BI data source prerequisites
Using enhanced dataset metadata in Power BI Desktop (preview)
Work with multidimensional models in Power BI
About using DirectQuery in Power BI
Gateways
Guidance for deploying a data gateway
On-premises data gateway FAQ
How-to guides
Connect to data sources
Connect to data
Connect to data sources
Create a report on a SharePoint List
Connect to LinkedIn Sales Navigator
Get webpage data by providing examples
Connect to datasets in the Power BI service
Import Excel workbooks
Connect to data with Power BI Desktop generic interfaces
Connect to PDF files
Connect to Adobe Analytics
Connect to an Oracle database
Python
Run Python scripts
Use Python in Query Editor
Use an external Python IDE
Create visuals with Python
Learn which Python packages are supported
Run R scripts
Use R in Query Editor
Use an external R IDE
Create visuals with R packages
Enter data directly into Power BI Desktop
Connect to Excel workbooks
Connect to SSAS multidimensional models
Connect to CSV files
Connect to a Google BigQuery database
Connect to an Impala database
Connect to OData feeds
Connect to an Amazon Redshift database
Connect to webpages
Connect to a Snowflake computing warehouse
Connect to Snowflake in the Power BI service
Create visuals with the Azure Cost Management connector
 Connect to Azure Consumption Insights data
Connect to SAP HANA databases
Enable encryption for SAP HANA
Connect to Analysis Services tabular data
Connect to data sources with DirectQuery
Connect to SAP Business Warehouse with DirectQuery
Connect to SAP HANA data sources with DirectQuery
Apply the Assume Referential Integrity setting
Access SAP BW data with the SAP BW Connector
Use OneDrive for Business links
Third-party service: Use the Facebook connector
Third-party service: Use the Google Analytics connector
Connect to Project Online data through Power BI Desktop
Get data from files
Getting data from files
Get data from Excel workbook files
Get data from Power BI Desktop files
Edit parameters
Get data from comma separated value (.csv) files
Real-time streaming in Power BI
Publish to Power BI from Excel
Reduce the size of an Excel workbook
Get data from shared datasets
Use datasets across workspaces
Share datasets
Build permission for shared datasets
Create reports based on datasets
Copy reports based on datasets
Control the use of datasets
Endorse datasets
Promote datasets
Certify datasets
Get data from databases
Azure and Power BI
Power BI and Azure egress
Azure SQL Data Warehouse with DirectQuery
Azure SQL Database with DirectQuery
SQL Server Analysis Services live data in Power BI
Refresh data
Data refresh in Power BI
Configure scheduled refresh
Refresh summaries
Configure incremental refresh
Refresh a dataset from a local Power BI Desktop file
Refresh a dataset from a cloud Power BI Desktop file
Refresh a dataset from a local Excel workbook
Refresh a dataset from a cloud Excel workbook
Refresh a dataset from a .csv file on OneDrive
Query caching in Power BI Premium
Template apps
Template apps overview
Create template apps
Tips for creating template apps
Install & distribute template apps
Update, delete, and extract a Power BI template app
Template apps samples
Troubleshoot
Troubleshoot refresh scenarios
Troubleshoot an unsupported data source for refresh
Troubleshoot scheduled refresh for Azure SQL Databases
Troubleshoot analyze in Excel
Error: We couldn't find any data in your Excel workbook
How to refresh your Xero content pack credentials if refresh failed
Connect to services
 Connect to services with apps
COVID-19 US Tracking Report
Crisis Communication Presence Report
GitHub
Hospital Emergency Response Decision Support Dashboard
Microsoft Sustainability Calculator
Office365Mon
Power BI Premium Capacity Metrics
Project Online
QuickBooks Online
Regional Emergency Response Dashboard
Salesforce
Smartsheet
Xero
Zendesk
Gateways
On-premises data gateway - in-depth
On-premises data gateway (personal mode)
Manage gateway data sources
Manage data sources
Manage your enterprise data source - Analysis Services
Manage your enterprise data source - SAP HANA
Manage your enterprise data source - SQL
Manage your data source - Oracle
Manage your enterprise data source - import/scheduled refresh
Merge on-premises and cloud data sources
Enable single sign-on (SSO)
SSO overview
Kerberos-based SSO
Configure Kerberos-based SSO
Datasource-specific configuration
SAML-based SSO
 Troubleshoot the gateway
Troubleshoot the gateway (personal mode)
Use custom connectors
Troubleshoot
Troubleshoot importing Access and Excel .xls files
Troubleshoot opening Power BI Desktop
Troubleshoot developing DirectQuery models
Reference
Data types in Power BI Desktop
Connector extensibility
Trusted third-party connectors
 Data sources for the Power BI service
9/9/2020 • 10 minutes to read • Edit Online

Data is at the heart of Power BI. Let's say you're exploring data. You may do that by creating charts and
dashboards, or asking questions with Q&A . The visualizations and answers you see are getting their underlying
data from a dataset. But where does that dataset come from? Well, it comes from a data source.
In this article, we're going to cover the data source types you can connect to from the Power BI service. Keep in
mind that there are many other types of data sources you can get data from, too. If you choose these data sources,
you may need to use Power BI Desktop or Excel's advanced data query and modeling features first. We'll go into
more about those options later. For now, let's look at the different types of data sources available right from your
Power BI service site.
You can get data from any of the data sources in Power BI by selecting Get Data in the bottom-left corner of the
page.

After you select Get Data , you can choose the data you want to access

Discover content
The Discover content section contains all the data and reports you need already prepared for you. In Power BI,
there are two types of content packs: Organizational and Services.
Organizational : If you and other users in your organization have a Power BI Pro account, you can create, share,
and use content packs. To learn more, see Intro to organizational content packs.
Ser vices : There are literally dozens of services with content packs for Power BI, and more are being added all the
time. Most services require you to have an account. To learn more, see Connect to services you use with Power BI.

Create new content

The Create new content section contains options for creating and importing content yourself. In Power BI, there
are two ways to create or import your own content: Files and Databases.
Files

Excel (.xlsx, .xlsm) - In Excel, a workbook may include different data types. For example, it can include data you've
entered into worksheets yourself. It can also include data that you've queried and loaded from external data
sources by using Power Query. Power Query is available through Get & Transform in Excel 2016 or Power Pivot.
You may import data from tables in worksheets, or import data from a data model. To learn more, see Get data
from files for Power BI.
Power BI Desktop (.pbix) - You can use Power BI Desktop to query and load data from external data sources and
create reports. You can also extend your data model with measures and relationships, or import your Power BI
Desktop file into your Power BI site. Power BI Desktop is best for more advanced users. Typically these users are
ones who have a good understanding of their data sources. They also understand data query and transformation,
and data modeling concepts. To learn more, see Connect to data in Power BI Desktop.
Comma-Separated Value (.csv) - Files are simple text files with rows of data. Each row may contain one or more
values, each separated by a comma. For example, a .csv containing name and address data might have many rows.
Each row may have values for first name, last name, street address, city, state, and so on. You can't import data into
a .csv file, but many applications, like Excel, can save simple table data as a .csv file.
For other file types, like XML Table (.xml) or text (.txt) files, you can use Get & Transform to query, transform, and
load that data into an Excel or Power BI Desktop file first. You can then import the Excel or Power BI Desktop file
into Power BI.
Where you store your files makes a significant difference, too. OneDrive for Business provides the greatest amount
of flexibility and integration with Power BI. It's OK to keep your files on your local drive. Though if you need to
refresh your data, there are a few extra steps. For more information, see the article links below.
Databases
Databases in the Cloud - From the Power BI service, you can connect live to:
Azure SQL Database
Azure SQL Data Warehouse
Spark on Azure HDInsight
Connections from Power BI to these databases are live. Let's say you connect to an Azure SQL Database. You then
begin exploring its data by creating reports in Power BI. Whenever you slice your data or add another field to a
visualization, Power BI makes a query right to the database. To learn more, see Azure and Power BI.
Databases on-premises - From the Power BI service, you can connect directly to SQL Server Analysis Services
Tabular model databases. To do so, you'll need a Power BI Enterprise gateway. If you're not clear on how to connect
to your organization's tabular model database, check with your administrator or IT department. To learn more, see
SQL Server Analysis Services live data in Power BI.
For other database types in your organization, you'll need to use Power BI Desktop or Excel to connect to, query,
and load data into a data model. You can then import your file into Power BI where a dataset exists. If you
configure a scheduled refresh, Power BI will use that configuration and connection information from the file to
connect directly to the datasource and query for updates. Power BI then loads those updates into the dataset. To
learn more, see Connect to data in Power BI Desktop.

What if my data comes from a different source?

There are hundreds of different data sources you can use with Power BI. Wherever you get your data from, that
data has to be in a format consumable by the Power BI service. With consumable data, the Power BI service can
create reports and dashboards, answer questions with Q&A , and so on.
Some data sources already have data formatted for the Power BI service. These sources are like content packs
from service providers like Google Analytics and Twilio. SQL Server Analysis Services Tabular model databases are
ready for use, too. You can also connect live to databases in the cloud like Azure SQL Database and Spark on
HDInsight.
In other cases, it might be necessary to query and load the data you want into a file. For example, let's say you
have logistics data in your organization. You store that data in a data warehouse database on a server. In the Power
BI service, you can't connect to that database and begin exploring its data unless it's a tabular model database. But,
you can use Power BI Desktop or Excel to query and load that logistics data into a data model you then save as a
file. You can then import that file into Power BI where a dataset exists.
You're probably thinking, "But the logistics data on that database changes every day. How do I refresh my Power BI
dataset?" When you import the data into the dataset, you also import the connection information from either the
Power BI Desktop or the Excel file.
Let's say you configure a scheduled refresh or do a manual refresh on the dataset. Power BI uses the connection
information from the dataset, along with a couple of other settings, to connect directly to the database. It then
queries for updates and loads those updates into the dataset. As a side note, you likely will need a Power BI
gateway to secure any data transfer between your on-premises server and Power BI. When the transfer is
complete, any visualizations in reports and dashboards refresh automatically.
You see, even though you can't connect to your data source directly from the Power BI service you can still get that
data into Power BI. It just might take a few more steps and maybe some help from your IT department. See Data
sources in Power BI Desktop to learn more.

Some more details

You'll see the terms dataset and data source used a lot in Power BI. They're often used synonymously. But they
really are two different things, although they're related.
You create a dataset automatically in Power BI when you use Get Data . With Get Data , you connect to and
import data from a content pack, file, or you connect to a live data source. A dataset contains information about
the data source and data-source credentials. In many cases, it also includes a subset of data copied from the data
source. When you create visualizations in reports and dashboards, you're often looking at data in the dataset.
A data source is where the data in a dataset comes from. For example, the data could come from:
An online service like Google Analytics or QuickBooks
A database in the cloud like Azure SQL Database
A database or file on a local computer or server in your own organization

Data refresh
Maybe you save your files on your local drive or a drive somewhere in your organization. You may need a Power
BI gateway so that you can refresh the dataset in Power BI. The computer that stores the file needs to be on when a
refresh happens. You can reimport your file or use Publish from Excel or Power BI Desktop, but those options
aren't automated processes.
If you save your files on OneDrive for Business or SharePoint - Team Sites, you can then connect to or import them
into Power BI. Then, your dataset, reports, and dashboard will always be up-to-date. Because both OneDrive and
Power BI are in the cloud, Power BI can connect directly to your saved file. It connects about once every hour and
checks for updates. The dataset and any visualizations refresh automatically if there are any updates.
Content packs from services are automatically updated. In most cases, they're updated once a day. You can
manually refresh, but if you see any updated data will depend on the service provider. Updates to content packs
from people in your organization will depend on the data sources used. They'll also depend on how the person
who created the content pack configured the refresh.
Azure SQL Database, Azure SQL Data Warehouse, and Spark on Azure HDInsight are data sources in the Cloud.
The Power BI service is also in the cloud so Power BI can connect to those data sources live, using DirectQuer y .
What you see in Power BI is always in sync and there's no need to set up a scheduled refresh.
When you connect to SQL Server Analysis Services from Power BI, it's a live connection just like an Azure database
in the cloud. The difference is the database itself is on a server in your organization. This type of connection
requires a Power BI gateway, which an IT department configures.
Data refresh is a super important part of Power BI, and much too deep to cover here. If you want to get a thorough
understanding, be sure to check out Data Refresh in Power BI.

Considerations and limitations

For all data sources used in the Power BI service, consider the following limitations. There are other limitations that
apply to specific features, but the following list applies to the full Power BI service:
Dataset size limit - There's a 1-GB limit for datasets stored in Shared capacities in the Power BI service. If
you need larger datasets, you can use Power BI Premium.
Distinct values in a column - When caching data in a Power BI dataset (sometimes called 'Import'
mode), there is a 1,999,999,997 limit on the number of distinct values that can be stored in a column.
Row limit - When using DirectQuer y , Power BI imposes a limit on the query results that are sent to your
underlying data source. If the query sent to the data source returns more than one million rows, you see an
error and the query fails. Your underlying data can still contain more than one million rows. You're unlikely
to run into this limit as most reports aggregate the data into smaller sets of results.
Column limit - The maximum number of columns allowed in a dataset, across all tables in the dataset, is
16,000 columns. This limit applies to the Power BI service and to datasets used in Power BI Desktop. Power
BI tracks the number of columns and tables in the dataset in this way, which means the maximum number
of columns is 16,000 minus one for each table in the dataset.
 What is an on-premises data gateway?
5/13/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

The on-premises data gateway acts as a bridge to provide quick and secure data transfer between on-premises
data (data that isn't in the cloud) and several Microsoft cloud services. These cloud services include Power BI,
PowerApps, Power Automate, Azure Analysis Services, and Azure Logic Apps. By using a gateway, organizations
can keep databases and other data sources on their on-premises networks, yet securely use that on-premises
data in cloud services.

How the gateway works

For more information on how the gateway works, see On-premises data gateway architecture.

Types of gateways
There are two different types of gateways, each for a different scenario:
On-premises data gateway allows multiple users to connect to multiple on-premises data sources. You
can use an on-premises data gateway with all supported services, with a single gateway installation. This
gateway is well-suited to complex scenarios with multiple people accessing multiple data sources.
 On-premises data gateway (personal mode) allows one user to connect to sources, and can’t be
shared with others. An on-premises data gateway (personal mode) can be used only with Power BI. This
gateway is well-suited to scenarios where you’re the only person who creates reports, and you don't need
to share any data sources with others.

Use a gateway
There are four main steps for using a gateway.
1. Download and install the gateway on a local computer.
2. Configure the gateway based on your firewall and other network requirements.
3. Add gateway admins who can also manage and administer other network requirements.
4. Use the gateway to refresh an on-premises data source.
5. Troubleshoot the gateway in case of errors.

Next steps
Install the on-premises data gateway
More questions? Try the Power BI Community
 Quickstart: Connect to data in Power BI Desktop
5/13/2020 • 2 minutes to read • Edit Online

In this quickstart, you connect to data using Power BI Desktop, which is the first step in building data models and
creating reports.

If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
To complete the steps in this article, you need the following resources:
Download and install Power BI Desktop, which is a free application that runs on your local computer. You can
download Power BI Desktop directly, or you can get it from the Microsoft Store.
Download this sample Excel workbook, and create a folder called C:\PBID-qs where you can store the Excel file.
Later steps in this quickstart assume that is the file location for the downloaded Excel workbook.
For many data connectors in Power BI Desktop, Internet Explorer 10 (or newer) is required for authentication.

Launch Power BI Desktop

Once you install Power BI Desktop, launch the application so it's running on your local computer. You're presented
with a Power BI tutorial. Follow the tutorial or close the dialog to start with a blank canvas. The canvas is where you
create visuals and reports from your data.
Connect to data
With Power BI Desktop, you can connect to many different types of data. These sources include basic data sources,
such as a Microsoft Excel file. You can connect to online services that contain all sorts of data, such as Salesforce,
Microsoft Dynamics, Azure Blob Storage, and many more.
To connect to data, from the Home ribbon select Get Data .

The Get Data window appears. You can choose from the many different data sources to which Power BI Desktop
can connect. In this quickstart, use the Excel workbook that you downloaded in Prerequisites.
Since this data source is an Excel file, select Excel from the Get Data window, then select the Connect button.
Power BI prompts you to provide the location of the Excel file to which to connect. The downloaded file is called
Financial Sample. Select that file, and then select Open .

Power BI Desktop then loads the workbook and reads its contents, and shows you the available data in the file
using the Navigator window. In that window, you can choose which data you would like to load into Power BI
Desktop. Select the tables by marking the checkboxes beside each table you want to import. Import both available
tables.

Once you've made your selections, select Load to import the data into Power BI Desktop.

View data in the Fields pane

Once you've loaded the tables, the Fields pane shows you the data. You can expand each table by selecting the
arrow beside its name. In the following image, the financials table is expanded, showing each of its fields.
And that's it! You've connected to data in Power BI Desktop, loaded that data, and now you can see all the available
fields within those tables.

Next steps
There are all sorts of things you can do with Power BI Desktop once you've connected to data. You can create
visuals and reports. Take a look at the following resource to get you going:
Get started with Power BI Desktop
 Tutorial: Shape and combine data in Power BI
Desktop
5/13/2020 • 13 minutes to read • Edit Online

With Power BI Desktop, you can connect to many different types of data sources, then shape the data to meet
your needs, enabling you to create visual reports to share with others. Shaping data means transforming the
data: renaming columns or tables, changing text to numbers, removing rows, setting the first row as headers, and
so on. Combining data means connecting to two or more data sources, shaping them as needed, then
consolidating them into a useful query.
In this tutorial, you'll learn how to:
Shape data by using Query Editor.
Connect to different data sources.
Combine those data sources, and create a data model to use in reports.
This tutorial demonstrates how to shape a query by using Power BI Desktop, highlighting the most common
tasks. The query used here is described in more detail, including how to create the query from scratch, in Getting
Started with Power BI Desktop.
Query Editor in Power BI Desktop makes ample use of right-click menus, as well as the Transform ribbon. Most
of what you can select in the ribbon is also available by right-clicking an item, such as a column, and choosing
from the menu that appears.

Shape data
When you shape data in Query Editor, you provide step-by-step instructions for Query Editor to carry out for you
to adjust the data as it loads and presents it. The original data source isn't affected; only this particular view of the
data is adjusted, or shaped.
The steps you specify (such as rename a table, transform a data type, or delete a column) are recorded by Query
Editor. Each time this query connects to the data source, Query Editor carries out those steps so that the data is
always shaped the way you specify. This process occurs whenever you use Query Editor, or for anyone who uses
your shared query, such as on the Power BI service. Those steps are captured, sequentially, in the Quer y
Settings pane, under Applied Steps . We’ll go through each of those steps in the next few paragraphs.
From Getting Started with Power BI Desktop, let's use the retirement data, which we found by connecting to a
web data source, to shape that data to fit our needs. We'll add a custom column to calculate rank based on all
data being equal factors, and compare this column to the existing column, Rank .
1. From the Add Column ribbon, select Custom Column , which lets you add a custom column.

2. In the Custom Column window, in New column name , enter New Rank. In Custom column formula ,
enter the following data:

([Cost of living] + [Weather] + [Health care quality] + [Crime] + [Tax] + [Culture] + [Senior] +
[#"Well-being"]) / 8

3. Make sure the status message is No syntax errors have been detected, and select OK .
4. To keep column data consistent, transform the new column values to whole numbers. To change them,
right-click the column header, and then select Change Type > Whole Number .
If you need to choose more than one column, select a column, hold down SHIFT , select additional
adjacent columns, and then right-click a column header. You can also use the CTRL key to choose non-
adjacent columns.

5. To transform column data types, in which you transform the current data type to another, select Data
 Type Text from the Transform ribbon.

6. In Quer y Settings , the Applied Steps list reflects any shaping steps applied to the data. To remove a
step from the shaping process, select the X to the left of the step.
In the following image, the Applied Steps list reflects the added steps so far:
Source : Connecting to the website.
Navigation : Selecting the table.
Changed Type : Changing text-based number columns from Text to Whole Number.
Added Custom : Adding a custom column.
Changed Type1 : The last applied step.

Adjust data
Before we can work with this query, we need to make a few changes to adjust its data:
Adjust the rankings by removing a column.
We've decided Cost of living is a non-factor in our results. After removing this column, we find that the
data remains unchanged.
Fix a few errors.
Because we removed a column, we need to readjust our calculations in the New Rank column, which
involves changing a formula.
Sort the data.
Sort the data based on the New Rank and Rank columns.
 Replace the data.
We'll highlight how to replace a specific value and the need of inserting an Applied Step .
Change the table name.
Because Table 0 isn't a useful descriptor for the table, we'll change its name.
1. To remove the Cost of living column, select the column, choose the Home tab from the ribbon, and then
select Remove Columns .

Notice the New Rank values haven't changed, due to the ordering of the steps. Because Query Editor
records the steps sequentially, yet independently, of each other, you can move each Applied Step up or
down in the sequence.
2. Right-click a step. Query Editor provides a menu that lets you do the following tasks:
Rename ; Rename the step.
Delete : Delete the step.
Delete Until End : Remove the current step, and all subsequent steps.
Move Up : Move the step up in the list.
Move Down : Move the step down in the list.
3. Move up the last step, Removed Columns , to just above the Added Custom step.
4. Select the Added Custom step.
Notice the data now shows Error, which we'll need to address.
 There are a few ways to get more information about each error. If you select the cell without clicking on
the word Error, Query Editor displays the error information on the bottom of the window.

If you select the word Error directly, Query Editor creates an Applied Step in the Quer y Settings pane
and displays information about the error.
5. Because we don't need to display information about the errors, select Cancel .
6. To fix the errors, select the New Rank column, then display the column's data formula by selecting the
Formula Bar checkbox from the View tab.
7. Remove the Cost of living parameter and decrement the divisor, by changing the formula as follows:

Table.AddColumn(#"Removed Columns", "New Rank", each ([Weather] + [Health care quality] + [Crime] +
[Tax] + [Culture] + [Senior] + [#"Well-being"]) / 7)

8. Select the green checkmark to the left of the formula box or press Enter .
Query Editor replaces the data with the revised values and the Added Custom step completes with no errors.

NOTE
You can also select Remove Errors , by using the ribbon or the right-click menu, which removes any rows that have errors.
However, we didn't want to do so in this tutorial because we wanted to preserve the data in the table.

1. Sort the data based on the New Rank column. First, select the last applied step, Changed Type1 to
display the most recent data. Then, select the drop-down located next to the New Rank column header
and select Sor t Ascending .
 The data is now sorted according to New Rank . However, if you look at the Rank column, you'll notice
the data isn't sorted properly in cases where the New Rank value is a tie. We'll fix it in the next step.
2. To fix the data sorting issue, select the New Rank column and change the formula in the Formula Bar to
the following formula:

= Table.Sort(#"Changed Type1",{{"New Rank", Order.Ascending},{"Rank", Order.Ascending}})

3. Select the green checkmark to the left of the formula box or press Enter .
The rows are now ordered in accordance with both New Rank and Rank . In addition, you can select an
Applied Step anywhere in the list, and continue shaping the data at that point in the sequence. Query
Editor automatically inserts a new step directly after the currently selected Applied Step .
4. In Applied Step , select the step preceding the custom column, which is the Removed Columns step.
Here we'll replace the value of the Weather ranking in Arizona. Right-click the appropriate cell that
contains Arizona's Weather ranking, and then select Replace Values . Note which Applied Step is
currently selected.
5. Select Inser t .
Because we're inserting a step, Query Editor warns us about the danger of doing so; subsequent steps
could cause the query to break.

6. Change the data value to 51.

Query Editor replaces the data for Arizona. When you create a new Applied Step , Query Editor names it
based on the action; in this case, Replaced Value . If you have more than one step with the same name in
your query, Query Editor adds a number (in sequence) to each subsequent Applied Step to differentiate
between them.
7. Select the last Applied Step , Sor ted Rows .
Notice the data has changed regarding Arizona's new ranking. This change occurs because we inserted
the Replaced Value step in the correct location, before the Added Custom step.
8. Lastly, we want to change the name of that table to something descriptive. In the Quer y Settings pane,
under Proper ties , enter the new name of the table, and then select Enter . Name this table
RetirementStats.
 When we start creating reports, it’s useful to have descriptive table names, especially when we connect to
multiple data sources, which are listed in the Fields pane of the Repor t view.
We’ve now shaped our data to the extent we need to. Next let’s connect to another data source, and
combine data.

Combine data
The data about various states is interesting, and will be useful for building additional analysis efforts and queries.
But there’s one problem: most data out there uses a two-letter abbreviation for state codes, not the full name of
the state. We need a way to associate state names with their abbreviations.
We’re in luck; there’s another public data source that does just that, but it needs a fair amount of shaping before
we can connect it to our retirement table. TO shape the data, follow these steps:
1. From the Home ribbon in Query Editor, select New Source > Web .
2. Enter the address of the website for state abbreviations,
https://en.wikipedia.org/wiki/List_of_U.S._state_abbreviations, and then select Connect .
The Navigator displays the content of the website.
3. Select Codes and abbreviations .

TIP
It will take quite a bit of shaping to pare this table’s data down to what we want. Is there a faster or easier way to
accomplish the steps below? Yes, we could create a relationship between the two tables, and shape the data based
on that relationship. The following steps are still good to learn for working with tables; however, relationships can
help you quickly use data from multiple tables.

To get the data into shape, follow these steps:

1. Remove the top row. Because it's a result of the way that the web page’s table was created, we don’t need
it. From the Home ribbon, select Reduce Rows > Remove Rows > Remove Top Rows .
 The Remove Top Rows window appears, letting you specify how many rows you want to remove.

NOTE
If Power BI accidentally imports the table headers as a row in your data table, you can select Use First Row As
Headers from the Home tab, or from the Transform tab in the ribbon, to fix your table.

2. Remove the bottom 26 rows. These rows are U.S. territories, which we don’t need to include. From the
Home ribbon, select Reduce Rows > Remove Rows > Remove Bottom Rows .

3. Because the RetirementStats table doesn't have information for Washington DC, we need to filter it from
our list. Select the Region Status drop-down, then clear the checkbox beside Federal district .
4. Remove a few unneeded columns. Because we need only the mapping of each state to its official two-
letter abbreviation, we can remove the following columns: Column1 , Column3 , Column4 , and
Column6 through Column11 . First select Column1 , then hold down the CTRL key and select each of
the other columns to be removed. From the Home tab on the ribbon, select Remove Columns >
Remove Columns .

NOTE
This is a good time to point out that the sequence of applied steps in Query Editor is important, and can affect
how the data is shaped. It’s also important to consider how one step may impact another subsequent step; if you
remove a step from the Applied Steps, subsequent steps may not behave as originally intended, because of the
impact of the query’s sequence of steps.

NOTE
When you resize the Query Editor window to make the width smaller, some ribbon items are condensed to make
the best use of visible space. When you increase the width of the Query Editor window, the ribbon items expand to
make the most use of the increased ribbon area.
5. Rename the columns and the table. There are a few ways to rename a column: First, select the column,
then either select Rename from the Transform tab on the ribbon, or right-click and select Rename . The
following image has arrows pointing to both options; you only need to choose one.

6. Rename the columns to State Name and State Code. To rename the table, enter the Name in the Quer y
Settings pane. Name this table StateCodes.

Combine queries
Now that we’ve shaped the StateCodes table the way we want, let’s combine these two tables, or queries, into
one. Because the tables we now have are a result of the queries we applied to the data, they’re often referred to
as queries.
There are two primary ways of combining queries: merging and appending.
When you have one or more columns that you’d like to add to another query, you merge the queries.
When you have additional rows of data that you’d like to add to an existing query, you append the query.
In this case, we want to merge the queries. To do so, follow these steps:
1. From the left pane of Query Editor, select the query into which you want the other query to merge. In this
case, it's RetirementStats .
2. Select Combine > Merge Queries from the Home tab on the ribbon.
 You may be prompted to set the privacy levels, to ensure the data is combined without including or
transferring data you don't want transferred.
The Merge window appears. It prompts you to select which table you'd like merged into the selected
table, and the matching columns to use for the merge.
3. Select State from the RetirementStats table, then select the StateCodes query.
When you select the correct matching columns, the OK button is enabled.

4. Select OK .
Query Editor creates a NewColumn column at the end of the query, which contains the contents of the
table (query) that was merged with the existing query. All columns from the merged query are condensed
into the NewColumn column, but you can Expand the table and include whichever columns you want.
5. To expand the merged table, and select which columns to include, select the expand icon ( ).
The Expand window appears.

6. In this case, we want only the State Code column. Select that column, clear Use original column name
as prefix , and then select OK .
If we had left the checkbox selected for Use original column name as prefix , the merged column
would be named NewColumn.State Code .
 NOTE
Want to explore how to bring in the NewColumn table? You can experiment a bit, and if you don’t like the results,
just delete that step from the Applied Steps list in the Quer y Settings pane; your query returns to the state
prior to applying that Expand step. You can do this as many times as you like until the expand process looks the
way you want it.

We now have a single query (table) that combines two data sources, each of which has been shaped to
meet our needs. This query can serve as a basis for many additional and interesting data connections,
such as housing cost statistics, demographics, or job opportunities in any state.
7. To apply your changes and close Query Editor, select Close & Apply from the Home ribbon tab.
The transformed dataset appears in Power BI Desktop, ready to be used for creating reports.

Next steps
For more information on Power BI Desktop and its capabilities, see the following resources:
What is Power BI Desktop?
Query overview in Power BI Desktop
Data sources in Power BI Desktop
Connect to data in Power BI Desktop
Common query tasks in Power BI Desktop
 Tutorial: Analyze webpage data by using Power BI
Desktop
9/9/2020 • 7 minutes to read • Edit Online

As a long-time soccer fan, you want to report on the UEFA European Championship (Euro Cup) winners over the
years. With Power BI Desktop, you can import this data from a web page into a report and create visualizations that
show the data. In this tutorial, you learn how to use Power BI Desktop to:
Connect to a web data source and navigate across its available tables.
Shape and transform data in the Power Query Editor.
Name a query and import it into a Power BI Desktop report.
Create and customize a map and a pie chart visualization.

Connect to a web data source

You can get the UEFA winners data from the Results table on the UEFA European Football Championship Wikipedia
page at https://en.wikipedia.org/wiki/UEFA_European_Football_Championship.

Web connections are only established using basic authentication. Web sites requiring authentication may not work
properly with the Web connector.
To import the data:
1. In the Power BI Desktop Home ribbon tab, drop down the arrow next to Get Data , and then select Web .
 NOTE
You can also select the Get Data item itself, or select Get Data from the Power BI Desktop get started dialog, then
select Web from the All or Other section of the Get Data dialog, and then select Connect .

2. In the From Web dialog, paste the URL https://en.wikipedia.org/wiki/UEFA_European_Football_Championship

into the URL text box, and then select OK .

After connecting to the Wikipedia web page, the Navigator dialog shows a list of available tables on the
page. You can select any of the table names to preview its data. The Results[edit] table has the data you
want, although it's not exactly in the shape you want. You'll reshape and clean up the data before loading it
into your report.
 NOTE
The Preview pane shows the most recent table selected, but all selected tables will load into the Power Query Editor
when you select Transform Data or Load .

3. Select the Results[edit] table in the Navigator list, and then select Transform Data .
A preview of the table opens in Power Quer y Editor , where you can apply transformations to clean up the
data.

Shape data in Power Query Editor

You want to make the data easier to scan by displaying only the years and the countries that won. You can use the
Power Query Editor to perform these data shaping and cleansing steps.
First, remove all the columns except for two from the table. Rename these columns as Year and Country later in the
process.
1. In the Power Quer y Editor grid, select the columns. Select Ctrl to select multiple items.
2. Right-click and select Remove Other Columns , or select Remove Columns > Remove Other Columns
from the Manage Columns group in the Home ribbon tab, to remove all other columns from the table.

or

Next, remove the extra word Details from the first column cells.
1. Select the first column.
2. Right-click, and select Replace Values , or select Replace Values from the Transform group in the Home
tab of the ribbon. This option is also found in the Any Column group in the Transform tab.

or
3. In the Replace Values dialog, type Details in the Value To Find text box, leave the Replace With text box
empty, and then select OK to delete the word Details from this column.

Some cells contain only the word "Year" rather than year values. You can filter the column to only display rows that
don't contain the word "Year".
1. Select the filter drop-down arrow on the column.
2. In the drop-down menu, scroll down and clear the checkbox next to the Year option, and then select OK .

Since you're only looking at the final winners data now, you can rename the second column to Countr y . To rename
the column:
1. Double-click or tap and hold in the second column header, or
Right-click the column header, and select Rename , or
Select the *column and select Rename from the Any Column group in the Transform tab of the ribbon.

or

2. Type Countr y in the header and press Enter to rename the column.
You also want to filter out rows like "2020" that have null values in the Countr y column. You could use the filter
menu as you did with the Year values, or you can:
1. Right-click on the Countr y cell in the 2020 row, which has the value null.
2. Select Text Filters > Does not Equal in the context menu to remove any rows that contain that cell's value.

Import the query into Report View

Now that you've shaped the data the way you want, you're ready to name your query "Euro Cup Winners" and
import it into your report.
1. In the Quer y Settings pane, in the Name text box, enter Euro Cup Winners .

2. Select Close & Apply > Close & Apply from the Home tab of the ribbon.

The query loads into the Power BI Desktop Report view, where you can see it in the Fields pane.

TIP
You can always get back to the Power Query Editor to edit and refine your query by:
Selecting the More options ellipsis (... ) next to Euro Cup Winners in the Fields pane, and selecting Edit Quer y , or
Selecting Edit Queries > Edit Queries in the External data group of the Home ribbon tab in Report view.

Create a visualization
To create a visualization based on your data:
1. Select the Countr y field in the Fields pane, or drag it to the report canvas. Power BI Desktop recognizes the
data as country names, and automatically creates a Map visualization.

2. Enlarge the map by dragging the handles in the corners so all the winning country names are visible.

3. The map shows identical data points for every country that won a Euro Cup tournament. To make the size of
each data point reflect how often the country has won, drag the Year field to Drag data fields here under
Size in the lower part of the Visualizations pane. The field automatically changes to a Count of Year
measure, and the map visualization now shows larger data points for countries that have won more
tournaments.
Customize the visualization
As you can see, it's very easy to create visualizations based on your data. It's also easy to customize your
visualizations to better present the data in ways that you want.
Format the map
You can change the appearance of a visualization by selecting it and then selecting the Format (paint roller) icon in
the Visualizations pane. For example, the "Germany" data points in your visualization could be misleading,
because West Germany won two tournaments and Germany won one, and the map superimposes the two points
rather than separating or adding them together. You can color these two points differently to highlight this fact. You
can also give the map a more descriptive and attractive title.
1. With the visualization selected, select the Format icon, and then select Data colors to expand the data color
options.

2. Turn Show all to On , and then select the drop-down menu next to West Germany and choose a yellow
 color.

3. Select Title to expand the title options, and in the Title text field, type Euro Cup Winners in place of the
current title.
4. Change Font color to red, Text size to 12 , and Font family to Segoe (Bold) .

Your map visualization now looks like this:

Change the visualization type
You can change the type of a visualization by selecting it and then selecting a different icon at the top of the
Visualizations pane. For example, your map visualization is missing the data for the Soviet Union and
Czechoslovakia, because those countries no longer exist on the world map. Another type of visualization like a
treemap or pie chart may be more accurate, because it shows all the values.
To change the map to a pie chart, select the map and then select the Pie char t icon in the Visualizations pane.

TIP
You can use the Data colors formatting options to make "Germany" and "West Germany" the same color.
To group the countries with the most wins together on the pie chart, select the ellipsis (... ) at the upper right of the
visualization, and then select Sor t by Count of Year .

Power BI Desktop provides a seamless end-to-end experience, from getting data from a wide range of data sources
and shaping it to meet your analysis needs, to visualizing this data in rich and interactive ways. Once your report is
ready, you can upload it to Power BI and create dashboards based on it, which you can share with other Power BI
users.

See also
Microsoft Learn for Power BI
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Tutorial: Analyze sales data from Excel and an OData
feed
9/9/2020 • 10 minutes to read • Edit Online

It's common to have data in multiple data sources. For example, you could have two databases, one for product
information, and another for sales information. With Power BI Desktop, you can combine data from different
sources to create interesting, compelling data analyses and visualizations.
In this tutorial, you combine data from two data sources:
An Excel workbook with product information
An OData feed containing orders data
You're going to import each dataset and do transformation and aggregation operations. Then, you'll use the two
source's data to produce a sales analysis report with interactive visualizations. Later, you can apply these techniques
to SQL Server queries, CSV files, and other data sources in Power BI Desktop.

NOTE
In Power BI Desktop, there are often a few ways to accomplish a task. For example, you can right-click or use a More
options menu on a column or cell to see additional ribbon selections. Several alternate methods are described in the steps
below.

Import Excel product data

First, import product data from the Products.xlsx Excel workbook into Power BI Desktop.
1. Download the Products.xlsx Excel workbook and save it as Products.xlsx.
2. Select the arrow next to Get Data in the Power BI Desktop ribbon's Home tab, and then select Excel from
the Most Common menu.
 NOTE
You can also select the Get Data item itself, or select Get Data from the Power BI Get star ted dialog box, then
select Excel or File > Excel in the Get Data dialog box, and then select Connect .

3. In the Open dialog box, navigate to and select the Products.xlsx file, and then select Open .
4. In the Navigator , select the Products table and then select Transform Data .
A table preview opens in the Power Query Editor, where you can apply transformations to clean up the data.

NOTE
You can also open the Power Query Editor by selecting Edit Queries > Edit Queries from the Home ribbon in Power BI
Desktop, or by right-clicking or choosing More options next to any query in the Repor t view, and selecting Edit Quer y .

Clean up the products columns

Your combined report will use the Excel workbook's ProductID , ProductName , QuantityPerUnit , and
UnitsInStock columns. You can remove the other columns.
1. In Power Query Editor, select the ProductID , ProductName , QuantityPerUnit , and UnitsInStock
columns. You can use Ctrl to select more than one column, or Shift to select columns next to each other.
2. Right-click any of the selected headers. Select Remove Other Columns from the drop-down menu. You
can also select Remove Columns > Remove Other Columns from the Manage Columns group in the
Home ribbon tab.

Import the OData feed's order data

Next, import the order data from the sample Northwind sales system OData feed.
1. In Power Query Editor, select New Source and then, from the Most Common menu, select OData feed .
2. In the OData feed dialog box, paste the Northwind OData feed URL,
https://services.odata.org/V3/Northwind/Northwind.svc/ . Select OK .

3. In Navigator , select the Orders table, and then select Transform Data to load the data into Power Query
Editor.
 NOTE
In Navigator , you can select any table name, without selecting the checkbox, to see a preview.

Expand the order data

You can use table references to build queries when connecting to data sources with multiple tables, such as
relational databases or the Northwind OData feed. The Orders table contains references to several related tables.
You can use the expand operation to add the ProductID , UnitPrice , and Quantity columns from the related
Order_Details table into the subject (Orders ) table.
1. Scroll to the right in the Orders table until you see the Order_Details column. It contains references to
another table and not data.
2. Select the Expand icon ( ) in the Order_Details column header.
3. In the drop-down menu:
a. Select (Select All Columns) to clear all columns.
b. Select ProductID , UnitPrice , and Quantity , and then select OK .

After you expand the Order_Details table, three new nested table columns replace the Order_Details column.
There are new rows in the table for each order's added data.

Create a custom calculated column

Power Query Editor lets you create calculations and custom fields to enrich your data. You'll create a custom
column that multiplies the unit price by item quantity to calculate the total price for each order's line item.
1. In the Power Query Editor's Add Column ribbon tab, select Custom Column .
2. In the Custom Column dialog box, type LineTotal in the New column name field.
3. In the Custom column formula field after the = , enter [Order_Details.UnitPrice] *
[Order_Details.Quantity] . You can also select the field names from the Available columns scroll box and
select << Inser t , instead of typing them.
4. Select OK .

The new LineTotal field appears as the last column in the Orders table.

Set the new field's data type

When Power Query Editor connects to data, it makes a best guess as to each field's data type for display purposes.
A header icon indicates each field's assigned data type. You can also look under Data Type in the Home ribbon
tab's Transform group.
Your new LineTotal column has an Any data type, but it has currency values. To assign a data type, right-click the
LineTotal column header, select Change Type from the drop-down menu, and then select Fixed decimal
number .
 NOTE
You can also select the LineTotal column, then select the arrow next to Data Type in the Transform area of the Home
ribbon tab, and then select Fixed decimal number .

Clean up the orders columns

To make your model easier to work with in reports, you can delete, rename, and reorder some columns.
Your report is going to use the following columns:
OrderDate
ShipCity
ShipCountr y
Order_Details.ProductID
Order_Details.UnitPrice
Order_Details.Quantity
LineTotal
Select these columns and use Remove Other Columns as you did with the Excel data. Or, you can select the non-
listed columns, right-click on one of them, and select Remove Columns .
You can rename the columns prefixed with "Order_Details." to make them easier to read:
1. Double-click or tap and hold each column header, or right-click the column header, and select Rename from
the drop-down menu.
2. Delete the Order_Details. prefix from each name.
Finally, to make the LineTotal column easier to access, drag and drop it to the left, just to the right of the
ShipCountr y column.
Review the query steps
Your Power Query Editor actions to shape and transform data are recorded. Each action appears on the right in the
Quer y Settings pane under Applied Steps . You can step back through the Applied Steps to review your steps,
and edit, delete, or rearrange them if necessary. However, changing preceding steps is risky as that can break later
steps.
Select each of your queries in the Queries list on the left side of Power Query Editor, and review the Applied
Steps in Quer y Settings . After applying the previous data transformations, the Applied Steps for your two
queries should look like this:

TIP
Underlying the Applied Steps are formulas written in the Power Query Language, also known as the M language. To see and
edit the formulas, select Advanced Editor in the Quer y group of the Home tab of the ribbon.

Import the transformed queries

When you're satisfied with your transformed data and ready to import it into Power BI Desktop Repor t view, select
Close & Apply > Close & Apply in the Home ribbon tab's Close group.
Once the data is loaded, the queries appear in the Fields list in the Power BI Desktop Repor t view.

Manage the relationship between the datasets

Power BI Desktop doesn't require you to combine queries to report on them. However, you can use the
relationships between datasets, based on common fields, to extend, and enrich your reports. Power BI Desktop may
detect relationships automatically, or you can create them in the Power BI Desktop Manage Relationships dialog
box. For more information, see Create and manage relationships in Power BI Desktop.
The shared ProductID field creates a relationship between this tutorial's Orders and Products datasets.
1. In Power BI Desktop Repor t view, select Manage Relationships in the Home ribbon tab's Relationships
area.

2. In the Manage relationships dialog box, you can see that Power BI Desktop has already detected and listed
an active relationship between the Products and Orders tables. To view the relationship, select Edit .
 Edit Relationship opens, showing details about the relationship.

3. Power BI Desktop has autodetected the relationship correctly, so you can select Cancel and then Close .
In Power BI Desktop, on the left side, select Model to view and manage query relationships. Double-click the arrow
on the line connecting the two queries to open the Edit relationship dialog and view or change the relationship.
To get back to Repor t view from Model view, select the Repor t icon.

Create visualizations using your data

You can create different visualizations in Power BI Desktop Review View to gain data insights. Reports can have
multiple pages, and each page can have multiple visuals. You and others can interact with your visualizations to
help analyze and understand data. For more information, see Interact with a report in Editing view in Power BI
service.
You can use both of your data sets, and the relationship between them, to help visualize and analyze your sales
data.
First, create a stacked column chart that uses fields from both queries to show the quantity of each product
ordered.
1. Select the Quantity field from Orders in the Fields pane at the right, or drag it onto a blank space on the
canvas. A stacked column chart is created showing the total quantity of all products ordered.
2. To show the quantity of each product ordered, select ProductName from Products in the Fields pane, or
drag it onto the chart.
3. To sort the products by most to least ordered, select the More options ellipsis (...) at the visualization's
upper right, and then select Sor t By Quantity .
4. Use the handles at the corners of the chart to enlarge it so more product names are visible.
Next, create a chart showing order dollar amounts (LineTotal ) over time (OrderDate ).
1. With nothing selected on the canvas, select LineTotal from Orders in the Fields pane, or drag it to a blank
space on the canvas. The stacked column chart shows the total dollar amount of all orders.
2. Select the stacked chart, then select OrderDate from Orders , or drag it onto the chart. The chart now
shows line totals for each order date.
3. Drag the corners to resize the visualization and see more data.

TIP
If you only see Years on the chart and only three data points, select the arrow next to OrderDate in the Axis field of
the Visualizations pane, and select OrderDate instead of Date Hierarchy .

Finally, create a map visualization showing order amounts from each country.
1. With nothing selected on the canvas, select ShipCountr y from Orders in the Fields pane, or drag it to a
blank space on the canvas. Power BI Desktop detects that the data is country names. It then automatically
creates a map visualization, with a data point for each country with orders.
2. To make the data point sizes reflect each country's order amounts, drag the LineTotal field onto the map.
You can also drag it to Drag data fields here under Size in the Visualizations pane. The sizes of the
circles on the map now reflect the dollar amounts of the orders from each country.
Interact with your report visuals to analyze further
In Power BI Desktop, you can interact with visuals that cross-highlight and filter each other to uncover further
trends. For more information, see Filters and highlighting in Power BI reports.
Because of the relationship between your queries, interactions with one visualization affect all the other
visualizations on the page.
On the map visualization, select the circle centered in Canada . The other two visualizations filter to highlight the
Canadian line totals and order quantities.

Select a Quantity by ProductName chart product to see the map and the date chart filter to reflect that product's
data. Select a LineTotal by OrderDate chart date to see the map and the product chart filter to show that date's
data.

TIP
To deselect a selection, select it again, or select one of the other visualizations.

Complete the sales analysis report

Your completed report combines data from the Products.xlsx Excel file and the Northwind OData feed in visuals
that help you analyze different countries' order information, time frames, and products. When your report is ready,
you can upload it to Power BI service to share it with other Power BI users.

Next steps
Microsoft Learn for Power BI
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Tutorial: Analyze Facebook data by using Power BI
Desktop
5/13/2020 • 9 minutes to read • Edit Online

In this tutorial, you learn how to import data from Facebook and use it in Power BI Desktop. You'll connect and
import data from the Power BI Facebook page, apply transformations to the imported data, and use the data in
report visualizations.

WARNING
Due to Facebook App permission restrictions, the connector capabilities described in this article are not currently working
properly. We’re working with Facebook to return this functionality as soon as possible.

Connect to a Facebook page

This tutorial uses data from the Microsoft Power BI Facebook page. You don't need any special credentials to
connect and import data from this page except for a personal Facebook account.
1. Open Power BI Desktop and select Get data in the Getting Star ted dialog box, or in the Home ribbon tab,
select Get Data and then select More .
2. In the Get Data dialog box, select Facebook from the Online Ser vices group, and then select Connect .
 A dialog box appears to alert you to the risks of using a third-party service.

3. Select Continue .
4. In the Facebook dialog box, enter the page name microsoftbi as the user name , select Posts from the
Connection dropdown, and then select OK .
5. When prompted for credentials, sign in to your Facebook account, and allow Power BI access to your
account.

After you connect to the Power BI Facebook page, you see a preview of the page's posts data.

Shape and transform the imported data

Suppose you want to see and show which posts have the most comments over time, but you notice in the posts
data preview that the created_time data is hard to read and understand, and there's a lack of comments data. To
pull the most out of it, perform some shaping and cleansing of the data. To do so, use the Power BI Desktop Power
Query Editor to edit the data, before or after importing it into Power BI Desktop.
Split the date/time column
First, separate the date and time values in the created_time column to be more readable.
1. In the Facebook data preview, select Edit .

The Power BI Desktop Power Query Editor opens in a new window and displays the data preview from the
Power BI Facebook page.

2. Select the created_time column. Notice that it's a Text data type, as denoted by an ABC icon in the column
header. Right-click the header and select Split Column > By Delimiter in the drop-down list. Or, select
Split Column > By Delimiter under the Transform group in the Home tab of the ribbon.
3. In the Split Column by Delimiter dialog box, select Custom from the dropdown, enter T (the character
that starts the time part of the created_time values) in the input field, and then select OK .

The column splits into two columns that contain the strings before and after the T delimiter. The new
columns are named created_time.1 and created_time.2 , respectively. Power BI has automatically detected
and changed the data types to Date for the first column and Time for the second column, and formatted the
date and time values to be more readable.
4. Rename the two columns. Select the created_time.1 column, and then select Rename in the Any Column
group of the Transform tab in the ribbon. Or, double-click the column header and enter the new column
name, created_date . Repeat for the created_time.2 column, and rename it created_time .

Expand the nested column

Now that the date and time data are as you want them, you can expose comments data by expanding a nested
column.
1. Select the icon at the top of the object_link column to open the Expand/Aggregate dialog box. Select
connections , and then select OK .
 The column heading changes to object_link .connections .
2. Select the icon at the top of the object_link .connections column, select comments , and then select
OK . The column heading changes to object_link .connections.comments .
3. Select the icon at the top of the object_link .connections.comments column, and this time select
Aggregate instead of Expand in the dialog box. Select # Count of id , and then select OK .

The column now displays the number of comments for each message.
4. Rename the Count of object_link .connections.comments.id column to Number of comments .
5. Select the down arrow next to the Number of comments column header and select Sor t Descending to
see the posts sorted from most to fewest comments.

Review query steps

As you shape and transform data in the Power Query Editor, each step is recorded in the Applied Steps area of the
Quer y Settings pane at the right side of the Power Quer y Editor window. You can step back through the
Applied Steps to see exactly what changes you made, and edit, delete, or rearrange them if necessary. Use caution
when modifying these steps, because changing preceding steps can break later steps.
After applying the data transformations so far, your Applied Steps should appear as follows:

TIP
Underlying the Applied Steps are formulas written in the Power Query M formula language. To see and edit the formulas,
select Advanced Editor in the Quer y group of the Home tab of the ribbon.

Import the transformed data

When you're satisfied with the data, select Close & Apply > Close & Apply in the Home tab of the ribbon to
import it into Power BI Desktop.

A dialog box displays the progress of loading the data into the Power BI Desktop data model.

Once the data is loaded, it appears in the Repor t view as a new query in the Fields pane.
Use the data in report visualizations
Now that you have imported data from the Facebook page, you can quickly and easily gain insights about your
data by using visualizations. Creating a visualization is easy, just select a field or drag it from the Fields pane onto
the report canvas.
Create a bar chart
1. In Power BI Desktop Repor t view, select message from the Fields pane, or drag it onto the report canvas. A
table showing all post messages appears on the canvas.

2. With that table selected, also select Number of comments from the Fields pane, or drag it into the table.
3. Select the Stacked bar char t icon in the Visualizations pane. The table changes to a bar chart showing
the number of comments per post.
4. Select More options (...) next to the visualization, and then select Sor t by > Number of comments to
sort the table by descending number of comments.
Notice that the most comments were associated with (Blank) messages (these posts may have been stories,
links, videos, or other non-text content).
5. To filter out the blank rows, select message is (All) from the Filters pane, select Select all , and then select
(Blank) to deselect it.
The Filters pane entry changes to message is not (Blank) , and the (Blank) row disappears from the chart
visualization.

Format the chart

The visualization is getting more interesting, but you can't see much of the post text in the chart. To show more of
the post text:
1. Use the handles on the chart visualization to resize the chart to be as large as possible.
2. With the chart selected, select the Format icon (paint roller) in the Visualizations pane.
3. Select the down arrow next to Y axis , and drag the Maximum size slider all the way to the right (50% ).
4. Reduce the Text size to 10 pt to fit more text.
 The chart now shows more of the post content.

The x axis (number of comments) of the chart doesn't show exact values, and looks lost at the bottom of the chart.
Let's use data labels instead:
1. Select the Format icon, and then set the slider for X axis to Off .
2. Select the Data labels slider to On .
Now the chart shows the exact number of comments for each post.

Edit the data type

That's better, but all the data labels have a .0 decimal place, which is distracting and misleading, because Number
of posts must be a whole number. To fix them, you need to change the data type of the Number of posts column
to Whole Number :
1. Right-click Quer y1 in the Fields pane, or hover over it and select More options (...).
2. From the context menu, select Edit quer y . Or, select Edit Queries > Edit Queries from the External data
group of the Home tab in the ribbon.
3. From the Power Quer y Editor window, select the Number of comments column, and change the data
type by following one of these steps:
Select the 1.2 icon next to the Number of comments column header, and then select Whole number
from the drop-down list
Right-click the column header, and then select Change Type > Whole Number .
Select Data type: Decimal Number in the Transform group of the Home tab, or in the Any Column
group of the Transform tab, and then select Whole Number .
The icon in the column header changes to 123 , denoting a Whole Number data type.

4. To apply the changes, select File > Close & Apply , or File > Apply to keep the Power Quer y Editor
window open.
After the changes load, the data labels on the chart become whole numbers.
Create a date slicer
Suppose you want to visualize the number of comments on posts over time. You can create a slicer visualization to
filter the chart data to different time frames.
1. Select a blank area of the canvas, and then select the Slicer icon in the Visualizations pane.
A blank slicer visualization appears.

2. Select the created_date field from the Fields pane, or drag it into the new slicer.
The slicer changes to a date range slider, based on the field's Date data type.
3. Move the slider handles to select different date ranges, and note how the chart data filters accordingly. You
can also select the date fields in the slicer and type in specific dates, or choose them from a calendar popup.

Format the visualizations

Give the chart a more descriptive and attractive title:
1. With the chart selected, select the Format icon in the Visualizations pane, and then select the drop-down
arrow next to Title to expand it.
2. Change the Title text to Comments per post .
3. Select the drop-down arrow next to Font color , and select a green color to match the green bars of the
visualization.
4. Increase the Text size to 10 pt , and change the Font family to Segoe (Bold) .
5. Experiment with other formatting options and settings to change the appearance of your visualizations.
Create more visualizations
As you can see, it's easy to customize visualizations in your report to present the data in ways that you want. For
example, try using the imported Facebook data to create this line chart showing the number of comments over
time.

Power BI Desktop provides a seamless end-to-end experience, from getting data from a wide range of data sources
and shaping it to meet your analysis needs, to visualizing this data in rich and interactive ways. When your report is
ready, you can upload it to the Power BI service and create dashboards based on it to share with other Power BI
users.

Next steps
Read other Power BI Desktop tutorials
Watch Power BI Desktop videos
Visit the Power BI Forum
Read the Power BI Blog
 Implement row-level security in an Analysis Services
tabular model
9/9/2020 • 6 minutes to read • Edit Online

Using a sample dataset to work through the steps below, this tutorial shows you how to implement row-level
security in an Analysis Services Tabular Model and use it in a Power BI report.
Create a new security table in the AdventureworksDW2012 database
Build the tabular model with necessary fact and dimension tables
Define user roles and permissions
Deploy the model to an Analysis Services tabular instance
Build a Power BI Desktop report that displays data tailored to the user accessing the report
Deploy the report to Power BI service
Create a new dashboard based on the report
Share the dashboard with your coworkers
This tutorial requires the AdventureworksDW2012 database.

Task 1: Create the user security table and define data relationship
You can find many articles describing how to define row-level dynamic security with the SQL Server Analysis
Services (SSAS) tabular model. For our sample, we use Implement Dynamic Security by Using Row Filters.
The steps here require using the AdventureworksDW2012 relational database.
1. In AdventureworksDW2012, create the DimUserSecurity table as shown below. You can use SQL Server
Management Studio (SSMS) to create the table.

2. Once you create and save the table, you need to establish the relationship between the DimUserSecurity
table's SalesTerritoryID column and the DimSalesTerritory table's SalesTerritoryKey column, as shown
below.
In SSMS, right-click DimUserSecurity , and select Design . Then select Table Designer > Relationships....
When done, save the table.
3. Add users to the table. Right-click DimUserSecurity and select Edit Top 200 Rows . Once you've added
users, the DimUserSecurity table should appear similar to the following example:

You'll see these users in upcoming tasks.

4. Next, do an inner join with the DimSalesTerritory table, which shows the user associated region details. The
SQL code here does the inner join, and the image shows how the table then appears.

select b.SalesTerritoryCountry, b.SalesTerritoryRegion, a.EmployeeID, a.FirstName, a.LastName,

a.UserName from [dbo].[DimUserSecurity] as a join [dbo].[DimSalesTerritory] as b on a.[SalesTerritoryID]
= b.[SalesTerritoryKey]

The joined table shows who is responsible for each sales region, thanks to the relationship created in Step 2.
For example, you can see that Rita Santos is responsible for Australia.

Task 2: Create the tabular model with facts and dimension tables
Once your relational data warehouse is in place, you need to define the tabular model. You can create the model
using SQL Server Data Tools (SSDT). For more information, see Create a New Tabular Model Project.
1. Import all the necessary tables into the model as shown below.
2. Once you've imported the necessary tables, you need to define a role called SalesTerritoryUsers with Read
permission. Select the Model menu in SQL Server Data Tools, and then select Roles . In Role Manager ,
select New .
3. Under Members in the Role Manager , add the users that you defined in the DimUserSecurity table in Task
1.
4. Next, add the proper functions for both DimSalesTerritory and DimUserSecurity tables, as shown below
under Row Filters tab.
5. The LOOKUPVALUE function returns values for a column in which the Windows user name matches the one
the USERNAME function returns. You can then restrict queries to where the LOOKUPVALUE returned values
match ones in the same or related table. In the DAX Filter column, type the following formula:

=DimSalesTerritory[SalesTerritoryKey]=LOOKUPVALUE(DimUserSecurity[SalesTerritoryID],
DimUserSecurity[UserName], USERNAME(), DimUserSecurity[SalesTerritoryID],
DimSalesTerritory[SalesTerritoryKey])

In this formula, the LOOKUPVALUE function returns all values for the DimUserSecurity[SalesTerritoryID]
column, where the DimUserSecurity[UserName] is the same as the current logged on Windows user name,
and DimUserSecurity[SalesTerritoryID] is the same as the DimSalesTerritory[SalesTerritoryKey] .

IMPORTANT
When using row-level security, the DAX function USERELATIONSHIP is not supported.

The set of Sales 's LOOKUPVALUE returns is then used to restrict the rows shown in the
SalesTerritoryKey
DimSalesTerritory . Only rows where the SalesTerritoryKey value is in the IDs that the LOOKUPVALUE
function returns are displayed.
6. For the DimUserSecurity table, in the DAX Filter column, add the following formula:

=FALSE()

This formula specifies that all columns resolve to false ; meaning DimUserSecurity table columns can't be
queried.
Now you need to process and deploy the model. For more information, see Deploy.

Task 3: Add Data Sources within your On-premises data gateway

Once your tabular model is deployed and ready for consumption, you need to add a data source connection to
your on-premises Analysis Services tabular server.
1. To allow the Power BI service access to your on-premises analysis service, you need an on-premises data
gateway installed and configured in your environment.
2. Once the gateway is correctly configured, you need to create a data source connection for your Analysis
Services tabular instance. For more information, see Manage your data source - Analysis Services.
With this procedure complete, the gateway is configured and ready to interact with your on-premises Analysis
Services data source.

Task 4: Create report based on analysis services tabular model using

Power BI desktop
1. Start Power BI Desktop and select Get Data > Database .
2. From the data sources list, select the SQL Ser ver Analysis Ser vices Database and select Connect .
3. Fill in your Analysis Services tabular instance details and select Connect live . Then select OK .

With Power BI, dynamic security works only with a live connection.
4. You can see that the deployed model is in the Analysis Services instance. Select the respective model and
then select OK .
Power BI Desktop now displays all the available fields, to the right of the canvas in the Fields pane.
5. In the Fields pane, select the SalesAmount measure from the FactInternetSales table and the
SalesTerritor yRegion dimension from the SalesTerritor y table.
6. To keep this report simple, we won't add any more columns right now. To have a more meaningful data
 representation, change the visualization to Donut char t .

7. Once your report is ready, you can directly publish it to the Power BI portal. From the Home ribbon in Power
BI Desktop, select Publish .

Task 5: Create and share a dashboard

You've created the report and published it to the Power BI service. Now you can use the example created in
previous steps to demonstrate the model security scenario.
In the role as Sales Manager, the user Grace can see data from all the different sales regions. Grace creates this
report and publishes it to the Power BI service. This report was created in the previous tasks.
Once Grace publishes the report, the next step is to create a dashboard in the Power BI service called
TabularDynamicSec based on that report. In the following image, notice that Grace can see the data corresponding
to all the sales region.
Now Grace shares the dashboard with a colleague, Rita, who is responsible for the Australia region sales.

When Rita logs in to the Power BI service and views the shared dashboard that Grace created, only sales from the
Australia region are visible.
Congratulations! The Power BI service shows the dynamic row-level security defined in the on-premises Analysis
Services tabular model. Power BI uses the EffectiveUserName property to send the current Power BI user credential
to the on-premises data source to run the queries.

Task 6: Understand what happens behind the scenes

This task assumes you're familiar with SQL Server Profiler, since you need to capture a SQL Server profiler trace on
your on-premises SSAS tabular instance.
The session gets initialized as soon as the user, Rita, accesses the dashboard in the Power BI service. You can see
that the salesterritor yusers role takes an immediate effect with the effective user name as [email protected]
 <PropertyList><Catalog>DefinedSalesTabular</Catalog><Timeout>600</Timeout><Content>SchemaData</Content>
<Format>Tabular</Format><AxisFormat>TupleFormat</AxisFormat><BeginRange>-1</BeginRange><EndRange>-1</EndRange>
<ShowHiddenCubes>false</ShowHiddenCubes><VisualMode>0</VisualMode>
<DbpropMsmdFlattened2>true</DbpropMsmdFlattened2><SspropInitAppName>PowerBI</SspropInitAppName>
<SecuredCellValue>0</SecuredCellValue><ImpactAnalysis>false</ImpactAnalysis>
<SQLQueryMode>Calculated</SQLQueryMode><ClientProcessID>6408</ClientProcessID><Cube>Model</Cube>
<ReturnCellProperties>true</ReturnCellProperties><CommitTimeout>0</CommitTimeout>
<ForceCommitTimeout>0</ForceCommitTimeout><ExecutionMode>Execute</ExecutionMode>
<RealTimeOlap>false</RealTimeOlap><MdxMissingMemberMode>Default</MdxMissingMemberMode>
<DisablePrefetchFacts>false</DisablePrefetchFacts><UpdateIsolationLevel>2</UpdateIsolationLevel>
<DbpropMsmdOptimizeResponse>0</DbpropMsmdOptimizeResponse><ResponseEncoding>Default</ResponseEncoding>
<DirectQueryMode>Default</DirectQueryMode><DbpropMsmdActivityID>4ea2a372-dd2f-4edd-a8ca-
1b909b4165b5</DbpropMsmdActivityID><DbpropMsmdRequestID>2313cf77-b881-015d-e6da-
eda9846d42db</DbpropMsmdRequestID><LocaleIdentifier>1033</LocaleIdentifier>
<EffectiveUserName>[email protected]</EffectiveUserName></PropertyList>

Based on the effective user name request, Analysis Services converts the request to the actual contoso\rita
credential after querying the local Active Directory. Once Analysis Services gets the credential, Analysis Services
returns the data the user has permission to view and access.
If more activity occurs with the dashboard, with SQL Profiler you would see a specific query coming back to the
Analysis Services tabular model as a DAX query. For example, if Rita goes from the dashboard to the underlying
report, the following query occurs.

You can also see below the DAX query that is getting executed to populate report data.

EVALUATE
ROW(
"SumEmployeeKey", CALCULATE(SUM(Employee[EmployeeKey]))
)

<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis">``
<Catalog>DefinedSalesTabular</Catalog>
<Cube>Model</Cube>
<SspropInitAppName>PowerBI</SspropInitAppName>
<EffectiveUserName>[email protected]</EffectiveUserName>
<LocaleIdentifier>1033</LocaleIdentifier>
<ClientProcessID>6408</ClientProcessID>
<Format>Tabular</Format>
<Content>SchemaData</Content>
<Timeout>600</Timeout>
<DbpropMsmdRequestID>8510d758-f07b-a025-8fb3-a0540189ff79</DbpropMsmdRequestID>
<DbPropMsmdActivityID>f2dbe8a3-ef51-4d70-a879-5f02a502b2c3</DbPropMsmdActivityID>
<ReturnCellProperties>true</ReturnCellProperties>
<DbpropMsmdFlattened2>true</DbpropMsmdFlattened2>
<DbpropMsmdActivityID>f2dbe8a3-ef51-4d70-a879-5f02a502b2c3</DbpropMsmdActivityID>
</PropertyList>

Considerations
On-premises row-level security with Power BI is only available with live connection.
Any changes in the data after processing the model would be immediately available for the users accessing
the report with live connection from the Power BI service.
 Tutorial: Connect to a GitHub repo with Power BI
5/13/2020 • 3 minutes to read • Edit Online

In this tutorial, you connect to real data in the GitHub service with Power BI, and Power BI automatically creates
dashboards and reports. You connect to the Power BI content public repository (also known as a repo) and see
answers to questions like: How many people contribute to the Power BI public content? Who contributes the most?
Which day of the week has the most contributions? And other questions.

In this tutorial, you complete the following steps:

Sign up for a GitHub account, if you don't have one yet
Sign in to your Power BI account, or sign up, if you don't have one yet
Open the Power BI service
Find the GitHub app
Enter the information for the Power BI public GitHub repo
View the dashboard and report with GitHub data
Clean up resources by deleting the app
If you're not signed up for Power BI, sign up for a free trial before you begin.

Prerequisites
To complete this tutorial, you need a GitHub account, if you don't already have one.
Sign up for a GitHub account.

How to connect
1. Sign in to the Power BI service ( https://app.powerbi.com ).
2. In the nav pane, select Apps , then Get apps .
3. Select Apps , type GitHub in the search box > Get it now .

4. In Install this Power BI App? select Install .

5. In Your new app is ready , select Go to app .
 6. In Get star ted with your new app , select Connect .

7. Enter the repository name and repository owner of the repo. The URL for this repo is
https://github.com/MicrosoftDocs/powerbi-docs, so Repositor y Owner is MicrosoftDocs , and
Repositor y is powerbi-docs .

8. Enter the GitHub credentials you created. Power BI might skip this step if you're already signed in to GitHub
in your browser.
9. For Authentication Method , keep oAuth2 selected > Sign In .
10. Follow the GitHub authentication screens. Grant Power BI permission to the GitHub data.
Now Power BI can connect with GitHub and connect to the data. The data is refreshed once a day.
11. After Power BI imports the data, you see the contents of your new GitHub workspace.
12. Select the arrow next to the workspace name in the nav pane. You see the workspace contains a dashboard
and a report.
13. Select More options (...) next to the dashboard name > Rename > type GitHub dashboard .

14. Select the global navigation icon to minimize the nav pane, so you have more room.

15. Select your GitHub dashboard.

The GitHub dashboard contains live data, so the values you see may be different.
Ask a question
1. Put your cursor in Ask a question about your data . Power BI offers Questions to get your star ted .
2. Select how many users are there .
3. In between how many and users are there , type pull requests per .
Power BI creates a bar chart showing the number of pull requests per person.

4. Select the pin to pin it to your dashboard, then Exit Q&A .

View the GitHub report

1. In the GitHub dashboard, select the column chart Pull Requests by Month to open the related report.

2. Select a user name in the Total pull requests by user chart. In this example, we see most of their hours
were in February.
3. Select the Punch Card tab to view the next page in the report.

Apparently Tuesday at 3 pm is the most common time and day of the week for commits, when people check
in their work.

Clean up resources
Now that you've finished the tutorial, you can delete the GitHub app.
1. In the nav pane, select Apps .
2. Hover over the GitHub tile and select the Delete garbage can.
Next steps
In this tutorial, you've connected to a GitHub public repo and gotten data, which Power BI has formatted in a
dashboard and report. You've answered some questions about the data by exploring the dashboard and report.
Now you can learn more about connecting to other services, such as Salesforce, Microsoft Dynamics, and Google
Analytics.
Connect to the online services you use
 Tutorial: Use Cognitive Services in Power BI
5/13/2020 • 5 minutes to read • Edit Online

Power BI provides access to a set of functions from Azure Cognitive Services to enrich your data in the self-service
data prep for Dataflows. The services that are supported today are Sentiment Analysis, Key Phrase Extraction,
Language Detection, and Image Tagging. The transformations are executed on the Power BI service and do not
require an Azure Cognitive Services subscription. This feature requires Power BI Premium.
Cognitive Services transforms are supported in the Self-Service Data Prep for Dataflows. Use the step-by-step
examples for text analytics and image tagging below to get started.
In this tutorial, you learn how to:
Import data into a dataflow
Score sentiment and extract key phrases of a text column in a dataflow
Connect to the results from Power BI Desktop

Prerequisites
To complete this tutorial, you need the following:
A Power BI account. If you're not signed up for Power BI, sign up for a free trial before you begin.
Access to a Power BI Premium capacity with the AI workload enabled. This workload will be turned off by default
during preview. If you are in on a Premium capacity and AI Insights are not showing up, contact your Premium
capacity admin to enable the AI workload in the admin portal.

Text analytics
Follow the steps in this section to complete the text analytics portion of the tutorial.
Step 1: Apply sentiment scoring in Power BI Service
To get started, navigate to a Power BI workspace with Premium capacity and create a new dataflow using the
Create button in the upper right of the screen.

The dataflow dialog shows you the options for creating a new dataflow, select Add new entities. Next, choose
Text/CSV from the menu of data sources.
Paste this URL into the URL field: https://pbiaitutorials.blob.core.windows.net/textanalytics/FabrikamComments.csv
and click Next.

The data is now ready to use for text analytics, and we can use Sentiment Scoring and Key Phrase Extraction on the
customer comments column.
In Power Query Editor, select AI Insights
Expand the Cognitive Ser vices folder and select the function you would like to use. This example is scoring the
sentiment of the comment column, but you can follow the same steps to try out Language Detection and Key
Phrase Extraction.

Once a function is selected, the required and optional fields will show. To score the sentiment of the example
reviews, select the reviews column as text input. Culture info is an optional input and requires an ISO format. For
example, enter 'en' if you want the text to be treated as English. When the field is left blank, Power BI will first detect
the language of the input value before scoring the sentiment.
Now select Invoke to run the function. A new column with the sentiment score for each row is added to the table.
You can go back to AI insights to extract key phrases of the review text in the same way.
Once you are finished with the transformations, change the query name to 'Customer comments' and select Done.

Next, Save the dataflow and name it Fabrikam. Select the Refresh Now button that pops up after saving the
dataflow.
Once the dataflow is saved and refreshed, you can use it in a Power BI report.
Step 2: Connect from Power BI Desktop
Open Power BI Desktop. In the Home ribbon, select Get Data.
Navigate to the Power BI dataflows (Beta ) in the Power BI section and select Connect.
As this is a preview feature, the connector will ask you to accept the preview conditions. After accepting these, sign
in with your organization account.

Select the dataflow you have just created. Navigate to the Customer comments table and click Load.
Now the data is loaded you can start building a report.

Image tagging
Navigate to a Power BI workspace with Premium capacity. Create a new dataflow using the Create button in the
upper right of the screen.

Select Add new entities .

Once you are asked to choose a data source, select Blank quer y.

Copy the query below in the query editor and click next. You can replace the URL paths below with other images or
add more rows. The Web.Contents function imports the image URL as binary. If you have a data source with
images stored as binary, you can also use that directly.

let
Source = Table.FromRows({
{ Web.Contents("https://images.pexels.com/photos/87452/flowers-background-butterflies-beautiful-87452.jpeg")
},
{ Web.Contents("https://upload.wikimedia.org/wikipedia/commons/5/53/Colosseum_in_Rome%2C_Italy_-
_April_2007.jpg") }}, { "Image" })
in
Source
When prompted for credentials, select anonymous.

You see the following image.

You're prompted for credentials for each individual web page.
Select AI Insights in the query editor.

Next, sign in with your organizational account .

Select the Tag Images function, enter [Binary] in the column field and en in the culture info field.

NOTE
You currently cannot pick a column using a dropdown, which will be resolved as soon as possible during the private preview.

In the function editor, remove the quotation marks around the column name.
 NOTE
Removing the quotation marks is a temporary workaround, which will be resolved as soon as possible during preview.

The function returns a record with both the tags in comma-separated format and as a json record. Select the
expand-button to add one or both as columns to the table.

Select Done and save the dataflow. Once you have refreshed the dataflow one, you can connect to it from Power BI
Desktop using the Dataflows connectors. (See steps on page 5 of this document).

Clean up resources
When no longer needed, delete the query by right-clicking the query name in the Power Query editor and selecting
Delete .

Next steps
In this tutorial, you applied sentiment scoring and image tagging functions on a Power BI dataflow. To learn more
about Cognitive Services in Power BI, read the following articles.
Cognitive Services in Azure
Get started with self-service data prep on dataflows
Learn more about Power BI Premium
You might also be interested in the following articles.
Tutorial: Invoke a Machine Learning Studio (classic) model in Power BI (Preview)
Azure Machine Learning integration in Power BI (Preview)
Cognitive Services in Power BI (Preview)
 Tutorial: Invoke a Machine Learning Studio (classic)
model in Power BI (Preview)
5/13/2020 • 7 minutes to read • Edit Online

In this tutorial, we walk through the experience of incorporating insights from an Azure Machine Learning
Studio (classic) model into Power BI. This tutorial includes guidance for granting a Power BI user access to an
Azure ML model, creating a dataflow, and applying the insights from the Azure ML model to your dataflow. It also
references the quickstart guide for creating an Azure ML model if you don't already have a model.
The tutorial takes you through the following steps:
Create and publish an Azure Machine Learning model
Grant access to a Power BI user to use the model
Create a dataflow
Apply insights from the Azure ML model to the dataflow

Create and publish an Azure ML model

Follow the instructions at Walkthrough Step 1: Create a Machine Learning Studio (classic) workspace to create a
Machine Learning workspace.
You can use these steps with any Azure ML model or dataset you already have. If you don't have a published model,
you can create a model in minutes by referring to Create your first data science experiment in Azure Machine
Learning Studio (classic), which sets up an Azure ML model for Automobile Price Prediction.
Follow the steps at Deploy an Azure Machine Learning Studio (classic) web service to publish the Azure ML model
as a web service.

Grant a Power BI user access

To access an Azure ML model from Power BI, you must have Read access to the Azure subscription and the
resource group and Read access to the Azure Machine Learning Studio (classic) web service for Machine Learning
Studio (classic) models. For Azure Machine Learning model, you need Read access to the Machine Learning
workspace.
The following steps assume you are the coadministrator for the Azure subscription and resource group to which
the model was published.
Sign in to the Azure portal, and navigate to the Subscriptions page, which you can find using the All Ser vices
list in the nav pane menu.
Select the Azure subscription that you used for publishing the model, and select Access Control (IAM) . Next
select Add role assignment , then select the Reader role, and select the Power BI user. Select Save when you're
done. The following image shows these selections.

Then repeat the steps above to grant Contributor role access to the Power BI user for the specific Machine
Learning web service to which the Azure ML model has been deployed.

Create a dataflow
Get data for creating the dataflow
Sign in to the Power BI service with the user credentials for whom you granted access to the Azure ML model in the
previous step.
This step assumes you have the data you want to score with your Azure ML model in CSV format. If you used the
Automobile Pricing Experiment to create the model in the Machine Learning Studio (classic), the dataset for is
shared in the following link:
Azure Learning Studio (classic) sample model
Create a dataflow
To create the entities in your dataflow, sign in to the Power BI service and navigate to a workspace on your
dedicated capacity that has the AI preview enabled.
If you don't already have a workspace, you can create one by selecting Workspaces in the left menu, and then
select Create workspace in the panel at the bottom. This opens a panel to enter the workspace details. Enter a
workspace name, and then select Save .

After the workspace has been created, you can select Skip in the bottom right of the Welcome screen.

Select the Dataflows (preview) tab, and then select the Create button at the top right of the workspace, and then
select Dataflow .
Select Add new entities , which launches Power Quer y Editor in the browser.

Select Text/CSV File as a data source.

In the next screen, you're prompted to connect to a data source. Paste the link to the data you used to create your
Azure ML model. If you used the Automotive Pricing data, you can paste the following link into the File path or
URL box and then Next .
https://raw.githubusercontent.com/MicrosoftLearning/Principles-of-Machine-Learning-
Python/master/Module7/Automobile%20price%20data%20_Raw_.csv

Power Query Editor shows a preview of the data from the CSV file. Select Transform Table from the command
ribbon and then select Use first row as headers . This adds the Promoted headers query step into the Applied
steps pane on the right. You can also rename the query to a friendlier name, such as Automobile Pricing using the
pane on the right.
Our source dataset has unknown values set to '?'. To clean this, we can replace '?' with '0' to avoid errors later for
simplicity. To do this, select the columns normalized-losses, bore, stroke, compression-ratio, horsepower, peak-rpm
and price by clicking on their name in the column headers, then click on 'Transform columns' and select 'Replace
values'. Replace '?' with '0'.

All the columns in the table from a Text/CSV source are treated as text columns. Next, we need to change the
numeric columns to their correct data types. You can do this in Power Query by clicking on the data type symbol in
the column header. Change the columns to the below types:
Whole number : symboling, normalized-losses, curb-weight, engine-size, horsepower, peak-rpm, city-mpg,
highway-mpg, price
Decimal number : wheel-base, length, width, height, bore, stroke, compression-ratio
Select Done to close Power Query Editor. This will show the entities list with the Automobile Pricing data we added.
Select Save in the top right corner, provide a name for the dataflow, and then select Save .

Refresh the dataflow

Saving the dataflow displays a notification that your dataflow was saved. Select Refresh now to ingest data from
the source into the dataflow.
Select Close in the upper right corner and wait for the dataflow refresh to complete.
You can also refresh your dataflow using the Actions commands. The dataflow displays the timestamp when the
refresh is completed.

Apply insights from your Azure ML model

To access the Azure ML model for Automobile Price Prediction, you can edit the Automobile Pricing entity for which
we want to add the predicted price.
Selecting the Edit icon opens Power Query Editor for the entities in your dataflow.

Select the AI Insights button in the ribbon, and then select the Azure Machine Learning Models folder from the
nav pane menu.
The Azure ML models to which you've been granted access are listed as Power Query functions with a prefix
AzureML. When you click on the function corresponding to the AutomobilePricePrediction model, the parameters
for the model's web service are listed as function parameters.
To invoke an Azure ML model, you can specify any of the selected entity's columns as an input from the drop-down.
You can also specify a constant value to be used as an input by toggling the column icon to the left of the input
dialog. When a column name that matches one of the function parameter names, then the column is automatically
suggested as an input. If the column name doesn't match, you can select it from the drop-down.
In the case of the Automobile Pricing Prediction model, the input parameters are:
make
 body-style
wheel-base
engine-size
horsepower
peak-rpm
highway-mpg
In our case, since our table matches the original dataset used to train the model, all the parameters have the correct
columns already selected.

Select Invoke to view the preview of the Azure ML model's output as a new column in the entity table. You'll also
see the model invocation as an applied step for the query.
The output of the model is shown as a record in the output column. You can expand the column to produce
individual output parameters in separate columns. In our case, we're only interested in the Scored Labels which
contains the predicted price of the automobile. So we deselect the rest, and select OK .
The resulting Scored Labels column has the price prediction from the Azure ML model.

Once you save your dataflow, the Azure ML model will be automatically invoked when the dataflow is refreshed for
any new or updated rows in the entity table.

Clean up resources
If you no longer need the Azure resources you created using this article, delete them to avoid incurring any
charges. You can also delete the dataflows you created, if you no longer require them.

Next steps
In this tutorial, you created a simple experiment using Azure Machine Learning Studio (classic) using a simple
dataset using these steps:
Create and publish an Azure Machine Learning model
 Grant access to a Power BI user to use the model
Create a dataflow
Apply insights from the Azure ML model to the dataflow
For more information about Azure Machine Learning integration in Power BI, see Azure Machine Learning
integration in Power BI (Preview).
 Tutorial: Build a Machine Learning model in Power BI
9/9/2020 • 9 minutes to read • Edit Online

In this tutorial article, you use Automated Machine Learning to create and apply a binary prediction model in
Power BI. The tutorial includes guidance for creating a Power BI dataflow, and using the entities defined in the
dataflow to train and validate a machine learning model directly in Power BI. We then use that model for scoring
new data to generate predictions.
First, you'll create a Binary Prediction machine learning model, to predict the purchase intent of online shoppers
based on a set of their online session attributes. A benchmark machine learning dataset is used for this exercise.
Once a model is trained, Power BI will automatically generate a validation report explaining the model results. You
can then review the validation report and apply the model to your data for scoring.
This tutorial consists of following steps:

Create a dataflow with the input data

Create and train a machine learning model
Review the model validation report
Apply the model to a dataflow entity
Using the scored output from the model in a Power BI report

Create a dataflow with the input data

The first part of this tutorial is to create a dataflow with input data. That process takes a few steps, as shown in the
following sections, beginning with getting data.
Get data
The first step in creating a dataflow is to have your data sources ready. In our case, we use a machine learning
dataset from a set of online sessions, some of which culminated in a purchase. The dataset contains a set of
attributes about these sessions, which we'll use for training our model.
You can download the dataset from the UC Irvine website. We also have this available, for the purpose of this
tutorial, from the following link: online_shoppers_intention.csv.
Create the entities
To create the entities in your dataflow, sign into the Power BI service and navigate to a workspace on your dedicated
capacity that has AI enabled.
If you don't already have a workspace, you can create one by selecting Workspaces in the nav pane menu in the
Power BI service, and select Create workspace at the bottom of the panel that appears. This opens a panel on the
right to enter the workspace details. Enter a workspace name and select Advanced . Confirm that the workspace
uses Dedicated Capacity using the radio button, and that it's assigned to a dedicated capacity instance that has the
AI preview turned on. Then select Save .
Once the workspace is created, you can select Skip in the bottom right of the Welcome screen, as shown in the
following image.

Select the Create button at the top right of the workspace, and then select Dataflow .
Select Add new entities . This launches a Power Quer y editor in the browser.

Select Text/CSV File as a data source, shown in the following image.

In the Connect to a data source page that appears next, paste the following link to the
online_shoppers_intention.csv into the File path or URL box, and then select Next .
https://raw.githubusercontent.com/santoshc1/PowerBI-AI-
samples/master/Tutorial_AutomatedML/online_shoppers_intention.csv

The Power Query Editor shows a preview of the data from the CSV file. You can rename the query to a friendlier
name by changing the value in the Name box found in the right pane. For example, you could change the Query
name to Online Visitors.
Power Query automatically infers the type of columns. You can change the column type by clicking on the attribute
type icon at the top of the column header. In this example, we change the type of the Revenue column to True/False.

Select the Save & close button to close Power Query Editor. Provide a name for the dataflow, and then select Save
on the dialog, as shown in the following image.
Create and train a machine learning model
To add a machine learning model, Select the Apply ML model button in the Actions list for the base entity that
contains your training data and label information, and then select Add a machine learning model .

The first step for creating our machine learning model is to identify the historical data including the outcome field
that you want to predict. The model will be created by learning from this data.
In the case of the dataset we're using, this is the Revenue field. Select Revenue as the 'Outcome field' value and
then select Next .
Next, we must select the type of machine learning model to create. Power BI analyzes the values in the outcome
field that you've identified and suggests the types of machine learning models that can be created to predict that
field.
In this case since we're predicting a binary outcome of whether a user will make a purchase or not, Binary
Prediction is recommended. Since we are interested in predicting users who will make a purchase, select True as the
Revenue outcome that you're most interested in. Additionally, you can provide friendly labels for the outcomes to
be used in the automatically generated report that will summarize the results of the model validation. Then select
Next.

Next, Power BI does a preliminary scan of a sample of your data and suggests the inputs that may produce more
accurate predictions. If Power BI doesn't recommend a field, an explanation would be provided next to it. You have
the option to change the selections to include only the fields you want the model to study, or you can select all the
fields by selecting the checkbox next to the entity name. Select Next to accept the inputs.
In the final step, we must provide a name for our model. Name the model Purchase Intent Prediction. You can
choose to reduce the training time to see quick results or increase the amount of time spent in training to get the
best model. Then select Save and train to start training the model.

The training process will begin by sampling and normalizing your historical data and splitting your dataset into two
new entities Purchase Intent Prediction Training Data and Purchase Intent Prediction Testing Data.
Depending on the size of the dataset, the training process can take anywhere from a few minutes to the training
time selected at the previous screen. At this point, you can see the model in the Machine learning models tab of
the dataflow. The Ready status indicates that the model has been queued for training or is under training.
You can confirm that the model is being trained and validated through the status of the dataflow. This appears as a
data refresh in progress in the Dataflows tab of the workspace.
Once the model training is completed, the dataflow displays an updated refresh time. You can confirm that the
model is trained, by navigating to the Machine learning models tab in the dataflow. The model you created
should show status as Trained and the Last Trained time should now be updated.

Review the model validation report

To review the model validation report, in the Machine learning models tab, select the View training report button in
the Actions column for the model. This report describes how your machine learning model is likely to perform.
In the Model Performance page of the report, select See top predictors to view the top predictors for your
model. You can select one of the predictors to see how the outcome distribution is associated with that predictor.
You can use the Probability Threshold slicer on the Model Performance page to examine its influence on the
Precision and Recall for the model.

The other pages of the report describe the statistical performance metrics for the model.
The report also includes a Training Details page that describes the different iterations that were run, how features
were extracted from the inputs, and the hyperparameters for the final model used.

Apply the model to a dataflow entity

Select the Apply model button at the top of the report to invoke this model. In the Apply dialog, you can specify
the target entity that has the source data to which the model should be applied.
When prompted, you must Refresh the dataflow to preview the results of your model.
Applying the model will create two new entities, with the suffix enriched <model_name> and enriched
<model_name> explanations . In our case, applying the model to the Online Visitors entity will create Online
Visitors enriched Purchase Intent Prediction which includes the predicted output from the model, and Online
Visitors enriched Purchase Intent Prediction explanations which contains top record-specific influencers for
the prediction.
Applying a Binary Prediction model adds four columns with predicted outcome, probability score, the top record-
specific influencers for the prediction, and explanation index each prefixed with the column name specified.

Once the dataflow refresh is completed, you can select the Online Visitors enriched Purchase Intent
Prediction entity to view the results.
You can also invoke any AutoML model in the workspace, directly from the Power Query Editor in your dataflow. To
access the AutoML models, select the Edit button for the entity that you want to enrich with insights from your
AutoML model, as shown in the following image.

Selecting the Edit button opens the Power Query Editor for the entities in your dataflow. Select the AI
Insights button in the ribbon.
Select the Power BI Machine Learning Models folder from the nav pane menu. All the AutoML models to which you
have access are listed here as Power Query functions. Also, the input parameters for the AutoML model are
automatically mapped as parameters of the corresponding Power Query function. Note that automatic mapping of
parameters happens only if the name and data type of the parameter is the same.
To invoke an AutoML model, you can specify any of the selected entity's columns as an input from the drop-down.
You can also specify a constant value to be used as an input by toggling the column icon to the left of the input
dialog.

Select Apply to view the preview of the AutoML model's output as a new columns in the entity table. You will also
see the model invocation as an applied step for the query.
Once you save your dataflow, the model is automatically invoked when the dataflow is refreshed, for any new or
updated rows in the entity table.

Using the scored output from the model in a Power BI report

To use the scored output from your machine learning model you can connect to your dataflow from the Power BI
desktop, using the Dataflows connector. The Online Visitors enriched Purchase Intent Prediction entity can
now be used to incorporate the predictions from your model in Power BI reports.

Next steps
In this tutorial, you created and applied a binary prediction model in Power BI using these steps:
Create a dataflow with the input data
Create and train a machine learning model
Review the model validation report
Apply the model to a dataflow entity
Using the scored output from the model in a Power BI report
For more information about Machine Learning automation in Power BI, see Automated Machine Learning in Power
BI.
 Refresh data from an on-premises SQL Server
database
5/13/2020 • 8 minutes to read • Edit Online

In this tutorial, you explore how to refresh a Power BI dataset from a relational database that exists on premises in
your local network. Specifically, this tutorial uses a sample SQL Server database, which Power BI must access
through an on-premises data gateway.
In this tutorial, you complete the following steps:
Create and publish a Power BI Desktop (.pbix) file that imports data from an on-premises SQL Server database.
Configure data source and dataset settings in Power BI for SQL Server connectivity through a data gateway.
Configure a refresh schedule to ensure your Power BI dataset has recent data.
Perform an on-demand refresh of your dataset.
Review the refresh history to analyze the outcomes of past refresh cycles.
Clean up resources by deleting the artifacts created in this tutorial.

Prerequisites
If you don't already have one, sign up for a free Power BI trial before you begin.
Install Power BI Desktop on a local computer.
Install SQL Server on a local computer, and restore the sample database from a backup. For more information
about AdventureWorks, see AdventureWorks installation and configuration.
Install an on-premises data gateway on the same local computer as SQL Server (in production, it would
typically be a different computer).

NOTE
If you're not a gateway administrator and don't want to install a gateway yourself, contact a gateway administrator in your
organization. They can create the required data source definition to connect your dataset to your SQL Server database.

Create and publish a Power BI Desktop file

Use the following procedure to create a basic Power BI report using the AdventureWorksDW sample database.
Publish the report to the Power BI service, so that you get a dataset in Power BI, which you can then configure and
refresh in subsequent steps.
1. In Power BI Desktop, on the Home tab, select Get Data > SQL Ser ver .
2. In the SQL Ser ver database dialog box, enter the Ser ver and Database (optional) names, make sure
the Data Connectivity mode is Impor t , and then select OK .
 We're not using Advanced options in this tutorial, but note that you can specify a SQL statement and set
other options like using SQL Server Failover.

3. Verify your credentials , then select Connect .

NOTE
If you're unable to authenticate, make sure you select the correct authentication method and use an account with
database access. In test environments, you might use Database authentication with an explicit username and
password. In production environments, you typically use Windows authentication. Refer to Troubleshooting refresh
scenarios and contact your database administrator for additional assistance.

4. If an Encr yption Suppor t dialog box appears, select OK .

5. In the Navigator dialog box, select the DimProduct table, then select Load .
6. In the Power BI Desktop Repor t view, in the Visualizations pane, select the Stacked column char t .

7. With the column chart selected in the report canvas, in the Fields pane select the EnglishProductName
and ListPrice fields.
8. Drag the EndDate onto Repor t level filters , and under Basic filtering select only the checkbox for
(Blank) .

The chart should now look like the following.

 Notice that the five Road-250 products are listed with the highest list price. This will change when you
update the data and refresh the report later in this tutorial.
9. Save the report with the name "AdventureWorksProducts.pbix".
10. On the Home tab select Publish > My Workspace > Select . Sign in to the Power BI service if you're asked
to do so.
11. On the Success screen, select Open 'AdventureWorksProducts.pbix' in Power BI .
Publish to Power BI

Connect a dataset to a SQL Server database

In Power BI Desktop, you connected directly to your on-premises SQL Server database, but the Power BI service
requires a data gateway to act as a bridge between the cloud and your on-premises network. Follow these steps to
add your on-premises SQL Server database as a data source to a gateway and then connect your dataset to this
data source.
1. Sign in to Power BI. In the upper-right corner, select the settings gear icon and then select Settings .

2. On the Datasets tab, select the dataset AdventureWorksProducts , so you can connect to your on-
premises SQL Server database through a data gateway.
3. Expand Gateway connection and verify that at least one gateway is listed. If you don't have a gateway, see
the Prerequisites section earlier in this tutorial for a link to the product documentation for installing and
configuring a gateway.

4. Under Actions , expand the toggle button to view the data sources and select the Add to gateway link.

NOTE
If you're not a gateway administrator and don't want to install a gateway yourself, contact a gateway administrator in
your organization. They can create the required data source definition to connect your dataset to your SQL Server
database.

5. On the Gateways management page, on the Data Source Settings tab, enter and verify the following
information, and select Add .

O P T IO N VA L UE

Data Source Name AdventureWorksProducts

Data Source Type SQL Server

 O P T IO N VA L UE

Server The name of your SQL Server instance, such as

SQLServer01 (must be identical to what you specified in
Power BI Desktop).

Database The name of your SQL Server database, such as

AdventureWorksDW (must be identical to what you
specified in Power BI Desktop).

Authentication Method Windows or Basic (typically Windows).

Username The user account you use to connect to SQL Server.

Password The password for the account you use to connect to SQL
Server.

6. On the Datasets tab, expand the Gateway connection section again. Select the data gateway you
configured, which shows a Status of running on the machine where you installed it, and select Apply .
Configure a refresh schedule
Now you've connected your dataset in Power BI to your SQL Server database on-premises through a data gateway,
follow these steps to configure a refresh schedule. Refreshing your dataset on a scheduled basis helps to ensure
that your reports and dashboards have the most recent data.
1. In the nav pane, open My Workspace > Datasets . Select the ellipsis (. . .) for the
AdventureWorksProducts dataset, then select Schedule refresh .

NOTE
Make sure you select the ellipsis for the AdventureWorksProducts dataset and not the ellipsis for the report with
the same name. The context menu of the AdventureWorksProducts report does not include a Schedule refresh
option.

2. In the Scheduled refresh section, under Keep your data up to date , set refresh to On .
3. Select an appropriate Refresh frequency , ( Daily for this example), and then under Time , select Add
another time to specify the desired refresh time (6:30 AM and PM for this example).
 NOTE
You can configure up to 8 daily time slots if your dataset is on shared capacity, or 48 time slots on Power BI Premium.

4. Leave the checkbox Send refresh failure notification emails to me enabled and select Apply .

Perform an on-demand refresh

Now that you've configured a refresh schedule, Power BI refreshes your dataset at the next scheduled time, within a
margin of 15 minutes. If you want to refresh the data sooner, such as to test your gateway and data source
configuration, perform an on-demand refresh by using the Refresh Now option in the dataset menu in the nav
pane. On-demand refreshes don't affect the next scheduled refresh time, but they count against the daily refresh
limit, mentioned in the previous section.
For illustration purposes, simulate a change to the sample data by updating the DimProduct table in the
AdventureWorksDW database using SQL Server Management Studio (SSMS).

UPDATE [AdventureWorksDW].[dbo].[DimProduct]
SET ListPrice = 5000
WHERE EnglishProductName ='Road-250 Red, 58'

Now follow these steps so the updated data can flow through the gateway connection to the dataset and into the
reports in Power BI.
1. In the Power BI Service, in the nav pane, select and expand My Workspace .
2. Under Datasets , for the AdventureWorksProducts dataset, select the ellipsis (. . .) then select Refresh
now .

Note in the upper right corner, that Power BI is preparing to perform the requested refresh.
3. Select My Workspace > Repor ts > AdventureWorksProducts . See how the updated data flowed
through, and the product with the highest list price is now Road-250 Red, 58 .

Review the refresh history

It is a good idea to check the outcomes of past refresh cycles periodically in the refresh history. Database
credentials might have expired, or the selected gateway might have been offline when a scheduled refresh was
due. Follow these steps to examine the refresh history and check for issues.
1. In the upper-right corner of the Power BI user interface, select the settings gear icon and then select
Settings .
2. Switch to Datasets and select the dataset, such as AdventureWorksProducts , you want to examine.
3. Select the Refresh histor y link to open the Refresh histor y dialog.

4. On the Scheduled tab, notice the past scheduled and on-demand refreshes with their Star t and End times,
and a Status of Completed , which indicates that Power BI performed the refreshes successfully. For failed
refreshes, you can see the error message and examine error details.

NOTE
The OneDrive tab is only relevant for datasets connected to Power BI Desktop files, Excel workbooks, or CSV files on
OneDrive or SharePoint Online, as explained in more detail in Data refresh in Power BI.

Clean up resources
If you don't want to use the sample data anymore, drop the database in SQL Server Management Studio (SSMS). If
you don't want to use the SQL Server data source, remove the data source from your data gateway. Also consider
uninstalling the data gateway if you only installed it for the purposes of completing this tutorial. You should also
delete the AdventureWorksProducts dataset and AdventureWorksProducts report that Power BI created when you
uploaded the AdventureWorksProducts.pbix file.

Next steps
In this tutorial, you've explored how to import data from an on-premises SQL Server database into a Power BI
dataset and how to refresh this dataset on a scheduled and on-demand basis to keep the reports and dashboards
that use this dataset updated in Power BI. Now you can learn more about managing data gateways and data
sources in Power BI. It might also be a good idea to review the conceptual article Data Refresh in Power BI.
Manage an on-premises data gateway
Manage your data source - Import/Scheduled Refresh
Data refresh in Power BI
 Power BI data sources
9/9/2020 • 6 minutes to read • Edit Online

The following table shows the data sources that Power BI supports for datasets, including information about
DirectQuery and the on-premises data gateway. For information about dataflows, see Connect to data sources
for Power BI dataflows.

NOTE
There are many data connectors for Power BI Desktop that require Internet Explorer 10 (or newer) for authentication.

C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Access Yes Yes No Yes 1 Yes

database

ActiveDirec Yes Yes No Yes Yes

tory

Adobe Yes Yes No No No

Analytics

Amazon Yes Yes Yes Yes No

Redshift

appFigures Yes Yes No No No

AtScale Yes Yes Yes Yes No

cubes

Azure Yes Yes Yes No No

Analysis
Services

Azure Blob Yes Yes No Yes No

Storage

Azure Yes Yes No No No

Cosmos DB

Azure Cost Yes Yes No No No

Manageme
nt

Azure Data Yes Yes Yes Yes No

Explorer
(kusto)
 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Azure Data Yes Yes No No No

Lake
Storage
Gen1

Azure Data Yes Yes No Yes No

Lake
Storage
Gen2

Azure Yes Yes No No No

DevOps

Azure Yes Yes No Yes Yes

DevOps
Server

Azure Yes Yes No No No

HDInsight
(HDFS)

Azure Yes Yes Yes No No

HDInsight
Spark

Azure SQL Yes Yes Yes Yes 2 No

Database

Azure SQL Yes Yes Yes Yes 2 No

Data
Warehouse

Azure Table Yes Yes No Yes No

Storage

BI Yes Yes Yes Yes Yes

Connector

BI360 - Yes Yes No No No

Budgeting
& Financial
Reporting

Common Yes Yes No No No

Data
Service

Data.World Yes Yes No No No

- Get
Dataset

Denodo Yes Yes Yes Yes Yes

 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Dremio Yes Yes Yes Yes Yes

Dynamics Yes Yes No No No

365
(online)

Dynamics Yes Yes No No No

365
Business
Central

Dynamics Yes Yes No No No

365
Business
Central
(on-
premises)

Dynamics Yes Yes No No No

365
Customer
Insights

Dynamics Yes Yes No No No

NAV

Emigo Data Yes Yes No No No

Source

Entersoft Yes Yes No No No

Business
Suite

Essbase Yes Yes Yes Yes Yes

Exasol Yes Yes Yes Yes Yes

Excel Yes 3 Yes 3 No Yes 3 No 4

Facebook Yes Yes No No No

File Yes Yes No Yes Yes

Folder Yes Yes No Yes Yes

GitHub Yes Yes No No No

Google Yes Yes No No No

Analytics
 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Google Yes Yes Yes No No

BigQuery

Hadoop Yes No No No No
File (HDFS)

HDInsight Yes Yes Yes No No

Interactive
Query

IBM DB2 Yes Yes Yes Yes No

IBM Yes Yes No Yes No

Informix
Database

IBM Yes Yes Yes Yes Yes

Netezza

Impala Yes Yes Yes Yes Yes

Indexima Yes Yes Yes Yes Yes

Industrial Yes Yes No No No

App Store

Information Yes Yes No No No

Grid

Intersystem Yes Yes Yes Yes Yes

s IRIS

Intune Yes Yes No No No

Data
Warehouse

Jethro Yes Yes Yes Yes Yes

ODBC

JSON Yes Yes No Yes** No 4

Kyligence Yes Yes Yes Yes Yes

Enterprise

MailChimp Yes Yes No No No

Marketo Yes Yes No No No

MarkLogic Yes Yes Yes Yes Yes

ODBC
 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Microsoft Yes Yes No No No

Azure
Consumpti
on Insights

Microsoft Yes Yes No Yes No

Exchange

Microsoft Yes Yes No No No

Exchange
Online

Microsoft Yes Yes No Yes No

Graph
Security

Mixpanel Yes Yes No No No

MySQL Yes Yes No Yes Yes

OData Yes Yes 7 No Yes No

ODBC Yes Yes No Yes Yes

OleDb Yes Yes No Yes Yes

Oracle Yes Yes Yes Yes Yes

Paxata 8 Yes Yes No Yes No

PDF Yes Yes No Yes No 4

Planview Yes Yes No No No

Enterprise
One - CTM

Planview Yes Yes No No No

Enterprise
One - PRM

Planview Yes Yes No No No

Projectplac
e

PostgreSQL Yes Yes Yes Yes No

Power BI Yes Yes No No No

dataflows
 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Power BI Yes Yes Yes No No

datasets

Power Yes Yes No No No

platform
dataflows

Python Yes Yes 5 No Yes 5 Yes

script

QubolePres Yes Yes Yes Yes Yes

to

Quick Base Yes Yes No Yes Yes

QuickBooks Yes Yes No No No

Online

R script Yes Yes 5 No Yes 5 No

Roamler Yes Yes No Yes No

Salesforce Yes Yes No No No

Objects

Salesforce Yes Yes No No No

Reports

SAP Yes Yes Yes Yes Yes

Business
Warehouse
Message
Server

SAP Yes Yes Yes Yes Yes

Business
Warehouse
Server

SAP HANA Yes Yes Yes Yes Yes

SharePoint Yes Yes No Yes No 4

Folder

SharePoint Yes Yes No Yes No 4

List

SharePoint Yes Yes No Yes 2 No

Online List

Smartsheet Yes Yes No No No

 C O N N EC T
AND DIREC TQ UE
C O N N EC T REF RESH RY / L IVE GAT EWAY
DATA F RO M F RO M C O N N EC T I ( SUP P O RT E GAT EWAY
SO URC E DESK TO P SERVIC E ON D) ( REQ UIRED)

Snowflake Yes Yes Yes Yes No

Spark Yes Yes Yes Yes No

SparkPost Yes Yes No No No

SQL Server Yes Yes Yes Yes Yes

SQL Server Yes Yes Yes Yes Yes

Analysis
Services

Stripe Yes Yes No No No

SurveyMon Yes Yes No Yes No

key

SweetIQ Yes Yes No No No

Sybase Yes Yes No Yes Yes

TeamDesk Yes Yes No Yes No

Tenforce Yes Yes No No No

Teradata Yes Yes Yes Yes Yes

Text/CSV Yes Yes No Yes No 4

Twilio Yes Yes No No No

tyGraph Yes Yes No No No

Vertica Yes Yes Yes Yes Yes

Web Yes Yes No Yes Yes 6

Webtrends Yes Yes No No No

Workforce Yes Yes No Yes No

Dimensions

XML Yes Yes No Yes No 4

Zendesk Yes Yes No No No

1 Supported with the ACE OLEDB provider, installed on the same machine as the gateway.

2
2 Supported with the same M function as the on-premises version, causing restricted Auth options (gateway

doesn't support OAuth).

3 Excel 1997-2003 files (.xls) require the ACE OLEDB provider.
4 Required for the on-premises version of the technology.
5 Supported only with the personal gateway.

6 Required for .html, .xls, and Access Databases

7 Power BI service doesn't support OData feeds that require authentication.
8 Paxata is supported in the version of Power BI Desktop optimized for Power BI Report Server. It isn't supported
in Power BI reports published to Power BI Report Server. See Power BI report data sources in Power BI Report
Server for the list of supported data sources.

Single sign-on (SSO) for DirectQuery sources

When the SSO option is enabled and your users access reports built atop the data source, Power BI sends their
authenticated Azure AD credentials in the queries to the underlying data source. This enables Power BI to respect
the security settings that are configured at the data source level. The SSO option takes effect across all datasets
that use this data source. It does not affect the authentication method used for import scenarios. The following
data sources support SSO for connections through DirectQuery:
Azure SQL Database
Azure SQL Data Warehouse
Impala
SAP HANA
SAP BW
SAP BW Message Server
Snowflake
Spark
SQL Server
Teradata

NOTE
Azure Multi-Factor Authentication (MFA) is not supported. Users who want to use SSO with DirectQuery must be
exempted from MFA.

Next steps
Connect to data in Power BI Desktop
Using DirectQuery in Power BI
SQL Server Analysis Services live data in Power BI
What is an on-premises data gateway?
Power BI report data sources in Power BI Report Server
 Power BI data source prerequisites
5/13/2020 • 2 minutes to read • Edit Online

For each data provider, Power BI supports a specific provider version on objects. For more information about data
sources available to Power BI, see Data sources. The following table describes these requirements.

M IN IM UM SUP P O RT ED
P RO VIDER M IN IM UM DATA DATA SO URC E
DATA SO URC E P RO VIDER VERSIO N SO URC E VERSIO N O B JEC T S DO W N LO A D L IN K

SQL Server ADO.net (built .NET Framework SQL Server Tables/Views, Included in .NET
into .Net 3.5 (only) 2005+ Scalar functions, Framework 3.5 or
Framework) Table functions above

Access Microsoft Access ACE 2010 SP1 No restriction Tables/Views Download link
Database Engine
(ACE)

Excel (.xls files Microsoft Access ACE 2010 SP1 No restriction Tables, Sheets Download link
only) (see note 1) Database Engine
(ACE)

Oracle (see note ODP.NET ODAC 11.2 9.x+ Tables/Views Download link
2) Release 5
(11.2.0.3.20)

System.Data.Orac .NET Framework 9.x+ Tables/Views Included in .NET

leClient (Built in 3.5 Framework 3.5 or
.NET Framework) above

IBM DB2 ADO.Net client 10.1 9.1+ Tables/Views Download link

from IBM (part of
the IBM data
server driver
package)

MySQL Connector/Net 6.6.5 5.1 Tables/Views, Download link

Scalar functions

PostgreSQL NPGSQL 4.0.10 9.4 Tables/Views Download link

ADO.NET
provider (Shipped
with Power BI
Desktop)

Teradata .NET Data 14+ 12+ Tables/Views Download link

Provider for
Teradata

SAP Sybase SQL iAnywhere.Data.S 16+ 16+ Tables/Views Download link

Anywhere QLAnywhere for
.NET 3.5
NOTE
Excel files that have an .xlsx extension do not require a separate provider installation.

NOTE
The Oracle providers also require Oracle client software (version 8.1.7+).
 Using enhanced dataset metadata (preview)
9/9/2020 • 4 minutes to read • Edit Online

When Power BI Desktop creates reports, it also creates dataset metadata in the corresponding PBIX and PBIT files.
Previously the metadata was stored in a format that was specific to Power BI Desktop. It used base-64 encoded M
expressions and data sources, and assumptions were made about how that metadata was stored.
With the release of the enhanced dataset metadata feature, many of these limitations are removed. With the
enhanced dataset metadata feature enabled, metadata created by Power BI Desktop uses a format similar to
what is used for Analysis Services tabular models, based on the Tabular Object Model.
The enhanced dataset metadata feature is strategic and foundational, because future Power BI functionality will
be built upon its metadata. Some additional capabilities that stand to benefit from enhanced dataset metadata
include XMLA read/write for management of Power BI datasets, and the migration of Analysis Services workloads
to Power BI to benefit from next-generation features.

Enable enhanced dataset metadata

The enhanced dataset metadata feature is currently in preview. To enable enhanced dataset metadata, in Power
BI Desktop select File > Options and settings > options > preview features , and then select the Store
datasets using enhanced metadata format checkbox, as shown in the following image.

You'll be prompted to restart Power BI Desktop.

Once the preview feature is enabled, Power BI Desktop attempts to upgrade PBIX and PBIT files that use the
previous metadata format.

IMPORTANT
Enabling the enhanced dataset metadata feature results in an irreversible upgrade to reports. Any Power BI reports
loaded or created with Power BI Desktop, once enhanced dataset metadata is enabled, are irreversibly converted to the
enhanced dataset metadata format.

Report backup files

Updating a report to use the enhanced dataset metadata feature is irreversible. During the update, however, a
report backup file is created to save a version of the report in its original (pre-update) format. The backup file is
removed after 30 days.
To locate the backup report file, do the following:
1. Navigate to the following location:
C:\Users\<user>\AppData\Local\Microsoft\Power BI Desktop\TempSaves\Backup . If using the Microsoft Store
version of Power BI Desktop, use the following location:
C:\Users\<user>\Microsoft\Power BI Desktop Store App\TempSaves\Backups

2. Find a copy of the report there with the name and time stamp of the original file.
3. Copy the file to a location you would prefer, in order to preserve it.
4. Make sure the Enhanced metadata format preview feature is disabled in Power BI Desktop if you choose
to open or use that original file.
The backup file is created when the report is upgraded, so any changes made after the upgrade are not included.
New reports created when the Enhanced metadata format feature is enabled do not have a backup file.

Considerations and limitations

In the preview version, the following limitations apply when the preview feature is enabled.
Unsupported features and connectors
The following limitations apply:
Upon opening an existing PBIX or PBIT file that hasn't been upgraded, the upgrade will fail if the dataset contains
any of the following features or connectors. If such failure happens, there should be no immediate impact to the
user experience, and Power BI Desktop continues to use the previous metadata format.
All custom connectors (May 2020 release limitation)
Python scripts
Azure DevOps Server
 BI Connector
Denodo
Dremio
Exasol
Indexima
IRIS
Jethro ODBC
Kyligence Enterprise
Mark Logic ODBC
Qubole Presto
Team Desk
M expressions containing certain character combinations such as “\n” in column names
When using datasets with the enhanced dataset metadata feature enabled, Single Sign On (SSO) data
sources cannot be set up in the Power BI service
If you are using the June 2020 release of Power BI Desktop (or later), all custom connectors and all built-in
connectors are supported for Power BI Desktop and the Power BI service. During the publish process when using
the June 2020 release or later, if the gateway encounters issues then the dataset will successfully publish, but users
must republish the report in order to refresh the data. The Data source settings dialog is the only indicator that
issues occurred with the publishing process.
Reports that use unsupported connectors or features will not be upgraded to the new format. Reports that have
already been upgraded, or that were created subsequent to enabling this new feature, will not support adding the
listed unsupported features or connectors.
Queries with dynamic datasources are not supported. Reports that have dynamic datasources will not be upgraded
to the new format, and reports that have already been upgraded or were newly created with the feature enabled
will not support adding dynamic datasources. A query has a dynamic datasource if the source changes depending
on a parameter, function input, or volatile function.
Queries with errors in upstream steps or branches are not supported.
In addition, PBIX and PBIT files that have already been successfully upgraded to use enhanced dataset metadata
cannot use the above features (or any unsupported connectors).
Lineage view
Datasets using the new metadata format currently don't show links to dataflows in the lineage view in the Power BI
service.

Next steps
You can do all sorts of things with Power BI Desktop. For more information on its capabilities, check out the
following resources:
What is Power BI Desktop?
What's new in Power BI Desktop?
Query overview with Power BI Desktop
Data types in Power BI Desktop
Shape and combine data with Power BI Desktop
Common query tasks in Power BI Desktop
 Work with multidimensional models in Power BI
5/13/2020 • 4 minutes to read • Edit Online

You can connect to multidimensional models in Power BI, and create reports that visualize all sorts of data within
the model. When working with multidimensional models, Power BI applies rules to how it processes data, based on
which column is defined as the default member.
When working with multidimensional models, Power BI handles data from the model based on where the column
that contains the DefaultMember is used. The DefaultMember attribute is set in CSDL (Conceptual Schema
Definition Language) for a particular column in a multidimensional model. You can learn more about the default
member in its attribute properties article. When a DAX query is executed, the default member specified in the
model is applied automatically.
This article described how Power BI behaves under various circumstances when working with multidimensional
models, based on where the default member is found.

Working with filter cards

When creating a filter card on a field with a default member, the default member field value is selected
automatically in the filter card. The result is that all visuals that are affected by the filter card retain their default
models in the database. The values in such filter cards reflect that default member.
If the default member is removed, de-selecting the value clears it for all visuals to which the filter card applies, and
the values displayed do not reflect the default member.
For example, imagine we have a Currency column that has a default member set to USD:
In this example case, if we have a card that shows Total Sales, the value will have the default member applied
and we see sales that correspond to "USD".
If we drag Currency to the filter card pane, we see USD as the default value selected. The value of Total Sales
remains the same, since the default member is applied.
However, if we deselect the USD value from the filter card, the default member for Currency is cleared, and now
Total Sales reflects all currencies.
Consequently, when we select another value in the filter card (let's say we select EURO), along the default
member, the Total Sales reflects the filter Currency IN {USD, EURO}.

Grouping behavior
In Power BI, whenever you group a visual on a column that has a default member, Power BI clears the default
member for that column and its attribute relationship path. This ensures the visual displays all values, rather than
just the default values.

Attribute relationship paths (ARPs)

Attribute relationship paths (ARPs) provide default members with powerful capabilities, but also introduce a certain
amount of complexity. When ARPs are encounter, Power BI follows the path of ARPs to clear additional default
members for other columns, to provide consistent, and precise handling of data for visuals.
Let's look at an example to clarify the behavior. Consider the following configuration of ARPs:
Now let's imagine the following default members are set for these columns:
City > Seattle
State > WA
Country > US
Population > Large
Now let's examine what happens when each of the columns is used in Power BI. When visuals group on the
following columns, here are the results:
City - Power BI displays all the cities by clearing all the default members for City, State, Country but preserves
the default member for Population; Power BI cleared the entire ARP for City.

NOTE
Population is not in the ARP path of City, it is solely related to State and thus Power BI doesn't clear it.

State - Power BI displays all the States by clearing all default members for City, State, Country and Population.
Countr y - Power BI displays all the countries by clearing all default members for City, State and Country, but
preserves the default member for Population.
City and State - Power BI clears all default members for all columns.
Groups displayed in the visual have their entire ARP path cleared.
If a group is not displayed in the visual, but is part of the ARP path of another grouped-on column, the following
applies:
Not all branches of the ARP path are cleared automatically.
That group is still filtered by that uncleared default member .
Slicers and filter cards
When working with slicers or filter cards, the following behavior occurs:
When a slicer or filter card is loaded with data, Power BI groups on the column in the visual, so the display
behavior is the same as described in the previous section.
Since slicers and filter cards are often used to interact with other visuals, the logic of clearing default members
for the affected visuals occurs as explained in the following table.
For this table, we use the same example data used earlier in this article:
The following rules apply for how Power BI behaves in these circumstances.
Power BI clears a default member for a given column if:
Power BI groups on that column
Power BI groups on a column related to that column (anywhere in the ARP, up or down)
Power BI filters on a column that is in the ARP (up or down)
The column has a filter card with ALL state
The column has a filter card with any value selected (Power BI receives a filter for the column)
Power BI does not clear a default member for a given column if:
The column has a filter card with default state, and Power BI is groupings on a column in its ARP.
The column is above another column in the ARP, and Power BI has a filter card for that other column in default
state.

Next steps
This article described the behavior of Power BI when working with default members in multidimensional models.
You might also be interested in the following articles:
Show items with no data in Power BI
Data sources in Power BI Desktop
 About using DirectQuery in Power BI
9/9/2020 • 40 minutes to read • Edit Online

You can connect to all sorts of different data sources when using Power BI Desktop or the Power BI service, and
make those data connections in different ways. You can import data to Power BI, which is the most common way
to get data, or connect directly to data in the original source repository, which is known as DirectQuery. This
article describes DirectQuery capabilities:
Different connectivity options for DirectQuery
Guidance for when you should consider using DirectQuery rather than import
Drawbacks of using DirectQuery
Best practices for using DirectQuery
Follow best practices for using import versus DirectQuery:
You should import data to Power BI wherever possible. Importing takes advantage of the high performance
query engine of Power BI, and provides a highly interactive and fully featured experience.
If your goals can't be met by importing data, consider using DirectQuery. For example, if the data is changing
frequently and reports must reflect the latest data, DirectQuery may be best. However, using DirectQuery is
only feasible when the underlying data source can provide interactive queries, less than 5 seconds for the
typical aggregate query, and can handle the query load that will be generated. Additionally, the list of
limitations for the use of DirectQuery should be considered carefully.
The set of capabilities offered by Power BI for import and DirectQuery evolve over time. Changes will include
providing more flexibility when using imported data, such that import can be used in more cases and eliminating
some of the drawbacks of using DirectQuery. Regardless of improvements, when using DirectQuery, the
performance of the underlying data source always remains a major consideration. If that underlying data source
is slow, using DirectQuery for that source will remain unfeasible.
This article covers DirectQuery with Power BI, and not SQL Server Analysis Services. DirectQuery is also a
feature of SQL Server Analysis Services. Many of the details described in this article apply to that feature. There
are also important differences. For information about using DirectQuery with SQL Server Analysis Services, see
DirectQuery in SQL Server 2016 Analysis Services.
This article focuses on the recommended workflow for DirectQuery, where the report is created in Power BI
Desktop, but also covers connecting directly in the Power BI service.

Power BI connectivity modes

Power BI connects to a large number of varied data sources, encompassing:
Online services (Salesforce, Dynamics 365, others)
Databases (SQL Server, Access, Amazon Redshift, others)
Simple files (Excel, JSON, others)
Other data sources (Spark, Web sites, Microsoft Exchange, others)
For these sources, it's possible to import the data to Power BI. For some, it's also possible to connect using
DirectQuery. For a summary of the sources that support DirectQuery, see Data Sources supported by
DirectQuery. More sources will be DirectQuery enabled in the future, focusing primarily on sources that can be
expected to deliver good interactive query performance.
SQL Server Analysis Services is a special case. When connecting to SQL Server Analysis Services, you can choose
to import the data or use a live connection. Using a live connection is similar to DirectQuery. No data is imported
and the underlying data source is always queried to refresh a visual. A live connection is different in many other
regards, so a different term, live connection versus DirectQuery, is used.
These three options for connecting to data: import, DirectQuery, and live connection.
Import connections
For import, when using Get Data in Power BI Desktop to connect to a data source like SQL Server, the behavior
of that connection is as follows:
During the initial Get Data experience, the set of tables selected each define a query that will return a set of
data. Those queries can be edited before loading the data, for example, to apply filters, or aggregate the data,
or join different tables.
Upon load, all of the data defined by those queries will be imported into the Power BI cache.
Upon building a visual within Power BI Desktop, the imported data will be queried. The Power BI store ensures
the query will be fast. All changes to the visual are reflected immediately.
Any changes to the underlying data aren't reflected in any visuals. It's necessary to Refresh to reimport data.
Upon publishing the report as a .pbix file to the Power BI service, a dataset is created and uploaded to the
Power BI service. The imported data is included with that dataset. It's then possible to schedule refresh of that
data, for example, to reimport the data every day. Depending upon the location of the original data source, it
might be necessary to configure an on-premises data gateway.
When opening an existing report in the Power BI service, or authoring a new report, the imported data is
queried again, ensuring interactivity.
Visuals, or entire report pages, can be pinned as dashboard tiles. The tiles automatically refresh whenever the
underlying dataset refreshes.
DirectQuery connections
For DirectQuery, when using Get Data in Power BI Desktop to connect to a data source, the behavior of that
connection is as follows:
During the initial Get Data experience, the source is selected. For relational sources, a set of tables are selected
and each still define a query that logically returns a set of data. For multidimensional sources, like SAP BW,
only the source is selected.
However, upon load, no data is imported into the Power BI store. Instead, upon building a visual within Power
BI Desktop, queries are sent to the underlying data source to retrieve the necessary data. The time taken to
refresh the visual depends on the performance of the underlying data source.
Any changes to the underlying data aren't immediately reflected in any existing visuals. It's still necessary to
refresh. The necessary queries are resent for each visual, and the visual is updated as necessary.
Upon publishing the report to the Power BI service, it will again result in a dataset in the Power BI service, the
same as for import. However, no data is included with that dataset.
When opening an existing report in the Power BI service, or authoring a new one, the underlying data source
is again queried to retrieve the necessary data. Depending upon the location of the original data source, it
might be necessary to configure an on-premises data gateway, as is needed for import mode if the data is
refreshed.
Visuals, or entire report pages, can be pinned as Dashboard tiles. To ensure that opening a dashboard is fast,
the tiles are automatically refreshed on a schedule, for example, every hour. The frequency of this refresh can
be controlled, to reflect how frequently the data is changing, and how important it's to see the latest data.
When opening a dashboard, the tiles reflect the data at the time of the last refresh, and not necessarily the
latest changes made to the underlying source. You can refresh an open dashboard to ensure it's current.
Live connections
When connecting to SQL Server Analysis Services, there's an option to either import data from or connect live to,
the selected data model. If you use import, you define a query against that external SQL Server Analysis Services
source, and the data is imported as normal. If you use connect live, there's no query defined, and the entire
external model is shown in the field list.
The situation described in the previous paragraph applies to connecting to the following sources as well, except
that there's no option to import the data:
Power BI datasets, for example, when connecting to a Power BI dataset that has previously been created and
published to the service, to author a new report over it.
Common Data Services.
The behavior of reports over SQL Server Analysis Services, upon publishing to the Power BI service, is similar to
DirectQuery reports in the following ways:
When opening an existing report in the Power BI service or authoring a new report, the underlying SQL
Server Analysis Services source is queried, possibly requiring an on-premises data gateway.
Dashboard tiles are automatically refreshed on a schedule, such as every hour.
There are also important differences. For instance, for live connections, the identity of the user opening the
report is always passed to the underlying SQL Server Analysis Services source.
With these comparisons out of the way, let's focus solely on DirectQuery for the rest of this article.

When is DirectQuery useful?

The following table describes scenarios where connecting with DirectQuery could be especially useful. It includes
cases where leaving the data in the original source would be considered beneficial. The description includes a
discussion about whether the specified scenario is available in Power BI.

L IM ITAT IO N DESC RIP T IO N

Data is changing frequently, and near real-time reporting is Models with imported data can be refreshed at most once
needed per hour (more frequently with Power BI Pro or Power BI
Premium subscriptions). Tf the data is continually changing,
and it's necessary for reports to show the latest data, using
import with scheduled refresh might not meet those needs.
You can stream data directly into Power BI, though there are
limits on the data volumes supported for this case.

Using DirectQuery, by contrast, means that opening or

refreshing a report or dashboard always shows the latest
data in the source. Additionally, the dashboard tiles can be
updated more frequently, as often as every 15 minutes.

Data is very large If the data is very large, it wouldn't be feasible to import it all.
DirectQuery, by contrast, requires no large transfer of data,
because it's queried in place.

However, large data might also imply that the performance

of the queries against that underlying source is too slow, as
discussed in Implications of using DirectQuery. You don't
always have to import the full detailed data. Instead, the data
can be pre-aggregated during import. The Query Editor
makes it easy to pre-aggregate during import. In the
extreme, it would be possible to import exactly the aggregate
data needed for each visual. While DirectQuery is the
simplest approach to large data, importing aggregate data
might offer a solution if the underlying source is too slow.
 L IM ITAT IO N DESC RIP T IO N

Security rules are defined in the underlying source When the data is imported, Power BI connects to the data
source using the current user's credentials from Power BI
Desktop, or the credentials defined as part of configuring
scheduled refresh from the Power BI service. In publishing
and sharing such a report, be careful to only share with users
allowed to see the same data, or to define row-level security
as part of the dataset.

Ideally, because DirectQuery always queries the underlying

source, this configuration would allow any security in that
underlying source to be applied. However, currently Power BI
always connects to the underlying source using the same
credentials as would be used for import.

Until Power BI allows for the identity of the report consumer

to pass through to the underlying source, DirectQuery offers
no advantages for data source security.

Data sovereignty restrictions apply Some organizations have policies around data sovereignty,
meaning that data can't leave the organization premises. A
solution based on import would clearly present issues. By
contrast, with DirectQuery that data remains in the
underlying source.

However, even with DirectQuery, some caches of data at the

visual level are kept in the Power BI service because of
scheduled refresh of tiles.

Underlying data source is an OLAP source, containing If the underlying data source contains measures, such as SAP
measures HANA or SAP Business Warehouse, then importing the data
brings other issues. It means that the data imported is at a
particular level of aggregation, as defined by the query. For
example, measures TotalSales by Class , Year , and City .
Then if a visual is built asking for data at a higher-level
aggregate, such as TotalSales by Year , it's further
aggregating the aggregate value. This aggregation is fine for
additive measures, such as Sum and Min , but it's an issue
for non-additive measures, such as Average ,
DistinctCount .

To make it easy to get the correct aggregate data, as needed

for the particular visual, directly from the source, it would be
necessary to send queries per visual, as in DirectQuery.

When connecting to SAP Business Warehouse (BW), choosing

DirectQuery allows for this treatment of measures. For
information about SAP BW, see DirectQuery and SAP BW.

However, currently DirectQuery over SAP HANA treats it the

same as a relational source, and provides similar behavior to
import. This approach is covered further in DirectQuery and
SAP HANA.

In summary, given the current capabilities of DirectQuery in Power BI, it offers the benefits in the following
scenarios:
Data is changing frequently, and near real-time reporting is needed.
Handling very large data, without the need to pre-aggregate.
Data sovereignty restrictions apply.
 The source is a multidimensional source containing measures, such as SAP BW.
The details in the previous list relate to the use of Power BI alone. Instead, you could use an external SQL Server
Analysis Services or Azure Analysis Services model to import data. Then use Power BI to connect to that model.
While that approach would require additional configuration, it does provide greater flexibility. Much larger
volumes of data can be imported. There's no restriction on how frequently the data can be refreshed.

Implications of using DirectQuery

Use of DirectQuery does have potentially negative implications, as detailed in this section. Some of those
limitations are slightly different depending upon the exact source that is being used. We address limitations
where applicable, and separate articles cover those sources that are substantially different.
Performance and load on the underlying source
When using DirectQuery, the overall experience depends very much on the performance of the underlying data
source. If refreshing each visual, for example, after changing a slicer value, takes a few seconds, usually less than
5 seconds, the experience would be reasonable. The experience might feel sluggish compared to the immediate
response when importing the data to Power BI. If the slowness of the source causes individual visuals to take
longer than tens of seconds, the experience becomes extremely poor. Queries may even time out.
Along with the performance of the underlying source, pay attention to the load placed upon the source. Load
impacts performance. Each user who opens a shared report, and each dashboard tile that refreshes, sends at
least one query per visual to the underlying source. This fact requires that the source can handle such a query
load, while still maintaining reasonable performance.
Security implications when combining data sources
It's possible to use multiple data sources in a DirectQuery model, just as when you import data, by using the
Composite models feature. When you use multiple data sources, it's important to understand how data is moved
back and forth between the underlying data sources, and the security implications it brings.
Limited data transformations
Similarly, there are limitations in the data transformations that can be applied within Query Editor. With imported
data, a sophisticated set of transformations can easily be applied to clean and reshape the data before using it to
create visuals, such as parsing JSON documents, or pivoting data from a column to a row form. Those
transformations are more limited in DirectQuery.
First, when connecting to an OLAP source like SAP Business Warehouse, no transformations can be defined at all,
and the entire external model is taken from the source. For relational sources, like SQL Server, it's still possible to
define a set of transformations per query, but those transformations are limited for performance reasons.
Any such transformation will need to be applied on every query to the underlying source, rather than once on
data refresh, so they're limited to those transformations that can reasonably be translated into a single native
query. If you use a transformation that is too complex, you receive an error that either it must be deleted or the
model switched to import.
Additionally, the query that results from the Get Data dialog or Query Editor will be used in a subselect within
the queries generated and sent to retrieve the necessary data for a visual. The query defined in Query Editor
must be valid within this context. In particular, it's not possible to use a query using Common Table Expressions,
nor one that invokes Stored Procedures.
Modeling limitations
The term modeling in this context means the act of refining and enriching the raw data, as part of authoring a
report using it. Examples include:
Defining relationships between tables
Adding new calculations (calculated columns and measures)
 Renaming and hiding columns and measures
Defining hierarchies
Defining the formatting, default summarization and sort order for a column
Grouping or clustering values
When using DirectQuery, many of these model enrichments can still be made, and certainly there's still the
principle that the raw data is being enriched, so as to improve later consumption. However, there are some
modeling capabilities that aren't available, or are limited, when using DirectQuery. The limitations are generally
applied to avoid performance issues. The set of limitations that are common to all DirectQuery sources are listed
here. Additional limitations might apply to individual sources, as described in Next steps.
No built-in date hierarchy: When importing data, every date/datetime column will also have a built-in
date hierarchy available by default. For example, if importing a table of sales orders including a column
OrderDate , then upon using OrderDate in a visual, it will be possible to choose the appropriate level (year,
month, day) to use. This built-in date hierarchy isn't available when using DirectQuery. If there's a Date table
available in the underlying source, as is common in many data warehouses, then the DAX Time Intelligence
functions can be used as normal.
Date/time suppor t only to second accuracy: When using time columns in your dataset, Power BI only
issues queries to the underlying source to a level of detail of seconds. Queries aren't sent to the DirectQuery
source for milliseconds. Remove this part of the times from your source columns.
Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can only
refer to values of other columns of the same table, without the use of any aggregate functions. Additionally,
the DAX scalar functions, such as LEFT() , that are allowed, are limited to those functions that can be pushed
to the underlying source. The functions vary depending upon the exact capabilities of the source. Functions
that aren't supported aren't listed in autocomplete when authoring the DAX for a calculated column, and
would result in an error if used.
No suppor t for parent-child DAX functions: When in DirectQuery mode, it's not possible to use the
family of DAX PATH() functions that generally handle Parent-Child structures, such as chart of accounts, or
employee hierarchies.
Calculated tables aren't suppor ted: The ability to define a calculated table using a DAX expression isn't
supported in DirectQuery mode.
Relationship filtering: For information about bi-directional filtering, see Bidirectional cross-filtering. This
whitepaper presents examples in the context of SQL Server Analysis Services. The fundamental points apply
equally to Power BI.
No Clustering: When using DirectQuery, it's not possible to use the Clustering capability, to automatically
find groups.
Reporting limitations
Almost all reporting capabilities are supported for DirectQuery models. As such, so long as the underlying
source offers a suitable level of performance, the same set of visualizations can be used. There are some
important limitations in some of the other capabilities offered in the Power BI service after a report is published:
Quick Insights isn't suppor ted: Power BI Quick Insights searches different subsets of your dataset while
applying a set of sophisticated algorithms to discover potentially interesting insights. Given the need for very
high performance queries, this capability isn't available on datasets using DirectQuery.
Q&A isn't suppor ted: Power BI Q&A enables you to explore your data using intuitive, natural language
capabilities and receive answers in the form of charts and graphs. However, it's currently not supported on
datasets using DirectQuery.
Using Explore in Excel will likely result in poorer performance: You can explore your data by using
the Explore in Excel capability on a dataset. This approach allows Pivot Tables and Pivot Charts to be created in
Excel. While this capability is supported on datasets using DirectQuery, the performance is generally slower
than creating visuals in Power BI, and therefore if the use of Excel is important for your scenarios, this fact
 should be accounted for in your decision to use DirectQuery.
Security
As discussed earlier in this article, a report in DirectQuery always uses the same fixed credentials to connect to
the underlying data source, after it's published to the Power BI service. This behavior applies to DirectQuery, not
to live connections to SQL Server Analysis Services, which is different in this respect. Immediately after publish
of a DirectQuery report, it's necessary to configure the credentials of the user that will be used. Until you
configure the credentials, opening the report on the Power BI service would result in an error.
Once the user credentials are provided, then those credentials will be used whichever user who opens the report.
In this way, it's exactly like imported data. Every user sees the same data, unless row-level security has been
defined as part of the report. The same attention must be paid to sharing the report, if there are any security
rules defined in the underlying source.
Behavior in the Power BI service
This section describes the behavior of a DirectQuery report in the Power BI service, to explain the degree of load
that will be placed on the back-end data source, given the number of users that the report and dashboard will be
shared with, the complexity of the report, and whether row-level security has been defined in the report.
Reports – opening, interacting with, editing
When a report is opened, all the visuals on the currently visible page refresh. Each visual generally requires at
least one query to the underlying data source. Some visuals might require more than one query. For example, a
visual might show aggregate values from two different fact tables, or contain a more complex measure, or
contain totals of a non-additive measure like Count Distinct. Moving to a new page refreshes those visuals.
Refreshing sends a new set of queries to the underlying source.
Every user interaction on the report might result in visuals being refreshed. For example, selecting a different
value on a slicer requires sending a new set of queries to refresh all of the affected visuals. The same is true for
clicking on a visual to cross-highlight other visuals, or changing a filter.
Similarly, editing a new report requires queries to be sent for each step on the path to produce the final visual.
There's some caching of results. The refresh of a visual is instantaneous if the exact same results have recently
been obtained. If row-level security is defined, such caches aren't shared across users.
Dashboard Refresh
Individual visuals, or entire pages, can be pinned to dashboard as tiles. Tiles based on DirectQuery datasets
refresh automatically according to a schedule. Tiles send queries to the back-end data source. By default, datasets
refresh every hour, but can be configured as part of dataset settings to be between weekly and every 15 minutes.
If no row-level security is defined in the model, each tile is refreshed once, and the results shared across all users.
Otherwise, there can be a large multiplier effect. Each tile requires separate queries per user to be sent to the
underlying source.
A dashboard with 10 tiles, shared with 100 users, created on a dataset using DirectQuery with row-level security,
and configured to refresh every 15 minutes, would result in at least 1000 queries being sent every 15 minutes to
the back-end source.
Pay careful consideration to the use of row-level security, and the configuring of the refresh schedule.
Time-outs
A time-out of four minutes is applied to individual queries in the Power BI service. Queries taking longer than
that will fail. As stressed earlier, we recommend that you use DirectQuery for sources that provide near
interactive query performance. This limit is intended to prevent issues from overly long execution times.
Other implications
Some other general implications of using DirectQuery are as follows:
 If data is changing, it's necessar y to refresh to ensure the latest data is shown: Given the use of
caches, there's no guarantee that the visual is always showing the latest data. For example, a visual might
show the transactions in the last day. Because of a slicer being changed, it might refresh to show the
transactions for the last two days. The transactions could include recent, newly arrived transactions.
Returning the slicer to its original value would result in it again showing the cached value previously
obtained.
Selecting Refresh clears any caches and refreshes all the visuals on the page to show the latest data.
If data is changing, there's no guarantee of consistency between visuals: Different visuals,
whether on the same page or on different pages, might be refreshed at different times. If the data in the
underlying source is changing, there's no guarantee that each visual shows the data at the exact same
point of time. Indeed, given that sometimes more than one query is required for a single visual, for
example, to obtain the details and the totals, then consistency even within a single visual isn't guaranteed.
To guarantee this consistency would require the overhead of refreshing all visuals whenever any visual
refreshed, in tandem with the use of costly features like Snapshot Isolation in the underlying data source.
This issue can be mitigated to a large extent by again selecting Refresh to refresh all of the visuals on the
page. Even if using import mode, there's a similar problem of guaranteeing consistency while importing
data from more than one table.
Refresh in Power BI Desktop is needed to reflect any metadata changes: After a report is
published, Refresh will refresh the visuals in the report. If the schema of the underlying source has
changed, then those changes aren't automatically applied to change the available fields in the field list. If
tables or columns have been removed from the underlying source, it might result in query failure upon
refresh. Opening the report in Power BI Desktop, and choosing Refresh updates the fields in the model to
reflect the changes.
Limit of 1 million rows returned on any quer y: There's a fixed limit of 1 million rows placed on the
number of rows that can be returned in any single query to the underlying source. This limit generally has
no practical implications, and visuals themselves aren't going to display that many points. However, the
limit can occur in cases where Power BI isn't fully optimizing the queries sent, and there's some
intermediate result being requested that exceeds the limit. It can also occur while building a visual, on the
path to a more reasonable final state. For example, including Customer and TotalSalesQuantity would
hit this limit if there were more than 1 million customers, until some filter were applied.
The error that would be returned would be: "The resultset of a query to external data source has exceeded
the maximum allowed size of '1000000' rows."
Can't change from impor t to DirectQuer y mode: While it's possible to switch a model from
DirectQuery mode to use import mode, all the necessary data must be imported. It's also not possible to
switch back, primarily because of the set of features not supported in DirectQuery mode. DirectQuery
models over multidimensional sources, like SAP BW, also can't be switched from DirectQuery to import,
because of the different treatment of external measures.

DirectQuery in the Power BI service

All sources are supported from Power BI Desktop. Some sources are also available directly from within the Power
BI service. For example, it's possible for a business user to use Power BI to connect to their data in Salesforce, and
immediately get a dashboard, without use of Power BI Desktop.
Only two of the DirectQuery enabled-sources are available directly in the service:
Spark
Azure SQL Data Warehouse
However, we recommend that any use of DirectQuery over those two sources start within Power BI Desktop. The
reason is that when the connection is initially made in the Power BI service, many key limitations will apply. While
the start point was easy, starting in the Power BI service, there are limitations on enhancing the resulting report
any further. For example, it's not possible then to create any calculations, or use many analytical features, or even
refresh the metadata to reflect any changes to the underlying schema.

Guidance for using DirectQuery successfully

If you're going to use DirectQuery, this section provides you with some high-level guidance on how to ensure
success. The guidance in this section is derived from the implications of using DirectQuery that have been
described in this article.
Back-end data source performance
Validate that simple visuals refresh in a reasonable time. A refresh time should be within 5 seconds to have a
reasonable interactive experience. If visuals are taking longer than 30 seconds, it's highly likely that further issues
will occur following publication of the report. These issues can make the solution unworkable.
If queries are slow, examine the queries being sent to the underlying source, and the reason for the query
performance. This article doesn't cover the wide range of database optimization best practices across the full set
of potential underlying sources. This article does cover the standard database practices that apply to most
situations:
Relationships based on integer columns generally perform better than joins on columns of other data types.
The appropriate indexes should be created. Index creation generally means the use of column store indexes in
those sources that support them, for example, SQL Server.
Any necessary statistics in the source should be updated.
Model Design Guidance
When defining the model, consider following this guidance:
Avoid complex queries in Quer y Editor. Query Editor translates a complex query into a single SQL
query. The single query appears in the subselect of every query sent to that table. If that query is complex,
it might result in performance issues on every query sent. The actual SQL query for a set of steps can be
obtained by selecting the last step in Query Editor, and choosing View Native Quer y from the context
menu.
Keep measures simple. At least initially, we recommend limiting measures to simple aggregates. Then if
the measures operate in a satisfactory manner, more complex measures can be defined, but paying
attention to the performance for each.
Avoid relationships on calculated columns. This guidance is relevant to databases where you need
to do multi-column joins. Power BI today doesn't allow a relationship to be based on multiple columns as
the FK/PK. The common workaround is to concatenate the columns together using a calculated column,
and base the join on that column. While this workaround is reasonable for imported data, for DirectQuery,
it results in a join on an expression. That result commonly prevents use of any indexes, and leads to poor
performance. The only workaround is to actually materialize the multiple columns into a single column in
the underlying database.
Avoid relationships on uniqueidentifier columns. Power BI doesn't natively support a datatype of
uniqueidentifier . Defining a relationship between columns of type uniqueidentifier column results in a
query with a join involving a cast. Again, this approach commonly leads to poor performance. Until this
case is specifically optimized, the only workaround is to materialize columns of an alternative type in the
underlying database.
Hide the to column on relationships. The to column on relationships is commonly the primary key on
 the to table. That column should be hidden. If hidden, it doesn't appear in the field list and can't be used in
visuals. Often the columns on which relationships are based are in fact system columns, for example,
surrogate keys in a data warehouse. It's good practice to hide such columns anyway. If the column does
have meaning, then introduce a calculated column that is visible, and that has a simple expression of
being equal to the primary key, as in the following example:

ProductKey_PK (Destination of a relationship, hidden)

ProductKey (= [ProductKey_PK], visible)
ProductName
...

Examine all uses of calculated columns and data type changes. Use of these capabilities aren't
necessarily harmful. They do result in the queries sent to the underlying source containing expressions
rather than simple references to columns. That again might result in indexes not being used.
Avoid use of the bi-directional cross filtering on relationships. Use of bi-directional cross filtering
can lead to query statements that don't perform well.
Experiment with setting Assume referential integrity . The Assume Referential Integrity setting on
relationships enables queries to use INNER JOIN statements rather than OUTER JOIN . This guidance
generally improves query performance, though it does depend on the specifics of the data source.
Don't use the relative data filtering in Quer y Editor. It's possible to define relative date filtering in
Query Editor. For example, to filter to the rows where the date is in the last 14 days.

However, this filter is translated into a filter based on the fixed date, as at the time the query was authored.
This result can be seen from viewing the native query.

This result is probably not what you wanted. To ensure the filter is applied based on the date at the time
the report runs, instead apply the filter in the report as a Report Filter. Currently, this approach would be
done by creating a calculated column calculating the number of days ago, using the DAX DATE() function,
and then using that calculated column in a filter.
Report Design Guidance
When creating a report using a DirectQuery connection, follow this guidance:
Consider use of Quer y Reduction options: Power BI provides options in the report to send fewer
queries, and to disable certain interactions that would result in a poor experience if the resulting queries
take a long time to run. To access these options in Power BI Desktop, go to File > Options and settings
> Options and select Quer y reduction .

Checking box selections on the Quer y reduction let you disable cross-highlighting throughout your
entire report. You can also show an Apply button to slicers or filter selections. This approach lets you then
make many slicer and filter selections before applying them. No queries are sent until you select the
Apply button on the slicer. Your selections can then be used to filter the data.
These options apply to your report while you interact with it in Power BI Desktop. These options also apply
when your users consume the report in the Power BI service.
Apply filters first: Always apply any applicable filters at the start of building a visual. For example, rather
than drag in TotalSalesAmount and ProductName , then filter to a particular year, apply the filter on
Year at the very start. Each step of building a visual sends a query. Although it's possible to then make
another change before the first query has completed, this approach still leaves unnecessary load on the
underlying source. By applying filters early, it generally makes those intermediate queries less costly. Also,
failing to apply filters early can result in hitting the 1 million row limit.
Limit the number of visuals on a page: When you open a page or change a page level slicer or filter,
all of the visuals on a page are refreshed. There's also a limit on the number of queries that are sent in
parallel. As the number of visuals increases, some of the visuals will be refreshed in a serial manner,
increasing the time taken to refresh the entire page. For this reason, we recommend that you limit the
number of visuals on a single page, and instead have more, simpler pages.
Consider switching off interaction between visuals: By default, visualizations on a report page can
 be used to cross-filter and cross-highlight the other visualizations on the page. For example, having
selected 1999 on the pie chart, the column chart is cross highlighted to show the sales by category for
1999 .

Cross-filtering and cross-highlighting in DirectQuery require queries to be submitted to the underlying

source. The interaction should be switched off if the time taken to respond to users' selections would be
unreasonably long. You can switch off this interaction. Switch off the interaction for either the entire
report, as described earlier for query reduction options, or on a case-by-case basis. For more information,
see How visuals cross-filter each other in a Power BI report.
In addition to the previous suggestions, each of the following reporting capabilities can cause performance
issues:
Measure filters: Visuals containing measures, or aggregates of columns, can contain filters in those
measures. For example, the following graphic shows SalesAmount by Categor y , but only including
those categories with more than 20M of sales.

This approach results in two queries being sent to the underlying source:
The first query retrieves the Categories meeting the condition, SalesAmount greater than 20 million.
The second query then retrieves the necessary data for the visual, including the categories that met the
condition in the WHERE clause.
This approach generally works well if there are hundreds or thousands of categories, as in this example.
 Performance can degrade if the number of categories is much larger. The query fails for more than a
million categories meeting the condition. The 1 million row limit was discussed earlier.
TopN filters: Advanced filters can be defined to filter on only the top or bottom N values ranked by some
measure. For example, filters can include the top 10 categories in the previous visual. This approach again
results in two queries being sent to the underlying source. However, the first query will return all
categories from the underlying source, and then the TopN are determined based on the returned results.
Depending on the cardinality of the column involved, this approach can lead to performance issues or
query failures because of the 1 million row limit.
Median: Generally, any aggregation, such as Sum or Count Distinct , is pushed to the underlying source.
However, this fact isn't true for median, which this aggregate is generally not supported by the underlying
source. In such cases, the detail data is retrieved from the underlying source, and the median calculated
from the returned results. This approach is reasonable when the median is to be calculated over a
relatively small number of results. Performance issues or query failures because of the 1 million row limit
occur if the cardinality is large. For example, Median Countr y Population might be reasonable, but
Median Sales Price might not be.
Advanced text filters ( contains and similar): When filtering on a text column, the advanced filtering
allows filters like contains and begins with and so on. These filters can certainly result in degraded
performance for some data sources. In particular, the default contains filter shouldn't be used if what is
required is an exact match. Although the results might be the same, depending on the actual data, the
performance might be drastically different because of indexes.
Multi select slicers: By default, slicers only allow a single selection to be made. Allowing multi-selection
in filters can cause some performance issues, because the user selects a set of items in the slicer. For
example, if the user selects the 10 products of interest, each new selection results in queries being sent to
the source. Although the user can select the next item before the query completes, this approach results in
extra load on the underlying source.
Consider switching off totals on visuals: By default, tables and matrices display totals and subtotals.
In many cases, separate queries must be sent to the underlying source to obtain the values for such totals.
This fact applies whenever using DistinctCount aggregation, or in all cases when using DirectQuery over
SAP BW or SAP HANA. Such totals should be switched off by using the Format pane.
Maximum number of connections option for DirectQuery
You can set the maximum number of connections DirectQuery opens for each underlying data source, which
controls the number of queries concurrently sent to each data source.
DirectQuery opens a default maximum number of 10 concurrent connections. You can change the maximum
number for the current file in Power BI Desktop. Go to File > Options and Settings > Options . In the Current
File section in the left pane, select DirectQuer y .
The setting is only enabled when there's at least one DirectQuery source in the current report. The value applies
to all DirectQuery sources, and to any new DirectQuery sources added to the same report.
Increasing Maximum connections per data source ensures more queries, up to the maximum number
specified, can be sent to the underlying data source. This approach is useful when many visuals are on a single
page, or many users access a report at the same time. Once the maximum number of connections is reached,
further queries are queued until a connection becomes available. Increasing this limit does result in more load on
the underlying source, so the setting isn't guaranteed to improve overall performance.
Once a report is published, the maximum number of concurrent queries sent to the underlying data source also
depend upon fixed limits. The limits depend on the target environment to which the report is published. Different
environments, such as Power BI, Power BI Premium, or Power BI Report Server, can impose different limits.
Diagnosing performance issues
This section describes how to diagnose performance issues, or how to get more detailed information to allow the
reports to be optimized.
We recommended that you start diagnosis of performance issues in Power BI Desktop, rather than in the Power
BI service. Performance issues are often based on the performance of the underlying source. You can more easily
identify and diagnose issues in the more isolated environment of Power BI Desktop. This approach initially
eliminates certain components, such as the Power BI gateway. If the performance issues are absent from Power
BI Desktop, investigate the specifics of the report in the Power BI service. The performance analyzer is a useful
tool for identifying issues throughout this process.
Similarly, we recommend to first try to isolate any issues to an individual visual, rather than many visuals on a
page.
Let's say the steps in the previous paragraphs in this section have been taken. We now have a single visual on a
page in Power BI Desktop that is still sluggish. Use the performance analyzer to determine the queries that Power
BI Desktop sends to the underlying source. It's also possible to view traces and diagnostic information that might
be emitted by the underlying data source. Traces might also contain useful details of how the query was
executed, and how it can be improved.
Further, even in the absence of such traces from the source, it's possible to view the queries sent by Power BI,
along with their execution times, as described in the next section.
Determining the queries sent by Power BI Desktop
By default, Power BI Desktop logs events during a given session to a trace file called FlightRecorderCurrent.trc.
For some DirectQuery sources, this log includes all queries sent to the underlying data source. The remaining
DirectQuery sources will be included in the future. The following sources send queries to the log:
SQL Server
Azure SQL Database
Azure SQL Data warehouse
Oracle
Teradata
SAP HANA
The trace file can be found in the AppData folder for the current user:
<User>\AppData\Local\Microsoft\Power BI Desktop\AnalysisServicesWorkspaces
To get to this folder, in Power BI Desktop, select File > Options and settings > Options , and then select
Diagnostics . The following dialog appears:
When you select Open crash dump/traces folder , under Diagnostic Options , the following folder opens:
<User>\AppData\Local\Microsoft\Power BI Desktop\Traces.
Navigating to that folder's parent folder displays the folder containing AnalysisServicesWorkspaces, which will
contain one workspace folder for every open instance of Power BI Desktop. These folders are named with an
integer suffix, such as AnalysisServicesWorkspace2058279583.
Inside that folder is a \Data folder. It contains the trace file FlightRecorderCurrent.trc for the current Power BI
session. The corresponding workspace folder is deleted when the associated Power BI Desktop session ends.
The trace files can be read using the SQL Server Profiler tool. Get it as part of the free download SQL Server
Management Studio.
Once you download and install SQL Server Management Studio, run SQL Server Profiler.

To open the trace file, take the following steps:

1. In SQL Server Profiler, select File > Open > Trace file .
2. Enter the path to the trace file for the currently open Power BI session, such as:
C:\Users<user>\AppData\Local\Microsoft\Power BI
Desktop\AnalysisServicesWorkspaces\AnalysisServicesWorkspace2058279583\Data.
3. Open FlightRecorderCurrent.trc.
All events from the current session are displayed. An annotated example is shown here, which highlights groups
of events. Each group has the following events:
A Query Begin and Query End event, which represent the start and end of a DAX query generated by the UI,
for example, from a visual, or from populating a list of values in the filter UI.
One or more pairs of DirectQuery Begin and DirectQuery End events, which represent a query sent to the
underlying data source, as part of evaluating the DAX query.
Multiple DAX queries can run in parallel, so events from different groups can be interleaved. The value of the
ActivityID can be used to determine which events belong to the same group.

Other columns of interest are as follows:

TextData: The textual detail of the event. For Query Begin/End events, the detail is the DAX query. For
DirectQuery Begin/End events, the detail is the SQL query sent to the underlying source. The TextData for the
currently selected event is also displayed in the region at the bottom.
EndTime: The time when the event completed.
Duration: The duration, in milliseconds, taken to execute the DAX or SQL query.
Error : Indicates if an error occurred, in which case the event is also displayed in red.
In the image above, some of the less interesting columns have been narrowed, to allow other columns to be seen
more easily.
We recommend the following approach to capturing a trace to help diagnose a potential performance issue:
Open a single Power BI Desktop session, to avoid the confusion of multiple workspace folders.
Do the set of actions of interest in Power BI Desktop. Include a few additional actions, to ensure that the
events of interest are flushed into the trace file.
Open SQL Server Profiler and examine the trace, as described previously. Remember that closing Power BI
Desktop deletes the trace file. Also, further actions in Power BI Desktop don't immediately appear. The trace
file should be closed and reopened to see the new events.
Keep individual sessions reasonably small, perhaps 10 seconds of actions, not hundreds. This approach makes
it easier to interpret the trace file. There's also a limit on the size of the trace file. For long sessions, there's a
chance of early events being dropped.
Understanding the form of query sent by Power BI Desktop
The general format of queries created and sent by Power BI Desktop use subselects for each of the tables
referenced. The Query Editor query defines the subselect. For example, assume the following TPC-DS tables in
SQL Server:
Consider the following query:

That query results in the following visual:

Refreshing that visual will result in the SQL query shown here. As you can tell, there are three subselects for
Web Sales , Item , and Date_dim , that each return all the columns on the respective table, even though only four
columns are actually referenced by the visual. These queries in the subselects that are shaded are exactly the
result of the queries defined in Query Editor. Use of subselects in this manner hasn't been found to impact
performance for the data sources so far supported for DirectQuery. Data sources like SQL Server optimize away
the references to the other columns.
Power BI employs this pattern because the SQL query used can be provided directly by the analyst. It's used "as
provided", without an attempt to rewrite it.
Next steps
This article describes aspects of DirectQuery that are common across all data sources. There are certain details
that are specific to individual sources. See the following articles covering specific sources:
DirectQuery and SAP HANA
DirectQuery and SAP BW
For more information about DirectQuery, see the following resource:
Data Sources supported by DirectQuery
 Guidance for deploying a data gateway for Power BI
5/13/2020 • 3 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

This article provides guidance and considerations for deploying a data gateway for Power BI in your network
environment.
For information about how to download, install, configure, and manage the on-premises data gateway, see What is
an on-premises data gateway?. You can also find out more about the on-premises data gateway and Power BI by
visiting the Microsoft Power blog and the Microsoft Power BI Community site.

Installation considerations for the on-premises data gateway

Before you install the on-premises data gateway for your Power BI cloud service, there are some considerations to
keep in mind. The following sections describe these considerations.
Number of users
The number of users who consume a report that uses the gateway is an important metric in your decision about
where to install the gateway. Here are some questions to consider:
Do users use these reports at different times of the day?
What types of connections do they use (DirectQuery or Import)?
Do all users use the same report?
If all the users access a given report at the same time each day, make sure that you install the gateway on a
machine that's capable of handling all those requests. See the following sections for performance counters and
minimum requirements that can help you determine whether a machine is adequate.
A constraint in Power BI allows only one gateway per report. Even if a report is based on multiple data sources, all
such data sources must go through a single gateway. If a dashboard is based on multiple reports, you can use a
dedicated gateway for each contributing report. In this way, you distribute the gateway load among the multiple
reports that contribute to the single dashboard.
Connection type
Power BI offers two types of connections: DirectQuery and Import. Not all data sources support both connection
types. Many factors might contribute to your choice of one over the other, such as security requirements,
performance, data limits, and data model sizes. To learn more about connection types and supported data sources,
see the list of available data source types.
Depending on which type of connection is used, gateway usage can be different. For example, try to separate
DirectQuery data sources from scheduled refresh data sources whenever possible. The assumption is that they're in
different reports and can be separated. Separating sources prevents the gateway from having thousands of
DirectQuery requests queued up at the same time as the morning's scheduled refresh of a large-size data model
that's used for the company's main dashboard.
Here's what to consider for each option:
 Scheduled refresh : Depending on your query size and the number of refreshes that occur per day, you can
choose to stay with the recommended minimum hardware requirements or upgrade to a higher
performance machine. If a given query isn't folded, transformations occur on the gateway machine. As a
result, the gateway machine benefits from having more available RAM.
DirectQuer y : A query is sent each time any user opens the report or looks at data. If you expect more than
1,000 users to access the data concurrently, make sure your computer has robust and capable hardware
components. More CPU cores result in better throughput for a DirectQuery connection.
For the machine installation requirements, see the on-premises data gateway installation requirements.
Location
The location of the gateway installation can have significant impact on your query performance. Try to make sure
that your gateway, data source locations, and the Power BI tenant are as close as possible to each other to minimize
network latency. To determine your Power BI tenant location, in the Power BI service select the ? icon in the upper-
right corner. Then select About Power BI .

If you intend to use the Power BI gateway with Azure Analysis Services, be sure that the data regions in both match.
For more information about how to set data regions for multiple services, watch this video.

Next steps
Configuring proxy settings
Troubleshoot gateways - Power BI
On-premises data gateway FAQ - Power BI
More questions? Try the Power BI Community.
 On-premises data gateway FAQ - Power BI
9/9/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

Power BI
Question: Do I need to upgrade the on-premises data gateway (personal mode)?
Answer : No, you can keep using the gateway (personal mode) for Power BI.
Question: Are any special permissions required to install the gateway and manage it in the Power BI service?
Answer : No special permissions are required.
Question: Can I upload Excel workbooks with Power Pivot data models that connect to on-premises data sources?
Do I need a gateway for this scenario?
Answer : Yes, you can upload the workbook. And, no, you don’t need a gateway. But, because the data will reside in
the Excel data model, reports in Power BI based on the Excel workbook won't be live. To refresh reports in Power BI,
you have to re-upload an updated workbook each time. Or, use the gateway with scheduled refresh.
Question: If users share dashboards that have a DirectQuery connection, will those other users be able to see the
data even though they might not have the same permissions?
Answer : For a dashboard connected to Azure Analysis Services, users will see only the data they have access to. If
the users don't have the same permissions, they won't be able to see any data. For other data sources, all users will
share the credentials entered by the admin for that data source.
Question: Why can't I connect to my Oracle server?
Answer : You might need to install the Oracle client and configure the tnsnames.ora file with the proper server
information in order to connect to your Oracle server. This is a separate installation outside of the gateway. For
more information, see Install the Oracle client.
Question: I'm using R scripts. Is that supported?
Answer : R scripts are supported only for personal mode.

Analysis Services in Power BI

Question: Can I use msmdpump.dll to create custom effective username mappings for Analysis Services?
Answer : No. This use isn't supported at this time.
Question: Can I use the gateway to connect to a multidimensional (OLAP) instance?
Answer : Yes. The on-premises data gateway supports live connections to both Analysis Services Tabular and
Multidimensional models.
Question: What if I install the gateway on a computer in a different domain from my on-premises server that uses
Windows authentication?
Answer : No guarantees here. It all depends on the trust relationship between the two domains. If the two different
domains are in a trusted domain model, the gateway might be able to connect to the Analysis Services server and
the effective username can be resolved. If not, you might encounter a login failure.
Question: How can I find out what effective username is being passed to my on-premises Analysis Services
server?
Answer : We answer this question in the troubleshooting article.

Next steps
Troubleshooting the on-premises data gateway
More questions? Try the Power BI Community.
 Connect to data sources in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

With Power BI Desktop, you can easily connect to the ever expanding world of data. If you don’t have Power BI
Desktop, you can download and install it.
There are all sorts of data sources available in Power BI Desktop. The following image shows how to connect to
data, by selecting Get Data > Other > Web .

Example of connecting to data

For this example, we'll connect to a Web data source.
Imagine you’re retiring. You want to live where there’s lots of sunshine, preferable taxes, and good health care.
Or… perhaps you’re a data analyst, and you want that information to help your customers, as in, help your
raincoat manufacturing client target sales where it rains a lot.
Either way, you find a Web resource that has interesting data about those topics, and more:
https://www.bankrate.com/finance/retirement/best-places-retire-how-state-ranks.aspx
Select Get Data > Other > Web . In From Web , enter the address.
When you select OK , the Query functionality of Power BI Desktop goes to work. Power BI Desktop contacts the
Web resource, and the Navigator window returns the results of what it found on that Web page. In this case, it
found a table and the overall Document. We're interested in the table, so we select it from the list. The Navigator
window displays a preview.

At this point, you can edit the query before loading the table, by selecting Transform Data from the bottom of
the window, or just load the table.
Select Transform Data to load the table and launch Power Query Editor. The Quer y Settings pane is displayed.
If it's not, select View from the ribbon, then Quer y Settings to display the Quer y Settings pane. Here’s what
that looks like.
All those scores are text rather than numbers, and we need them to be numbers. No problem. Just right-click the
column header, and select Change Type > Whole Number to change them. To choose more than one column,
first select a column then hold down Shift, select additional adjacent columns, and then right-click a column
header to change all selected columns. Use Ctrl to choose columns that aren't adjacent.

In Quer y Settings , the APPLIED STEPS will reflect any changes that were made. As you make additional
changes to the data, Power Query Editor will record those changes in the APPLIED STEPS section, which you can
adjust, revisit, rearrange, or delete as necessary.
Additional changes to the table can still be made after it's loaded, but for now this will do. When you're done,
select Close & Apply from the Home ribbon, and Power BI Desktop applies the changes and closes Power Query
Editor.

With the data model loaded, in Repor t view in Power BI Desktop, we can begin creating visualizations by
dragging fields onto the canvas.

Of course, this model is simple, with a single data connection. Most Power BI Desktop reports will have
connections to different data sources, shaped to meet your needs, with relationships that produce a rich data
model.

Next steps
There are all sorts of things you can do with Power BI Desktop. For more information on its capabilities, check out
the following resources:
What is Power BI Desktop?
About using Query Editor in Power BI Desktop
Data sources in Power BI Desktop
 Shape and combine data in Power BI Desktop
Perform common query tasks in Power BI Desktop
Want to give us feedback? Great! Use the Submit an Idea menu item in Power BI Desktop or visit Community
Feedback. We look forward to hearing from you!
 Data sources in Power BI Desktop
9/9/2020 • 8 minutes to read • Edit Online

With Power BI Desktop, you can connect to data from many different sources. For a full list of available data
sources, see Power BI data sources.
You connect to data by using the Home ribbon. To show the Most Common data types menu, select the Get
Data button label or the down arrow.

To go to the Get Data dialog box, show the Most Common data types menu and select More . You can also
bring up the Get Data dialog box (and bypass the Most Common menu) by selecting the Get Data icon
directly.
 NOTE
The Power BI team is continually expanding the data sources available to Power BI Desktop and the Power BI service. As
such, you'll often see early versions of work-in-progress data sources marked as Beta or Preview . Any data source
marked as Beta or Preview has limited support and functionality, and it shouldn't be used in production environments.
Additionally, any data source marked as Beta or Preview for Power BI Desktop may not be available for use in the Power
BI service or other Microsoft services until the data source becomes generally available (GA).

NOTE
There are many data connectors for Power BI Desktop that require Internet Explorer 10 (or newer) for authentication.

Data sources
The Get Data dialog box organizes data types in the following categories:
All
File
Database
Power Platform
Azure
Online Services
Other
The All category includes all data connection types from all categories.
File data sources
The File category provides the following data connections:
Excel
Text/CSV
XML
JSON
Folder
PDF
SharePoint folder
The following image shows the Get Data window for File .

Database data sources

The Database category provides the following data connections:
SQL Server database
Access database
SQL Server Analysis Services database
Oracle database
IBM Db2 database
IBM Informix database (Beta)
IBM Netezza
MySQL database
PostgreSQL database
 Sybase database
Teradata database
SAP HANA database
SAP Business Warehouse Application Server
SAP Business Warehouse Message Server
Amazon Redshift
Impala
Google BigQuery
Vertica
Snowflake
Essbase
AtScale cubes
BI Connector
Data Virtuality LDW (Beta)
Denodo
Dremio
Exasol
Indexima (Beta)
InterSystems IRIS (Beta)
Jethro (Beta)
Kyligence
Linkar PICK Style / MultiValue Databases (Beta)
MarkLogic

NOTE
Some database connectors require that you enable them by selecting File > Options and settings > Options then
selecting Preview Features and enabling the connector. If you don't see some of the connectors mentioned above and
want to use them, check your Preview Features settings. Also note that any data source marked as Beta or Preview has
limited support and functionality, and should not be used in production environments.

The following image shows the Get Data window for Database .
Power Platform data sources
The Power Platform category provides the following data connections:
Power BI datasets
Power BI dataflows
Common Data Service
Power Platform dataflows (Beta)
The following image shows the Get Data window for Power Platform .
Azure data sources
The Azure category provides the following data connections:
Azure SQL Database
Azure SQL Data Warehouse
Azure Analysis Services database
Azure Database for PostgreSQL
Azure Blob Storage
Azure Table Storage
Azure Cosmos DB
Azure Data Explorer (Kusto)
Azure Data Lake Storage Gen2
Azure Data Lake Storage Gen1
Azure HDInsight (HDFS)
Azure HDInsight Spark
HDInsight Interactive Query
Azure Data Explorer (Kusto)
Azure Cost Management
Azure Time Series Insights (Beta)
The following image shows the Get Data window for Azure .
Online Services data sources
The Online Ser vices category provides the following data connections:
SharePoint Online List
Microsoft Exchange Online
Dynamics 365 (online)
Dynamics NAV
Dynamics 365 Business Central
Dynamics 365 Business Central (on-premises)
Microsoft Azure Consumption Insights (Beta)
Azure DevOps (Boards only)
Azure DevOps Server (Boards only)
Salesforce Objects
Salesforce Reports
Google Analytics
Adobe Analytics
appFigures (Beta)
Data.World - Get Dataset (Beta)
GitHub (Beta)
LinkedIn Sales Navigator (Beta)
Marketo (Beta)
Mixpanel (Beta)
 Planview Enterprise One - PRM (Beta)
QuickBooks Online (Beta)
Smartsheet
SparkPost (Beta)
SweetIQ (Beta)
Planview Enterprise One - CTM (Beta)
Twilio (Beta)
Zendesk (Beta)
Asana (Beta)
Dynamics 365 Customer Insights (Beta)
Emigo Data Source
Entersoft Business Suite (Beta)
FactSet Analytics
Palantir Foundry
Industrial App Store
Intune Data Warehouse (Beta)
Microsoft Graph Security (Beta)
Projectplace for Power BI (Beta)
Product Insights (beta)
Quick Base
TeamDesk (Beta)
Webtrends Analytics (Beta)
Witivio (Beta)
Workplace Analytics (Beta)
Zoho Creator (Beta)
The following image shows the Get Data window for Online Ser vices .
Other data sources
The Other category provides the following data connections:
Web
SharePoint list
OData Feed
Active Directory
Microsoft Exchange
Hadoop File (HDFS)
Spark
Hive LLAP (Beta)
R script
Python script
ODBC
OLE DB
Solver
FHIR
Information Grid (Beta)
Jamf Pro (Beta)
Paxata
QubolePresto (Beta)
Roamler (Beta)
 Shortcuts Business Insights (Beta)
Siteimprove
Tenforce (Smart)List
TIBCO(R) Data Virtualization (Beta)
Vessel Insight (Beta)
Workforce Dimensions (Beta)
Zucchetti HR Infinity (Beta)
Cognite Data Fusion (Beta)
MicroStrategy for Power BI
SurveyMonkey (Beta)
Vena (Beta)
Acterys : Model Automation & Planning (Beta)
Automation Anywhere (Beta)
Cherwell (Beta)
Blank Query
The following image shows the Get Data window for Other .

NOTE
At this time, it's not possible to connect to custom data sources secured using Azure Active Directory.
Connecting to a data source
To connect to a data source, select the data source from the Get Data window and select Connect . In the
following image, Web is selected from the Other data connection category.

A connection window is displayed, specific to the type of data connection. If credentials are required, you’ll be
prompted to provide them. The following image shows a URL being entered to connect to a Web data source.

Enter the URL or resource connection information, and then select OK . Power BI Desktop makes the connection
to the data source, and it presents the available data sources in the Navigator .
To load the data, select the Load button at the bottom of the Navigator pane. To transform or edit the query in
Power Query Editor before loading the data, select the Transform Data button.
That’s all there is to connecting to data sources in Power BI Desktop! Try connecting to data from our growing
list of data sources, and check back often - we continue to add to this list all the time.

Using PBIDS files to get data

PBIDS files are Power BI Desktop files that have a specific structure, and they have a .PBIDS extension to identify
it is a Power BI data source file.
You can create a PBIDS file to streamline the Get Data experience for report creators in your organization. To
make it easier for a new report author to use PBIDS files, we recommend that an administrator create these files
for commonly used connections.
When an author opens a PBIDS file, Power BI Desktop opens and prompts the user for credentials to
authenticate and connect to the data source that's specified in the file. The Navigation dialog box appears, and
the user must select the tables from that data source to load into the model. Users may also need to select the
database(s) if none was specified in the PBIDS file.
From that point forward, the user can begin building visualizations or select Recent Sources to load a new set
of tables into the model.
Currently, PBIDS files only support a single data source in one file. Specifying more than one data source results
in an error.
To create the PBIDS file, an administrator must specify the required inputs for a single connection. They can also
specify the connection mode as either DirectQuery or Import. If mode is missing/null in the file, the user who
opens the file in Power BI Desktop is prompted to select DirectQuer y or Impor t .
PBIDS file examples
This section provides some examples from commonly used data sources. The PBIDS file type only supports data
connections that are also supported in Power BI Desktop, with two exceptions: Live Connect and Blank Query.
The PBIDS file doesn't include authentication information and table and schema information.
The following code snippets show several common examples for PBIDS files, but they aren't complete or
comprehensive. For other data sources, you can refer to the Data Source Reference (DSR) format for protocol
and address information.
These examples are for convenience only, aren't meant to be comprehensive, and don't include all supported
connectors in DSR format. An administrator or organization can create their own data sources using these
examples as guides, from which they can create and support their own data source files.
Azure AS

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "analysis-services",
"address": {
"server": "server-here"
},
}
}
]
}

Folder

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "folder",
"address": {
"path": "folder-path-here"
}
}
}
]
}

OData

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "odata",
"address": {
"url": "URL-here"
}
}
}
]
}

SAP BW
 {
"version": "0.1",
"connections": [
{
"details": {
"protocol": "sap-bw-olap",
"address": {
"server": "server-name-here",
"systemNumber": "system-number-here",
"clientId": "client-id-here"
},
}
}
]
}

SAP Hana

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "sap-hana-sql",
"address": {
"server": "server-name-here:port-here"
},
}
}
]
}

SharePoint list
The URL must point to the SharePoint site itself, not to a list within the site. Users get a navigator that allows
them to select one or more lists from that site, each of which becomes a table in the model.

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "sharepoint-list",
"address": {
"url": "URL-here"
},
}
}
]
}

SQL Server
 {
"version": "0.1",
"connections": [
{
"details": {
"protocol": "tds",
"address": {
"server": "server-name-here",
"database": "db-name-here (optional) "
}
},
"options": {},
"mode": "DirectQuery"
}
]
}

Text file

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "file",
"address": {
"path": "path-here"
}
}
}
]
}

Web

{
"version": "0.1",
"connections": [
{
"details": {
"protocol": "http",
"address": {
"url": "URL-here"
}
}
}
]
}

Dataflow
 {
"version": "0.1",
"connections": [
{
"details": {
"protocol": "powerbi-dataflows",
"address": {
"workspace":"workspace id (Guid)",
"dataflow":"optional dataflow id (Guid)",
"entity":"optional entity name"
}
}
}
]
}

Next steps
You can do all sorts of things with Power BI Desktop. For more information on its capabilities, check out the
following resources:
What is Power BI Desktop?
Query overview with Power BI Desktop
Data types in Power BI Desktop
Shape and combine data with Power BI Desktop
Common query tasks in Power BI Desktop
 Create a report on a SharePoint List
9/9/2020 • 2 minutes to read • Edit Online

Many teams and organizations use Lists in SharePoint Online to store data because it's easy to set up and easy for
users to update. Sometimes a chart is a much easier way for users to quickly understand the data rather than
looking at the list itself. In this tutorial, we show how to transform your SharePoint List data into a Power BI report.
Watch this five-minute tutorial video, or scroll down for step-by-step instructions.
https://www.youtube.com/embed/OZO3x2NF8Ak

Part 1: Connect to your SharePoint List

1. If you don't have it already, download and install Power BI Desktop.
2. Open Power BI Desktop and in the Home tab of the ribbon, select Get Data > More .
3. Select Online Ser vices , then select SharePoint Online List .

4. Select Connect .
5. Find the address (also known as a URL) of your SharePoint Online site that contains your list. From a page in
SharePoint Online, you can usually get the site address by selecting Home in the navigation pane, or the
icon for the site at the top, then copying the address from your web browser's address bar.
Watch a video of this step:
https://www.youtube.com/embed/OZO3x2NF8Ak?start=48&end=90
6. In Power BI Desktop, paste the address into the Site URL field in the open dialog box.
7. You may or may not see a SharePoint access screen like the following image. If you don't see it, skip to step
10. If you do see it, select Microsoft Account on the left side of the page.
 8. Select Sign In and enter the user name and password you use to sign in to Microsoft 365.

9. When you finish signing in, select Connect .

10. On the left side of the Navigator, select the checkbox beside the SharePoint list you want to connect to.

11. Select Load . Power BI loads your list data into a new report.

Part 2: Create a report

1. On the left side, select the Data icon to see that your SharePoint list data was loaded.
2. Make sure your list columns with numbers show the Sum, or Sigma, icon in the Fields pane on the right.
For any that don't, select the column header in the table view, select the Modeling tab, then change the
Data type to Decimal Number or Whole Number , depending on the data. If prompted to confirm your
change, select Yes . If your number is a special format, like currency, you can also choose that by setting the
Format .
Watch a video of this step:
https://www.youtube.com/embed/OZO3x2NF8Ak?start=147&end=204
3. On the left side, select the Repor t icon.
4. Select columns you want to visualize by selecting the checkbox beside them in the Fields pane on the right.
 Watch a video of this step:
https://www.youtube.com/embed/OZO3x2NF8Ak?start=215&end=252
5. Change the visual type if you need to.
6. You can create multiple visualizations in the same report by unselecting the existing visual then selecting
checkboxes for other columns in the Fields pane.
7. Select Save to save your report.
 Connect to LinkedIn Sales Navigator in Power BI
Desktop
9/9/2020 • 3 minutes to read • Edit Online

In Power BI Desktop , you can connect to LinkedIn Sales Navigator to help find and build relationships just like
any other data source in Power BI Desktop, and create ready-made reports about your progress.

To connect to LinkedIn data using the LinkedIn Sales Navigator , you need to have a LinkedIn Sales Navigator
Enterprise plan, and either be an Admin or Reporting User on the Sales Navigator Contract.
The following video provides a quick tour and tutorial for using the LinkedIn Sales Navigator template app,
which is described in detail later in this article.

Connect to LinkedIn Sales Navigator

To connect to LinkedIn Sales Navigator data, select Get Data from the Home ribbon in Power BI Desktop. Select
Online Ser vices from the categories on the left, then scroll until you see LinkedIn Sales Navigator (Beta) .
You'll be advised that you're connecting to a third-party connecter that's still under development.

When you select Continue , you're prompted to specify which data you want.
In the LinkedIn Sales Navigator window that appears, select which data you want to return, either All contacts or
Selected contacts from the first drop-down selector. You can then specify the start and end dates to constrain the
data it receives to a particular time window.
Once you've provided the information, Power BI Desktop connects to the data associated with your LinkedIn Sales
Navigator contract. Use the same email address you use to sign in to LinkedIn Sales Navigator through the website.
When you connect successfully, you're prompted to select which data from your LinkedIn Sales Navigator contract
from a Navigator window.
You can create whatever reports you like with your LinkedIn Sales Navigator data. To make things easier, there is
also a LinkedIn Sales Navigator .PBIX file that you can download, that has sample data already provided, so you can
get familiar with the data and the reports, without having to start from scratch.
You can download the PBIX file from the following location:
PBIX for LinkedIn Sales Navigator
In addition to the PBIX file, the LinkedIn Sales Navigator also has a template app that you can download and use,
too. The next section describes the template app in detail.

Using the LinkedIn Sales Navigator template app

To make using the LinkedIn Sales Navigator as easy as possible, you can use the template app that automatically
creates a ready-made report from your LinkedIn Sales Navigator data.
When you download the app, you can select whether to connect to your data, or explore the app with sample data.
You can always go back and connect to your own LinkedIn Sales Navigator data after you explore the sample data.

You can get the LinkedIn Sales Navigator template app from the following link:
LinkedIn Sales Navigator template app
The template app provides four tabs to help analyze and share your information:
Usage
Search
InMail
SSI
The Usage tab shows your overall LinkedIn Sales Navigator data.
The Search tab lets you drill deeper into your search results:

The InMail provides insights into your InMail usage, including number of InMails sent, acceptance rates, and other
useful information:
The SSI tab provides additional details into your social selling index (SSI):

To go from the sample data to your own data, select edit app in the top-right corner (the pencil icon) and then
select Connect your data from the screen that appears.
From there you can connect your own data, selecting how many days of data to load. You can load up to 365 days
of data. You'll need to sign in, again using the same email address you use to sign in to LinkedIn Sales Navigator
through the website.

the template app then refreshes the data in the app with your data. You can also set up a scheduled refresh, so the
data in your app is as current as your refresh frequency specifies.
Once the data updates, you can see the app populated with your own data.

Getting help
If you run into problems when connecting to your data, you can contact LinkedIn Sales Navigator support at
https://www.linkedin.com/help/sales-navigator.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Get webpage data by providing examples
9/9/2020 • 2 minutes to read • Edit Online

Getting data from a web page lets users easily extract data from web pages, and import that data into Power BI
Desktop. Often however, data on Web pages aren't in tidy tables that are easy to extract. Getting data from such
pages can be challenging, even if the data is structured and consistent.
There's a solution. With the Get Data from Web by example feature, you can essentially show Power BI Desktop
which data you want to extract by providing one or more examples within the connector dialog. Power BI Desktop
gathers other data on the page that match your examples. With this solution you can extract all sorts of data from
Web pages, including data found in tables and other non-table data.

Prices in graphics are for example purposes only.

Using Get Data from Web by example

Select Get Data from the Home ribbon menu. In the dialog box that appears, select Other from the categories in
the left pane, and then select Web . Select Connect to continue.
In From Web , enter the URL of the Web page from which you'd like to extract data. In this article, we'll use the
Microsoft Store Web page, and show how this connector works.
If you want to follow along, you can use the Microsoft Store URL that we use in this article:

https://www.microsoft.com/store/top-paid/games/xbox?category=classics

When you select OK , you're taken to the Navigator dialog box where any autodetected tables from the Web page
are presented. In the case shown in the image below, no tables were found. Select Add table using examples to
provide examples.
Add table using examples presents an interactive window where you can preview the content of the Web page.
Enter sample values of the data you want to extract.
In this example, we'll extract the Name and Price for each of the games on the page. We can do that by specifying a
couple of examples from the page for each column. As you enter examples, Power Query extracts data that fits the
pattern of example entries using smart data extraction algorithms.
 NOTE
Value suggestions only include values less than or equal to 128 characters in length.

Once you're happy with the data extracted from the Web page, select OK to go to Power Query Editor. You can
apply more transformations or shape the data, such as combining this data with other data our sources.

From there, you can create visuals or otherwise use the Web page data when creating your Power BI Desktop
reports.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
Add a column from an example in Power BI Desktop
Connect to webpages from Power BI Desktop
Data sources in Power BI Desktop
Shape and combine data in Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to datasets in the Power BI service from
Power BI Desktop
9/9/2020 • 8 minutes to read • Edit Online

You can establish a live connection to a shared dataset in the Power BI service, and create many different reports
from the same dataset. You can create your perfect data model in Power BI Desktop and publish it to the Power BI
service. Then you and others can create multiple different reports in separate .pbix files from that common data
model, and save them to different workspaces. This feature is called Power BI service live connection.

There are all sorts of benefits of this feature, including best practices, which we discuss during this article. We
recommend you review the considerations and limitations of this feature.

Using a Power BI service live connection for report lifecycle

management
One challenge with the popularity of Power BI is the proliferation of reports, dashboards, and their underlying data
models. It's easy to create compelling reports in Power BI Desktop, then publish those reports in the Power BI
service, and to create great dashboards from those datasets. Since so many people do so, often using the same or
nearly the same datasets, knowing which report was based on which dataset and how fresh each dataset might be
becomes a challenge. The Power BI service live connection addresses that challenge, and makes creating, sharing,
and expanding upon common-dataset reports and dashboards easier and consistent.
Create a dataset everyone can use, then share it
Let's say Anna is a business analyst is on your team. Anna is skilled at creating good data models, often called
datasets. Anna can create a dataset and report, and then share that report in the Power BI service.
Everyone loves Anna's report and dataset. That's where the trouble would begin. Everyone on Anna's team would
attempt to create their own version of that dataset, then share their own reports with the team. All of the sudden,
there would be a multitude of reports from different datasets in your team's workspace in the Power BI service.
Which was the most recent? Were the datasets the same, or only almost? What were the differences? With the
Power BI service live connection feature, all that can change for the better. In the next section, we see how others
can use Anna's published dataset for their own reports, in their own workspaces, and enable everyone to use the
same solid, vetted, published dataset to build their unique reports.
Connect to a Power BI service dataset using a live connection
Anna creates a report and creates the dataset it's based upon. Anna then publishes it to the Power BI service. The
report shows up in the team's workspace in the Power BI service. If Anna saves it to a new experience workspace.
Anna can set Build permission to make it available to everyone in and out of their workspace to see and use.
To learn more about the new experience workspaces, see workspaces.
Other members in and out of Anna's workspace can now establish a live connection to Anna's shared data model
using the Power BI service live connection feature. They can create their own unique reports, from their original
dataset, in their own new experience workspaces.
In the following image, you see how Anna creates one Power BI Desktop report, and publishes it, which includes its
data model, to the Power BI service. Then others can connect to Anna's data model using the Power BI service live
connection, and create their own unique reports in their own workspaces, based on Anna's dataset.
 NOTE
If you save your dataset to a classic shared workspace, only members of that workspace build reports on your dataset. To
establish a Power BI service live connection, the dataset to which you connect must be in a shared workspace of which you
are a member.

Step by step for using the Power BI service live connection

Now that we know how useful the Power BI service live connection is, and how you can use it as a best practice
approach to report lifecycle management, let's walk through the steps that get us from Anna's great report and
dataset to a shared dataset that her Power BI teammates can use.
Publish a Power BI report and dataset
The first step in managing the report lifecycle using a Power BI service live connection is to have a report and
dataset that teammates want to use. So Anna must first publish the report from Power BI Desktop. Select Publish
from the Home ribbon in Power BI Desktop.

If Anna isn't signed in to the Power BI service account, Power BI prompts Anna to do so.

From there, Anna can choose the workspace destination to which the report and dataset will be published.
Remember, if Anna saves it to a new experience workspace, then anyone with Build permission can have access to
that dataset. Build permission is set in the Power BI service, after publishing. If work is saved to a classic workspace
only members who have access to the workspace where a report is published can access its dataset using a Power
BI service live connection.
The publishing process begins, and Power BI Desktop shows the progress.

Once complete, Power BI Desktop shows you success, and provides a couple links to get you to the report itself in
the Power BI service, and a link to get quick insights about the report.

Now that your report with its dataset is in the Power BI service, you can also promote it. Promotion means that you
attest to its quality and reliability. You can even request that it be certified by a central authority in your Power BI
tenant. With either of these endorsements, your dataset always appears at the top of the list when people are
looking for datasets. For more information, see Promote your dataset.
The last step is to set Build permission for the dataset the report is based on. Build permission determines who can
see and use your dataset. You can set it in the workspace itself, or when you share an app from the workspace. For
more information, see Build permission for shared datasets.
Next, let's see how other teammates who have access to the workspace where the report and dataset were
published can connect to the dataset and build their own reports.
Establish a Power BI service live connection to the published dataset
To establish a connection to the published report, and create your own report based on the published dataset,
select Get Data from the Home ribbon in Power BI Desktop, select Power Platform in the left pane, and then
select Power BI datasets .
If you're not signed in, Power BI prompts you to sign in. Once signed in, Power BI shows which workspaces you're a
member of. You can select which workspace contains the dataset to which you want to establish a Power BI service
live connection.
The datasets in the list are all the shared datasets you have Build permission for, in any workspace. You can search
for a specific dataset and see its name, owner, the workspace where it resides, and when it was last refreshed. You
also see ENDORSEMENT for datasets, either certified or promoted, at the top of the list.

When you select Create , you establish a live connection to the selected dataset. Power BI Desktop loads the fields
and their values that you see into Power BI Desktop in real time.

Now you and others can create and share custom reports, all from the same dataset. This approach is a great way
to have one knowledgeable person create a well-formed dataset, such as what Anna does. Many teammates can
use that shared dataset to create their own reports.

Limitations and considerations

When using the Power BI service live connection, there are a few limitations and considerations to keep in mind.
Only users with Build permission for a dataset can connect to a published dataset using the Power BI service live
connection.
Free users only see datasets in their My Workspace and in Premium-based workspaces.
Since this connection is a live connection, left-navigation and modeling are disabled. You can only connect to
one dataset in each report. This behavior is similar to the behavior when connected to SQL Server Analysis
Services.
Since this connection is a live connection, row-level security (RLS) and other such connection behaviors are
enforced. This is the same as when connected to SQL Server Analysis Services.
If the owner modifies the original shared .pbix file, the dataset and report that is shared in the Power BI service
is overwritten. Reports based on that dataset aren't overwritten, but any changes to the dataset are reflected in
the report.
Members of a workspace can't replace the originally shared report. Attempts to do so result in a warning that
prompts you to rename the file, and publish.
If you delete the shared dataset in the Power BI service, then other reports based on that dataset will no longer
work properly or display their visuals.
For Content Packs, you must first create a copy of a content pack before using it as a basis for sharing a .pbix
report and dataset to the Power BI service.
For Content Packs from My Organization, once copied, you can't replace the report created on the service or a
report created as part of copying a Content Pack with a live connection. Attempts to do so result in a warning
that prompts you to rename the file, and publish. In this situation, you can only replace published live connected
reports.
Deleting a shared dataset in the Power BI service means no one can access that dataset any longer from Power
BI Desktop.
Reports that share a dataset on the Power BI service don't support automated deployments using the Power BI
REST API.
 Import Excel workbooks into Power BI Desktop
9/9/2020 • 4 minutes to read • Edit Online

With Power BI Desktop, you can easily import Excel workbooks that contain Power Query queries, Power Pivot
models, and Power View worksheets into Power BI Desktop. Power BI Desktop automatically creates reports and
visualizations based on the Excel workbook. Once imported, you can continue to improve and refine those reports
with Power BI Desktop, using the existing features and new features released with each Power BI Desktop monthly
update.

How do I import an Excel workbook?

1. To import an Excel workbook into Power BI Desktop, select File > Impor t > Power Quer y, Power Pivot,
Power View .

2. From the Open window, select an Excel workbook to import.

Although there's currently no limitation on the size or number of objects in the workbook, larger workbooks
take longer for Power BI Desktop to analyze and import.

NOTE
To load or import Excel files from shared OneDrive for Business folders or from Microsoft 365 group folders, use the
URL of the Excel file, and input it into the Web data source in Power BI Desktop. There are a few steps you need to
follow to properly format the OneDrive for Business URL; for information and the correct series of steps, see Use
OneDrive for Business links in Power BI Desktop.

3. From the import dialog box that appears, select Star t .

 Power BI Desktop analyzes the workbook and converts it into a Power BI Desktop file (.pbix). This action is a
one-time event; once the Power BI Desktop file is created with these steps, the Power BI Desktop file has no
dependence on the original Excel workbook, and can be modified, saved, and shared without affecting the
original workbook.
After the import is finished, a summary page appears that describes the items that were converted, and also
lists any items that couldn't be imported.

4. Select Close .
Power BI Desktop imports the Excel workbook and loads a report based on the workbook contents.
After the workbook is imported, you can continue working on the report. You can create new visualizations, add
data, or create new report pages by using any of the features and capabilities included in Power BI Desktop.

Which workbook elements are imported?

Power BI Desktop can import the following elements, commonly referred to as objects, in Excel.

O B JEC T IN EXC EL W O RK B O O K F IN A L RESULT IN P O W ER B I DESK TO P F IL E

Power Query queries All Power Query queries from Excel are converted to queries in
Power BI Desktop. If there are query groups defined in the
Excel Workbook, the same organization is replicated in Power
BI Desktop. All queries are loaded unless they're set to Only
Create Connection in the Impor t Data Excel dialog box.
The load behavior is customized by selecting Proper ties from
the Home tab of Power Query Editor in Power BI Desktop.

Power Pivot external data connections All Power Pivot external data connections are converted to
queries in Power BI Desktop.
 O B JEC T IN EXC EL W O RK B O O K F IN A L RESULT IN P O W ER B I DESK TO P F IL E

Linked tables or current workbook tables If there's a worksheet table in Excel linked to the data model,
or linked to a query (by using From Table or the
Excel.CurrentWorkbook() function in M), the following options
are presented:
1. Impor t the table to the Power BI Desktop file .
This table is a one-time snapshot of the data, after
which the data is read-only in the table in Power BI
Desktop. There's a size limitation of 1 million characters
(total, combining all column headers and cells) for
tables created using this option.
2. Keep a connection to the original workbook .
Alternatively, you can keep a connection to the original
Excel Workbook and Power BI Desktop retrieves the
latest content in this table with each refresh, just like
any other query created against an Excel workbook in
Power BI Desktop.

Data model calculated columns, measures, KPIs, data These data model objects are converted to the equivalent
categories, and relationships objects in Power BI Desktop. Note there are certain data
categories that aren't available in Power BI Desktop, such as
Image. In these cases, the data category information is reset
for the columns in question.

Power View worksheets A new report page is created for each Power View worksheet
in Excel. The name and order of these report pages match the
original Excel workbook.

Are there any limitations to importing a workbook?

There are a few limitations to importing a workbook into Power BI Desktop:
External connections to SQL Ser ver Analysis Ser vices tabular models: In Excel 2013, it's possible to
create a connection to SQL Server Analysis Services tabular models and create Power View reports on top of
these models without the need to import the data. This type of connection is currently not supported as part of
importing Excel workbooks into Power BI Desktop. As a workaround, you must recreate these external
connections in Power BI Desktop.
Hierarchies: This type of data model object is currently not supported in Power BI Desktop. As such, hierarchies
are skipped as part of importing an Excel workbook into Power BI Desktop.
Binar y data columns: This type of data model column is currently not supported in Power BI Desktop. Binary
data columns are removed from the resulting table in Power BI Desktop.
Unsuppor ted Power View elements: There are a few features in Power View that aren't available in Power BI
Desktop, such as themes or certain types of visualizations (scatter chart with play axis, drill-down behaviors, and
so on). These unsupported visualizations result in Unsupported Visualization messages on their corresponding
locations in the Power BI Desktop report, which you can delete or reconfigure as needed.
Named Ranges using From Table in Power Quer y, or using Excel.CurrentWorkbook in M: Importing
this named range data into Power BI Desktop isn't currently supported, but it's a planned update. Currently,
these named ranges are loaded into Power BI Desktop as a connection to the external Excel workbook.
PowerPivot to SSRS: PowerPivot external connections to SQL Server Reporting Services (SSRS) aren't
currently supported, because that data source isn't currently available in Power BI Desktop.
 Connect to data by using Power BI Desktop generic
interfaces
9/9/2020 • 4 minutes to read • Edit Online

You can connect to a multitude of different data sources in Power BI Desktop , using built-in data connectors that
range from Access databases to Zendesk resources, as shown in the Get Data window. You can also connect to
all sorts of other data sources to further expand your connectivity options, by using the generic interfaces (such as
ODBC or REST APIs ) built into Power BI Desktop .

Power BI Desktop data interfaces

Power BI Desktop includes an ever-growing collection of data connectors that are built to connect to a specific
data source. For example, the SharePoint List data connector provides specific fields and supporting information
during the connection sequence that are designed for SharePoint Lists , which is the case with other data sources
found in the window that appears when you select Get Data > More... (shown in the previous image).
In addition, Power BI Desktop lets you connect to data sources that aren't identified in the Get Data lists, by
using one of the following generic data interfaces:
ODBC
OLE DB
 OData
REST APIs
R Scripts
By providing the appropriate parameters in the connection windows that these generic interfaces provide, the
world of data sources you can access and use in Power BI Desktop grows significantly.
In the following sections, you can find lists of data sources that can be accessed by these generic interfaces.
Can't find the data source you wanted to use with Power BI Desktop ? Submit your idea to the Power BI team's list
of ideas and requests.

Data sources accessible through ODBC

The ODBC connector in Power BI Desktop lets you import data from any third-party ODBC driver simply by
specifying a Data Source Name (DSN) or a connection string. As an option, you can also specify a SQL statement
to execute against the ODBC driver.

The following list details a few examples of data sources to which Power BI Desktop can connect by using the
generic ODBC interface.

P O W ER B I DESK TO P GEN ERIC

C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

ODBC Cassandra Cassandra ODBC driver

ODBC Couchbase DB Couchbase and Power BI

ODBC DynamoDB DynamoDB ODBC driver

ODBC Google BigQuery BigQuery ODBC driver

 P O W ER B I DESK TO P GEN ERIC
C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

ODBC HBase HBase ODBC driver

ODBC Hive Hive ODBC driver

ODBC IBM Netezza IBM Netezza information

ODBC Presto Presto ODBC driver

ODBC Project Online Project Online article

ODBC Progress OpenEdge Progress OpenEdge ODBC driver blog

post

Data sources accessible through OLE DB

The OLE DB connector in Power BI Desktop lets you import data from any third-party OLE DB driver simply by
specifying a connection string. As an option, you can also specify a SQL statement to execute against the OLE DB
driver.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic OLE DB interface.

P O W ER B I DESK TO P GEN ERIC

C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

OLE DB SAS OLE DB SAS provider for OLE DB

OLE DB Sybase OLE DB Sybase provider for OLE DB

Data sources accessible through OData
The OData connector in Power BI Desktop lets you import data from any OData URL simply by typing in or
pasting the OData URL. You can add multiple URL parts by typing or pasting those links in the text boxes provided
in the OData Feed window.

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic OData interface.

P O W ER B I DESK TO P GEN ERIC

C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

OData Coming soon Check back soon for OData data

sources

Data sources accessible through REST APIs

You can connect to data sources using the REST APIs and thereby use data from all sorts of data sources that
support REST .

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic REST APIs interface.

P O W ER B I DESK TO P GEN ERIC

C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

REST APIs Couchbase DB Couchbase REST API information

Data sources accessible through R Script

You can use R scripts to access data sources, and use that data in Power BI Desktop .

The following list details a few examples of the data sources to which Power BI Desktop can connect by using the
generic R scripts interface.

P O W ER B I DESK TO P GEN ERIC

C O N N EC TO R EXT ERN A L DATA SO URC E L IN K F O R M O RE IN F O RM AT IO N

R Script SAS Files R script guidance from CRAN

R Script SPSS Files R script guidance from CRAN

R Script R Statistical Files R script guidance from CRAN

Next steps
There are all sorts of data sources you can connect to using Power BI Desktop . For more information on data
sources, check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to PDF files in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a PDF file and use the included data from the file, just like any other data
source in Power BI Desktop.

The following sections describe how to connect to a PDF file , select data, and bring that data into Power BI
Desktop .
We always recommend upgrading to the most recent release of Power BI Desktop , which you can get from a link
in get Power BI Desktop.

Connect to a PDF file

To connect to a PDF file select Get Data from the Home ribbon in Power BI Desktop. Select File from the
categories on the left, and you see PDF .
You're prompted to provide the location of the PDF file you want to use. Once you provide the file location and the
PDF file loads, a Navigator window appears and displays the data available from the file, from which you can
select one or multiple elements to import and use in Power BI Desktop .
Selecting a checkbox next to discovered elements in the PDF file displays them in the right pane. When you're ready
to import, select the Load button to bring the data into Power BI Desktop .
Beginning with the November 2018 release of Power BI Desktop , you can specify the Star t page and End Page
as optional parameters for your PDF connection. You can also specify these parameters in the M formula language,
using the following format:
Pdf.Tables(File.Contents("c:\sample.pdf"), [StartPage=10, EndPage=11])

Limitations and considerations

When working with the PDF connector on datasets in a Premium capacity, the PDF connector does not properly
make the connection. To enable the PDF connector to work on a dataset in a Premium capacity, configure that
dataset to use a gateway, and confirm the connection to that dataset goes through the gateway.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Adobe Analytics in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop , you can connect to Adobe Analytics and use the underlying data just like any other data
source in Power BI Desktop.

Connect to Adobe Analytics data

To connect to Adobe Analytics data, select Get Data from the Home ribbon in Power BI Desktop. Select Online
Ser vices from the categories on the left, and you see Adobe Analytics connector .
In the Adobe Analytics window that appears, select the Sign in button, and provide your credentials to sign in to
your Adobe Analytics account. The Adobe sign in window appears, as shown in the following image.
When prompted, put in your username and password. Once the connection is established, you can preview and
select multiple dimensions and measures within the Power BI Navigator dialog to create a single tabular output.
You can also provide any necessary input parameters required for the selected items.

You can Load the selected table, which brings the entire table into Power BI Desktop , or you can Edit the query,
which opens Quer y Editor so you can filter and refine the set of data you want to use, and then load that refined
set of data into Power BI Desktop .
Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to an Oracle database with Power BI
Desktop
9/9/2020 • 3 minutes to read • Edit Online

To connect to an Oracle database with Power BI Desktop, the correct Oracle client software must be installed on the
computer running Power BI Desktop. The Oracle client software you use depends on which version of Power BI
Desktop you've installed: 32-bit or 64-bit. It also depends on your version of Oracle server.
Supported Oracle versions:
Oracle Server 9 and later
Oracle Data Access Client (ODAC) software 11.2 and later

NOTE
If you're configuring an Oracle database for Power BI Desktop, On Premises Data Gateway or Power BI Report Server, consult
the information in the Oracle Connection Type article.

Determining which version of Power BI Desktop is installed

To determine which version of Power BI Desktop is installed, select File > Help > About , then check the Version
line. In the following image, a 64-bit version of Power BI Desktop is installed:

Install the Oracle client

For the 32-bit version of Power BI Desktop, download and install the 32-bit Oracle client.
For the 64-bit version of Power BI Desktop, download and install the 64-bit Oracle client.
 NOTE
Choose a version of Oracle Data Access Client (ODAC) which is compatible with your Oracle Server. For instance, ODAC 12.x
does not always support Oracle Server version 9. Choose the Windows installer of the Oracle Client. During the setup of the
Oracle client, make sure you enable Configure ODP.NET and/or Oracle Providers for ASP.NET at machine-wide level by
selecting the corresponding checkbox during the setup wizard. Some versions of the Oracle client wizard selects the checkbox
by default, others do not. Make sure that checkbox is selected so that Power BI can connect to your Oracle database.

Connect to an Oracle database

After you install the matching Oracle client driver, you can connect to an Oracle database. To make the connection,
take the following steps:
1. From the Home tab, select Get Data .
2. From the Get Data window that appears, select More (if necessary), select Database > Oracle database ,
and then select Connect .

3. In the Oracle database dialog that appears, provide the name of the Ser ver , and select OK . If a SID is
required, specify it by using the format: ServerName/SID, where SID is the unique name of the database. If
the ServerName/SID format doesn't work, use ServerName/ServiceName, where ServiceName is the alias
you use to connect.
 NOTE
If you are using a local database, or autonomous database connections, you may need to place the server name in
quotation marks to avoid connection errors.

4. If you want to import data by using a native database query, put your query in the SQL statement box,
which appears when you expand the Advanced options section of the Oracle database dialog.

5. After you've entered your Oracle database information in the Oracle database dialog (including any
optional information such as a SID or a native database query), select OK to connect.
6. If the Oracle database requires database user credentials, input those credentials in the dialog when
prompted.

Troubleshooting
You might encounter any of several errors from Oracle when the naming syntax is either incorrect or not
configured properly:
ORA-12154: TNS:could not resolve the connect identifier specified.
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.
ORA-12541: TNS:no listener.
ORA-12170: TNS:connect timeout occurred.
ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA.
These errors might occur if the Oracle client either isn't installed or isn't configured properly. If it's installed, verify
that the tnsnames.ora file is properly configured and you're using the proper net_service_name. You also need to
make sure that the net_service_name is the same between the machine that uses Power BI Desktop and the
machine that runs the gateway. For more information, see Install the Oracle client.
You might also encounter a compatibility issue between the Oracle server version and the Oracle Data Access Client
version. Typically, you want these versions to match, as some combinations are incompatible. For instance, ODAC
12.x does not support Oracle Server version 9.
If you downloaded Power BI Desktop from the Microsoft Store, you might be unable to connect to Oracle databases
because of an Oracle driver issue. If you encounter this issue, the error message returned is: Object reference not
set. To address the issue, do one of these steps:
Download Power BI Desktop from the Download Center instead of Microsoft Store.
If you want to use the version from Microsoft Store: on your local computer, copy oraons.dll from
12.X.X\client_X to 12.X.X\client_X\bin, where X represents version and directory numbers.
If you see the error message, Object reference not set, in the Power BI Gateway when you connect to an Oracle
database, follow the instructions in Manage your data source - Oracle.
If you're using Power BI Report Server, consult the guidance in the Oracle Connection Type article.
 Run Python scripts in Power BI Desktop
9/9/2020 • 3 minutes to read • Edit Online

You can run Python scripts directly in Power BI Desktop and import the resulting datasets into a Power BI Desktop
data model.

Install Python
To run Python scripts in Power BI Desktop, you need to install Python on your local machine. You can download
Python from the Python website. The current Python scripting release supports Unicode characters and spaces in
the installation path.
Install required Python packages
The Power BI Python integration requires the installation of two Python packages:
Pandas. A software library for data manipulation and analysis. It offers data structures and operations for
manipulating numerical tables and time series. Your imported data must be in a pandas data frame. A data
frame is a two-dimensional data structure. For example, data is aligned in a tabular fashion in rows and
columns.
Matplotlib. A plotting library for Python and its numerical mathematics extension NumPy. It provides an object-
oriented API for embedding plots into applications using general-purpose GUI toolkits, such as Tkinter,
wxPython, Qt, or GTK+.
In a console or shell, use the pip command-line tool to install the two packages. The pip tool is packaged with more
recent Python versions.

pip install pandas

pip install matplotlib

Enable Python scripting

To enable Python scripting:
1. In Power BI Desktop, select File > Options and settings > Options > Python scripting . The Python
script options page appears.
2. If necessary, specify your local Python installation path in Detected Python home directories .
In the above image, the Python's installation local path is C:\Python. Make sure the path is for the local
Python installation you want Power BI Desktop to use.
3. Select OK .
Once you specify your Python installation, you’re ready to begin running Python scripts in Power BI Desktop.

Run Python scripts

In just a few steps, you can run Python scripts and create a data model. From this model, you can create reports
and share them on the Power BI service.
Prepare a Python script
First, create a script in your local Python development environment and make sure it runs successfully. For
example, here's a simple Python script that imports pandas and uses a data frame:

import pandas as pd
data = [['Alex',10],['Bob',12],['Clarke',13]]
df = pd.DataFrame(data,columns=['Name','Age'],dtype=float)
print (df)
When run, this script returns:

Name Age
0 Alex 10.0
1 Bob 12.0
2 Clarke 13.0

When preparing and running a Python script in Power BI Desktop, there are a few limitations:
Only pandas data frames are imported, so make sure the data you want to import to Power BI is represented in
a data frame
Any Python script that runs longer than 30 minutes times out
Interactive calls in the Python script, such as waiting for user input, halts the script’s execution
When setting the working directory within the Python script, you must define a full path to the working
directory, rather than a relative path
Nested tables are currently not supported
Run your Python script and import data
To run your Python Script in Power BI Desktop:
1. In the Home ribbon, select Get Data > Other .
2. Select Other > Python script as shown in the following image:
3. Select Connect . Your local latest installed Python version is selected as your Python engine. Copy your
script into the Python script dialog box that appears. Here, we enter the simple Python script shown
before.
4. Select OK . If the script runs successfully, the Navigator appears and you can load the data and use it. For
the example, select df , as shown in the image, then Load .

Troubleshooting
If Python isn't installed or identified, a warning displays. You can also see a warning if you have multiple local
machine installations. Revisit and review the previous Install Python and Enable Python scripting sections.
Using custom Python distributions
Power BI executes scripts directly by using the python.exe executable from a user-provided directory (provided
through the settings page). Distributions that require an extra step to prepare the environment (for example,
Conda) might encounter an issue where their execution fails.
We recommend using the official Python distribution from https://www.python.org/ to avoid related issues.
As a possible solution, you can start Power BI Desktop from your custom Python environment prompt.
Refresh
You can refresh a Python script in Power BI Desktop. To refresh, go to the Home ribbon and select Refresh . When
you refresh a Python script, Power BI Desktop runs the Python script again.

Known Limitations
Currently you won't be able to use Python scripts in reports created with Enhanced Metadata (Preview) feature
enabled. Existing reports will continue to work. For more information check out Using enhanced dataset metadata
(preview).

Next steps
Take a look at the following additional information about Python in Power BI.
Create Python Visuals in Power BI Desktop
Use an external Python IDE with Power BI
 Use Python in Query Editor
9/9/2020 • 4 minutes to read • Edit Online

You can use Python , a programming language widely used by statisticians, data scientists, and data analysts, in the
Power BI Desktop Quer y Editor . This integration of Python into Quer y Editor lets you perform data cleansing
using Python, and perform advanced data shaping and analytics in datasets, including completion of missing data,
predictions, and clustering, just to name a few. Python is a powerful language, and can be used in Quer y Editor
to prepare your data model and create reports.

Installing Python
To use Python in Power BI Desktop's Quer y Editor , you need to install Python on your local machine. You can
download and install Python for free from many locations, including the Official Python download page, and the
Anaconda.

Using Python in Query Editor

To show how to use Python in Quer y Editor , take this example from a stock market dataset, based on a .CSV file
that you can download from here and follow along. The steps for this example are the following:
1. First, load your data into Power BI Desktop . In this example, load the EuStockMarkets_NA.csv file and select
Get Data > CSV from the Home ribbon in Power BI Desktop .

2. Select the file and select Open , and the CSV is displayed in the CSV file dialog.
3. Once the data is loaded, you'll see it in the Fields pane in Power BI Desktop.

4. Open Quer y Editor by selecting Edit Queries from the Home tab in Power BI Desktop .
5. In the Transform tab, select Run Python Script and the Run Python Script editor appears (shown in the
next step). Notice that rows 15 and 20 suffer from missing data, as do other rows you can't see in the
following image. The steps below show how Python can (and will) complete those rows for you.

6. For this example, enter the following script code:

import pandas as pd
completedData = dataset.fillna(method='backfill', inplace=False)
dataset["completedValues"] = completedData["SMI missing values"]

NOTE
You'll need to have the pandas library installed in your Python environment for the previous script code to work
properly. To install pandas, run the following command in your Python installation: | > pip install pandas

When put into the Run Python Script dialog, the code looks like the following:
7. After selecting OK , Quer y Editor displays a warning about data privacy.

8. For the Python scripts to work properly in the Power BI service, all data sources need to be set to public. For
more information about privacy settings and their implications, see Privacy Levels.

Notice a new column in the Fields pane called completedValues. Notice there are a few missing data
 elements, such as on row 15 and 18. Take a look at how Python handles that in the next section.
With just five lines of Python script, Quer y Editor filled in the missing values with a predictive model.

Creating visuals from Python script data

Now we can create a visual to see how the Python script code using the pandas library completed the missing
values, as shown in the following image:

Once that visual is complete, and any other visuals you might want to create using Power BI Desktop , you can
save the Power BI Desktop file (which saves as a .pbix file) and then use the data model, including the Python
scripts that are part of it, in the Power BI service.

NOTE
Want to see a completed .pbix file with these steps completed? You're in luck - you can download the completed Power BI
Desktop file used in these examples right here.

Once you've uploaded the .pbix file to the Power BI service, a couple more steps are necessary to enable data
refresh (in the service) and to enable visuals to be updated in the service (the data needs access to Python for
visuals to be updated). The additional steps are the following:
Enable scheduled refresh for the dataset - to enable scheduled refresh for the workbook that contains
your dataset with Python scripts, see Configuring scheduled refresh, which also includes information about
Personal Gateway .
Install the Personal Gateway - you need a Personal Gateway installed on the machine where the file is
located, and where Python is installed; the Power BI service must access that workbook and re-render any
updated visuals. You can get more information on how to install and configure Personal Gateway.

Limitations
There are some limitations to queries that include Python scripts created in Quer y Editor :
All Python data source settings must be set to Public, and all other steps in a query created in Quer y Editor
must also be public. To get to data source settings, in Power BI Desktop select File > Options and
settings > Data source settings .
 From the Data Source Settings dialog, select the data source(s) and then select Edit Permissions... and
ensure that the Privacy Level is set to Public.

To enable scheduled refresh of your Python visuals or dataset, you need to enable Scheduled refresh and
have a Personal Gateway installed on the computer that houses the workbook and the Python installation.
For more information on both, see the previous section in this article, which provides links to learn more
about each.
Nested tables (table of tables) are currently not supported
There are all sorts of things you can do with Python and custom queries, so explore and shape your data just the
way you want it to appear.
 Use an external Python IDE with Power BI
9/9/2020 • 4 minutes to read • Edit Online

With Power BI Desktop , you can use your external Python IDE (Integrated Development Environment) to create
and refine Python scripts, then use those scripts in Power BI.

Enable an external Python IDE

You can launch your external Python IDE from Power BI Desktop and have your data automatically imported and
displayed in the Python IDE. From there, you can modify the script in that external Python IDE, then paste it back
into Power BI Desktop to create Power BI visuals and reports.
You can specify which Python IDE you would like to use, and have it launch automatically from within Power BI
Desktop .
Requirements
To use this feature, you need to install a Python IDE on your local computer. Power BI Desktop does not include,
deploy, or install the Python engine, so you must separately install Python on your local computer. You can choose
which Python IDE to use, with the following options:
You can install your favorite Python IDE, many of which are available for free, such as the Visual Studio Code
download page.
 Power BI Desktop also supports Visual Studio .
You can also install a different Python IDE and have Power BI Desktop launch that Python IDE by doing
one of the following:
You can associate .PY files with the external IDE you want Power BI Desktop to launch.
You can specify the .exe that Power BI Desktop should launch by selecting Other from the Python
Script Options section of the Options dialog. You can bring up the Options dialog by going to File
> Options and settings > Options .

If you have multiple Python IDEs installed, you can specify which will be launched by selecting it from the Detected
Python IDEs drop-down in the Options dialog.
By default, Power BI Desktop will launch Visual Studio Code as the external Python IDE if it's installed on your
local computer; if Visual Studio Code is not installed and you have Visual Studio , that will be launched instead.
If neither of those Python IDEs is installed, the application associated with .PY files is launched.
And if no .PY file association exists, it's possible to specify a path to a custom IDE in the Browse to your preferred
Python IDE section of the Options dialog. You can also launch a different Python IDE by selecting the Settings
gear icon beside the Launch Python IDE arrow icon, in Power BI Desktop .

Launch a Python IDE from Power BI Desktop

To launch a Python IDE from Power BI Desktop , take the following steps:
1. Load data into Power BI Desktop .
2. Select some fields from the Fields pane that you want to work with. If you haven't enabled script visuals yet,
 you'll be prompted to do so.

3. When script visuals are enabled, you can select a Python visual from the Visualizations pane, which
creates a blank Python visual that's ready to display the results of your script. The Python script editor
pane also appears.

4. Now you can select the fields you want to use in your Python script. When you select a field, the Python
script editor field automatically creates script code based on the field or fields you select. You can either
create (or paste) your Python script directly in the Python script editor pane, or you can leave it empty.
 NOTE
The default aggregation type for Python visuals is do not summarize.

5. You can now launch your Python IDE directly from Power BI Desktop . Select the Launch Python IDE
button, found on the right side of the Python script editor title bar, as shown below.

6. Your specified Python IDE is launched by Power BI Desktop, as shown in the following image (in this image,
Visual Studio Code is the default Python IDE).
 NOTE
Power BI Desktop adds the first three lines of the script so it can import your data from Power BI Desktop once
you run the script.

7. Any script you created in the Python script editor pane of Power BI Desktop appears starting in line 4
in your Python IDE. At this point, you can create your Python script in the Python IDE. Once your Python
script is complete in your Python IDE, you need to copy and paste it back into the Python script editor
pane in Power BI Desktop , excluding the first three lines of the script that Power BI Desktop
automatically generated. Do not copy the first three lines of script back into Power BI Desktop , those lines
were only used to import your data to your Python IDE from Power BI Desktop .
Known limitations
Launching a Python IDE directly from Power BI Desktop has a few limitations:
Automatically exporting your script from your Python IDE into Power BI Desktop is not supported.

Next steps
Take a look at the following additional information about Python in Power BI.
Running Python Scripts in Power BI Desktop
Create Power BI visuals using Python
 Create Power BI visuals by using Python
9/9/2020 • 5 minutes to read • Edit Online

With Power BI Desktop, you can use Python to visualize your data.

Prerequisites
Work through the Run Python scripts in Power BI Desktop tutorial using the following Python script:

import pandas as pd
df = pd.DataFrame({
'Fname':['Harry','Sally','Paul','Abe','June','Mike','Tom'],
'Age':[21,34,42,18,24,80,22],
'Weight': [180, 130, 200, 140, 176, 142, 210],
'Gender':['M','F','M','M','F','M','M'],
'State':['Washington','Oregon','California','Washington','Nevada','Texas','Nevada'],
'Children':[4,1,2,3,0,2,0],
'Pets':[3,2,2,5,0,1,5]
})
print (df)

The Run Python scripts in Power BI Desktop article shows you how to install Python on your local machine and
enable it for Python scripting in Power BI Desktop. This tutorial uses data from the above script to illustrate
creating Python visuals.

Create Python visuals in Power BI Desktop

1. Select the Python visual icon in the Visualizations pane.

2. In the Enable script visuals dialog box that appears, select Enable .
When you add a Python visual to a report, Power BI Desktop takes the following actions:
A placeholder Python visual image appears on the report canvas.
The Python script editor appears along the bottom of the center pane.
3. Next, drag the Age , Children , Fname , Gender , Pets , State , and Weight fields to the Values section
where it says Add data fields here .

Your Python script can only use fields added to the Values section. You can add or remove fields from the
Values section while working on your Python script. Power BI Desktop automatically detects field changes.

NOTE
The default aggregation type for Python visuals is do not summarize.

4. Now you can use the data you selected to create a plot.
As you select or remove fields, supporting code in the Python script editor is automatically generated or
removed.
 Based on your selections, the Python script editor generates the following binding code.
The editor created a dataset dataframe, with the fields you added.
The default aggregation is: do not summarize.
Similar to table visuals, fields are grouped and duplicate rows appear only once.

TIP
In certain cases, you might not want automatic grouping to occur, or you'll want all rows to appear, including
duplicates. If so, you can add an index field to your dataset that causes all rows to be considered unique and which
prevents grouping.

You can access columns in the dataset using their respective names. For example, you can code
dataset["Age"] in your Python script to access the age field.

5. With the dataframe automatically generated by the fields you selected, you're ready to write a Python script
that results in plotting to the Python default device. When the script is complete, select Run from the
Python script editor title bar.
Power BI Desktop replots the visual if any of the following events occur:
When you select Run from the Python script editor title bar
Whenever a data change occurs, due to data refresh, filtering, or highlighting
When you run a Python script that results in an error, the Python visual isn't plotted and a canvas error
message appears. For error details, select See details from the message.
To get a larger view of the visualizations, you can minimize the Python script editor .
Ok, let's create some visuals.

Create a scatter plot

Let's create a scatter plot to see if there's a correlation between age and weight.
1. Under Paste or type your script code here , enter this code:

import matplotlib.pyplot as plt

dataset.plot(kind='scatter', x='Age', y='Weight', color='red')
plt.show()

Your Python script editor pane should now look like this:
 The matplotlib library is imported to plot and create our visuals.
2. When you select the Run script button, the following scatter plot generates in the placeholder Python visual
image.

Create a line plot with multiple columns

Let's create a line plot for each person showing their number of children and pets. Remove or comment the code
under Paste or type your script code here and enter this Python code:

import matplotlib.pyplot as plt

ax = plt.gca()
dataset.plot(kind='line',x='Fname',y='Children',ax=ax)
dataset.plot(kind='line',x='Fname',y='Pets', color='red', ax=ax)
plt.show()

When you select the Run script button, the following line plot with multiple columns generates.
Create a bar plot
Let's create a bar plot for each person's age. Remove or comment the code under Paste or type your script
code here and enter this Python code:

import matplotlib.pyplot as plt

dataset.plot(kind='bar',x='Fname',y='Age')
plt.show()

When you select the Run script button, the following bar plot generates:

Security
IMPORTANT
Python scripts security: Python visuals are created from Python scripts, which could contain code with security or privacy
risks. When attempting to view or interact with an Python visual for the first time, a user is presented with a security warning
message. Only enable Python visuals if you trust the author and source, or after you review and understand the Python
script.

More information about plotting with Matplotlib, Pandas, and Python

This tutorial is designed to help you get started creating visuals with Python in Power BI Desktop. It barely
scratches the surface about the many options and capabilities for creating visual reports using Python, Pandas, and
the Matplotlib library. There's a lot more information out there, and here are a few links to get you started.
Documentation at the Matplotlib website.
Matplotlib Tutorial : A Basic Guide to Use Matplotlib with Python
Matplotlib Tutorial – Python Matplotlib Library with Examples
Pandas API Reference
Python visualizations in Power BI Service
Using Python Visuals in Power BI
Known limitations
Python visuals in Power BI Desktop have a few limitations:
Data size limitations. Data used by the Python visual for plotting is limited to 150,000 rows. If more than
150,000 rows are selected, only the top 150,000 rows are used and a message is displayed on the image.
Additionally, the input data has a limit of 250 MB.
Resolution. All Python visuals are displayed at 72 DPI.
Calculation time limitation. If a Python visual calculation exceeds five minutes the execution times out which
results in an error.
Relationships. As with other Power BI Desktop visuals, if data fields from different tables with no defined
relationship between them are selected, an error occurs.
Python visuals are refreshed upon data updates, filtering, and highlighting. However, the image itself isn't
interactive and can't be the source of cross-filtering.
Python visuals respond to highlighting other visuals, but you can't click on elements in the Python visual to
cross filter other elements.
Only plots that are plotted to the Python default display device are displayed correctly on the canvas. Avoid
explicitly using a different Python display device.
Python visuals do not support renaming input columns. Columns will be referred to by their original name
during script execution.

Next steps
Take a look at the following additional information about Python in Power BI.
Run Python Scripts in Power BI Desktop
Use an external Python IDE with Power BI
 Create visuals by using Python packages in the Power
BI service
9/9/2020 • 2 minutes to read • Edit Online

You can use the powerful Python programming language to create visuals in the Power BI service. Many Python
packages are supported in the Power BI service and more are being supported all the time.
The following sections provide an alphabetical table of which Python packages are supported in Power BI.

Request support for a new Python package

Supported Python packages for the Power BI ser vice are found in the following section, titled Suppor ted
Packages . If you would like to request support of an Python package not found in that list, please submit your
request to Power BI Ideas.

Requirements and Limitations of Python packages

There are a handful of requirements and limitations for Python packages:
Current Python runtime: Python 3.7.7.
The Power BI service, for the most part, supports Python packages with free and open-source software licenses
such as GPL-2, GPL-3, MIT+, and so on.
The Power BI service supports packages published in PyPI. The service does not support private or custom
Python packages. Users are encouraged to make their private packages available on PyPI prior to requesting the
package be available in the Power BI service.
For Python visuals in Power BI Desktop , you can install any package, including custom Python packages.
For security and privacy reasons, Python packages that provide client-server queries over the World-Wide Web
in the service, are not supported. Networking is blocked for such attempts.
The approval process for including a new Python package has a tree of dependencies; some dependencies
required to be installed in the service cannot be supported.

Python packages that are supported in Power BI

The following table shows which packages are suppor ted in the Power BI service.

PA C K A GE VERSIO N L IN K

matplotlib 3.2.1 https://pypi.org/project/matplotlib

numpy 1.18.4 https://pypi.org/project/numpy

pandas 1.0.1 https://pypi.org/project/pandas

scikit-learn 0.23.0 https://pypi.org/project/scikit-learn

scipy 1.4.1 https://pypi.org/project/scipy

s eaborn 0.10.1 https://pypi.org/project/seaborn

 PA C K A GE VERSIO N L IN K

statsmodels 0.11.1 https://pypi.org/project/statsmodels

xgboost 1.1.0 https://pypi.org/project/xgboost

Next steps
For more information about Python in Power BI, take a look at the following articles:
Create Power BI visuals using Python
Running Python scripts in Power BI Desktop
Using Python in Query Editor
 Run R scripts in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

You can run R scripts directly in Power BI Desktop and import the resulting datasets into a Power BI Desktop data
model.

Install R
To run R scripts in Power BI Desktop, you need to install R on your local machine. You can download and install R
for free from many locations, including the Microsoft R Application Network and the CRAN Repository. The current
release supports Unicode characters and spaces (empty characters) in the installation path.

Run R scripts
Using just a few steps in Power BI Desktop, you can run R scripts and create a data model. With the data model,
you can create reports and share them on the Power BI service. R scripting in Power BI Desktop now supports
number formats that contain decimals (.) and commas (,).
Prepare an R script
To run an R script in Power BI Desktop, create the script in your local R development environment, and make sure it
runs successfully.
To run the script in Power BI Desktop, make sure the script runs successfully in a new and unmodified workspace.
This prerequisite means that all packages and dependencies must be explicitly loaded and run. You can use
source() to run dependent scripts.

When you prepare and run an R script in Power BI Desktop, there are a few limitations:
Because only data frames are imported, remember to represent the data you want to import to Power BI in a
data frame.
Columns typed as Complex and Vector aren't imported, and they're replaced with error values in the created
table.
Values that are N/A are translated to NULL values in Power BI Desktop.
If an R script runs longer than 30 minutes, it times out.
Interactive calls in the R script, such as waiting for user input, halts the script’s execution.
When setting the working directory within the R script, you must define a full path to the working directory,
rather than a relative path.
Run your R script and import data
Now you can run your R script to import data into Power BI Desktop:
1. In Power BI Desktop, select Get Data , choose Other > R script , and then select Connect :
2. If R is installed on your local machine, just copy your script into the script window and select OK . The latest
installed version is displayed as your R engine.

3. Select OK to run the R Script. When the script runs successfully, you can then choose the resulting data
frames to add to the Power BI model.
You can control which R installation to use to run your script. To specify your R installation settings, choose File >
Options and settings > Options , then select R scripting . Under R script options , the Detected R home
directories dropdown list shows your current R installation choices. If the R installation you want isn't listed, pick
Other , and then browse to or enter your preferred R installation folder in Set an R home director y .
Refresh
You can refresh an R script in Power BI Desktop. When you refresh an R script, Power BI Desktop runs the R script
again in the Power BI Desktop environment.

Next steps
Take a look at the following additional information about R in Power BI.
Create Power BI visuals using R
Use an external R IDE with Power BI
 Use R in Power Query Editor
9/9/2020 • 4 minutes to read • Edit Online

The R language is a powerful programming language that many statisticians, data scientists, and data analysts use.
You can use R in Power BI Desktop's Power Query Editor to:
Prepare data models.
Create reports.
Do data cleansing, advanced data shaping, and dataset analytics, which include missing data completion,
predictions, clustering, and more.

Install R
You can download R for free from the Revolution R Open download page and the CRAN Repository.

Install mice
As a prerequisite, you must install the mice library in your R environment. Without mice, the sample script code
won't work properly. The mice package implements a method to deal with missing data.
To install the mice library:
1. Launch the R.exe program (for example, C:\Program Files\Microsoft\R Open\R-3.5.3\bin\R.exe).
2. Run the install command from the R prompt:

install.packages('mice')

Use R in Power Query Editor

To demonstrate using R in Power Query Editor, we'll use an example stock market dataset contained in a .csv file
and work through the following steps:
1. Download the EuStockMarkets_NA.csv file. Remember where you save it.
2. Load the file into Power BI Desktop. From the Home tab, select Get Data > Text/CSV .
3. Select the EuStockMarkets_NA.csv file, and then choose Open . The CSV data is displayed in the Text/CSV
file dialog box.

4. Select Load to load the data from the file. After Power BI has loaded the data, the new table appears in the
Fields pane.
5. To open Power Query Editor, from the Home ribbon select Edit Queries .

6. From the Transform tab, select Run R script . The Run R script editor appears. Rows 15 and 20 have
missing data, as do other rows you can't see in the image. The following steps show how R completes those
rows for you.

7. For this example, enter the following script code in the Script box of the Run R script window. Replace
<Your File Path> with the path to EuStockMarkets_NA.csv on your local file system, for example,
C:/Users/John Doe/Documents/Microsoft/EuStockMarkets_NA.csv.
 dataset <- read.csv(file="<Your File Path>/EuStockMarkets_NA.csv", header=TRUE, sep=",")
library(mice)
tempData <- mice(dataset,m=1,maxit=50,meth='pmm',seed=100)
completedData <- complete(tempData,1)
output <- dataset
output$completedValues <- completedData$"SMI missing values"

NOTE
You might need to overwrite a variable named output to properly create the new dataset with the filters applied.

8. Select OK . Power Query Editor displays a warning about data privacy.

9. Inside the warning message, select Continue . In the Privacy levels dialog box that appears, set all data
sources to Public for the R scripts to work properly in the Power BI service.

For more information about privacy settings and their implications, see Power BI Desktop privacy levels.
10. Select Save to run the script.
Notice a new column in the Fields pane called completedValues . This column has a few missing data elements,
such as on row 15 and 18. Take a look at how R handles that in the next section.
With just five lines of R script, Power Query Editor filled in the missing values with a predictive model.

Create visuals from R script data

We can now create a visual to see how the R script code with the mice library completes the missing values.

You can save all completed visuals in one Power BI Desktop .pbix file and use the data model and its R scripts in the
Power BI service.

NOTE
You can download a .pbix file with all these steps completed.

After you've uploaded the .pbix file to the Power BI service, you need to take additional steps to enable service data
refresh and updated visuals:
Enable scheduled refresh for the dataset : To enable scheduled refresh for the workbook containing
your dataset with R scripts, see Configuring scheduled refresh. This article also includes information about
personal gateways.
Install a personal gateway : You need a personal gateway installed on the machine where the file and R
are located. The Power BI service accesses that workbook and re-renders any updated visuals. For more
information, see Use personal gateways in Power BI.

Limitations
There are some limitations to queries that include R scripts created in Power Query Editor:
All R data source settings must be set to Public . All other steps in a Power Query Editor query must also be
public.
To get to the data source settings, in Power BI Desktop, select File > Options and settings > Data source
settings .
 In the Data source settings dialog box, select one or more data sources, and then select Edit
Permissions . Set the Privacy Level to Public .

To schedule refresh of your R visuals or dataset, enable scheduled refresh and install a personal gateway on
the computer containing the workbook and R.
There are all sorts of things you can do with R and custom queries. Explore and shape your data just the way you
want it to appear.
Next Steps
Introduction to R
Run R scripts in Power BI Desktop
Use an external R IDE with Power BI
Create visuals by using R packages in the Power BI service
 Use an external R IDE with Power BI
9/9/2020 • 4 minutes to read • Edit Online

With Power BI Desktop , you can use your external R IDE (Integrated Development Environment) to create and
refine R scripts, then use those scripts in Power BI.

Enable an external R IDE

Previously, you had to use the R script editor in Power BI Desktop to create and run R scripts. With this release,
you can launch your external R IDE from Power BI Desktop and have your data automatically imported and
displayed in the R IDE. From there, you can modify the script in that external R IDE, then paste it back into Power
BI Desktop to create Power BI visuals and reports.
Beginning with the September 2016 release of Power BI Desktop (version 2.39.4526.362), you can specify which
R IDE you would like to use, and have it launch automatically from within Power BI Desktop .
Requirements
To use this feature, you need to install an R IDE on your local computer. Power BI Desktop does not include,
deploy, or install the R engine, so you must separately install R on your local computer. You can choose which R IDE
to use, with the following options:
You can install your favorite R IDE, many of which are available for free, such as the Revolution Open
download page, and the CRAN Repository.
Power BI Desktop also supports R Studio and Visual Studio 2015 with R Tools for Visual Studio editors.
 You can also install a different R IDE and have Power BI Desktop launch that R IDE by doing one of the
following:
You can associate .R files with the external IDE you want Power BI Desktop to launch.
You can specify the .exe that Power BI Desktop should launch by selecting Other from the R Script
Options section of the Options dialog. You can bring up the Options dialog by going to File >
Options and settings > Options .

If you have multiple R IDEs installed, you can specify which will be launched by selecting it from the Detected R
IDEs drop-down in the Options dialog.
By default, Power BI Desktop will launch R Studio as the external R IDE if it's installed on your local computer; if
R Studio is not installed and you have Visual Studio 2015 with R Tools for Visual Studio , that will be
launched instead. If neither of those R IDEs is installed, the application associated with .R files is launched.
And if no .R file association exists, it's possible to specify a path to a custom IDE in the Browse to your preferred R
IDE section of the Options dialog. You can also launch a different R IDE by selecting the Settings gear icon beside
the Launch R IDE arrow icon, in Power BI Desktop .

Launch an R IDE from Power BI Desktop

To launch an R IDE from Power BI Desktop , take the following steps:
1. Load data into Power BI Desktop .
2. Select some fields from the Fields pane that you want to work with. If you haven't enabled script visuals yet,
you'll be prompted to do so.
3. When script visuals are enabled, you can select an R visual from the Visualizations pane, which creates a
blank R visual that's ready to display the results of your script. The R script editor pane also appears.

4. Now you can select the fields you want to use in your R script. When you select a field, the R script editor
field automatically creates script code based on the field or fields you select. You can either create (or paste)
your R script directly in the R script editor pane, or you can leave it empty.
 NOTE
The default aggregation type for R visuals is do not summarize.

5. You can now launch your R IDE directly from Power BI Desktop . Select the Launch R IDE button, found
on the right side of the R script editor title bar, as shown below.

6. Your specified R IDE is launched by Power BI Desktop, as shown in the following image (in this image,
RStudio is the default R IDE).
 NOTE
Power BI Desktop adds the first three lines of the script so it can import your data from Power BI Desktop once
you run the script.

7. Any script you created in the R script editor pane of Power BI Desktop appears starting in line 4 in your
R IDE. At this point, you can create your R script in the R IDE. Once your R script is complete in your R IDE,
you need to copy and paste it back into the R script editor pane in Power BI Desktop , excluding the first
three lines of the script that Power BI Desktop automatically generated. Do not copy the first three lines of
script back into Power BI Desktop , those lines were only used to import your data to your R IDE from
Power BI Desktop .
Known limitations
Launching an R IDE directly from Power BI Desktop has a few limitations:
Automatically exporting your script from your R IDE into Power BI Desktop is not supported.
R Client editor (RGui.exe) is not supported, because the editor itself does not support opening files.

Next steps
Take a look at the following additional information about R in Power BI.
Running R Scripts in Power BI Desktop
Create Power BI visuals using R
 Create visuals by using R packages in the Power BI
service
9/9/2020 • 16 minutes to read • Edit Online

You can use the powerful R programming language to create visuals in the Power BI service. Many R packages are
supported in the Power BI service (and more are being supported all the time), and some packages are not.
The following sections provide an alphabetical table of which R packages are supported in Power BI, and which are
not. For more information about R in Power BI, see the R visuals article.

Request support for a new R package

Supported R packages for the Power BI ser vice are found in the following section, titled Suppor ted Packages .
If you would like to request support of an R package not found in that list, please submit your request to Power BI
Ideas.

Requirements and Limitations of R packages

There are a handful of requirements and limitations for R packages:
Current R runtime: Microsoft R 3.4.4
The Power BI service, for the most part, supports R packages with free and open-source software licenses
such as GPL-2, GPL-3, MIT+, and so on.
The Power BI service supports packages published in CRAN. The service does not support private or custom
R packages. Users are encouraged to make their private packages available on CRAN prior to requesting the
package be available in the Power BI service.
The Power BI Desktop has two variations for R packages:
For R visuals, you can install any package, including custom R packages
For Custom R visuals, only public CRAN packages are supported for auto-installation of the packages
For security and privacy reasons, R packages that provide client-server queries over the World-Wide Web
(such as RgoogleMaps) in the service, are not supported. Networking is blocked for such attempts. See the
following section for a list of supported and unsupported R packages.
The approval process for including a new R package has a tree of dependencies; some dependencies
required to be installed in the service cannot be supported.

R packages that are supported in Power BI

The following table shows which packages are suppor ted in the Power BI service.

PA C K A GE VERSIO N L IN K

abc 2.1 https://cran.r-

project.org/web/packages/abc/index.ht
ml
PA C K A GE VERSIO N L IN K

abc.data 1.0 https://cran.r-

project.org/web/packages/abc.data/inde
x.html

abind 1.4-5 https://cran.r-

project.org/web/packages/abind/index.h
tml

acepack 1.4.1 https://cran.r-

project.org/web/packages/acepack/inde
x.html

actuar 2.3-1 https://cran.r-

project.org/web/packages/actuar/index.
html

ade4 1.7-10 https://cran.r-

project.org/web/packages/ade4/index.ht
ml

AdMit 2.1.3 https://cran.r-

project.org/web/packages/AdMit/index.
html

AER 1.2-5 https://cran.r-

project.org/web/packages/AER/index.ht
ml

agricolae 1.3-1 https://cran.r-

project.org/web/packages/agricolae/ind
ex.html

AlgDesign 1.1-7.3 https://cran.r-

project.org/web/packages/AlgDesign/in
dex.html

alluvial 0.1-2 https://cran.r-

project.org/web/packages/alluvial/index.
html

andrews 1.0 https://cran.r-

project.org/web/packages/andrews/inde
x.html

anomalize 0.1.1 https://cran.r-

project.org/web/packages/anomalize/in
dex.html

anytime 0.3.3 https://cran.r-

project.org/web/packages/anytime/inde
x.html

aod 1.3 https://cran.r-

project.org/web/packages/aod/index.ht
ml
PA C K A GE VERSIO N L IN K

apcluster 1.4.5 https://cran.r-

project.org/web/packages/apcluster/ind
ex.html

ape 5.0 https://cran.r-

project.org/web/packages/ape/index.ht
ml

aplpack 1.3.0 https://cran.r-

project.org/web/packages/aplpack/index
.html

approximator 1.2-6 https://cran.r-

project.org/web/packages/approximator
/index.html

arm 1.9-3 https://cran.r-

project.org/web/packages/arm/index.ht
ml

arules 1.6-0 https://cran.r-

project.org/web/packages/arules/index.h
tml

arulesViz 1.3-0 https://cran.r-

project.org/web/packages/arulesViz/ind
ex.html

ash 1.0-15 https://cran.r-

project.org/web/packages/ash/index.ht
ml

assertthat 0.2.0 https://cran.r-

project.org/web/packages/assertthat/in
dex.html

autocogs 0.1.2 https://cran.r-

project.org/web/packages/autocogs/ind
ex.html

AzureML 0.2.14 https://cran.r-

project.org/web/packages/AzureML/ind
ex.html

BaBooN 0.2-0 https://cran.r-

project.org/web/packages/BaBooN/inde
x.html

BACCO 2.0-9 https://cran.r-

project.org/web/packages/BACCO/index
.html

backports 1.1.2 https://cran.r-

project.org/web/packages/backports/ind
ex.html
PA C K A GE VERSIO N L IN K

BaM 1.0.1 https://cran.r-

project.org/web/packages/BaM/index.ht
ml

BAS 1.4.9 https://cran.r-

project.org/web/packages/BAS/index.ht
ml

base 3.4.4 NA

base2grob 0.0.2 https://cran.r-

project.org/web/packages/base2grob/in
dex.html

base64 2.0 https://cran.r-

project.org/web/packages/base64/index.
html

base64enc 0.1-3 https://cran.r-

project.org/web/packages/base64enc/in
dex.html

BayesDA 2012.04-1 https://cran.r-

project.org/web/packages/BayesDA/ind
ex.html

BayesFactor 0.9.12-2 https://cran.r-

project.org/web/packages/BayesFactor/i
ndex.html

bayesGARCH 2.1.3 https://cran.r-

project.org/web/packages/bayesGARCH
/index.html

bayesm 3.1-0.1 https://cran.r-

project.org/web/packages/bayesm/index
.html

bayesmix 0.7-4 https://cran.r-

project.org/web/packages/bayesmix/ind
ex.html

bayesplot 1.5.0 https://cran.r-

project.org/web/packages/bayesplot/ind
ex.html

bayesQR 2.3 https://cran.r-

project.org/web/packages/bayesQR/ind
ex.html

bayesSurv 3.2 https://cran.r-

project.org/web/packages/bayesSurv/in
dex.html
PA C K A GE VERSIO N L IN K

Bayesthresh 2.0.1 https://cran.r-

project.org/web/packages/Bayesthresh/i
ndex.html

BayesTree 0.3-1.4 https://cran.r-

project.org/web/packages/BayesTree/ind
ex.html

BayesValidate 0.0 https://cran.r-

project.org/web/packages/BayesValidate
/index.html

BayesX 0.2-9 https://cran.r-

project.org/web/packages/BayesX/index.
html

BayHaz 0.1-3 https://cran.r-

project.org/web/packages/BayHaz/index
.html

bbemkr 2.0 https://cran.r-

project.org/web/packages/bbemkr/index
.html

BCBCSF 1.0-1 https://cran.r-

project.org/web/packages/BCBCSF/inde
x.html

BCE 2.1 https://cran.r-

project.org/web/packages/BCE/index.ht
ml

bclust 1.5 https://cran.r-

project.org/web/packages/bclust/index.h
tml

bcp 4.0.0 https://cran.r-

project.org/web/packages/bcp/index.ht
ml

BDgraph 2.45 https://cran.r-

project.org/web/packages/BDgraph/ind
ex.html

beanplot 1.2 https://cran.r-

project.org/web/packages/beanplot/ind
ex.html

beeswarm 0.2.3 https://cran.r-

project.org/web/packages/beeswarm/in
dex.html

benford.analysis 0.1.4.1 https://cran.r-

project.org/web/packages/benford.analy
sis/index.html
PA C K A GE VERSIO N L IN K

BenfordTests 1.2.0 https://cran.r-

project.org/web/packages/BenfordTests/
index.html

bfp 0.0-38 https://cran.r-

project.org/web/packages/bfp/index.ht
ml

BH 1.66.0-1 https://cran.r-
project.org/web/packages/BH/index.htm
l

biglm 0.9-1 https://cran.r-

project.org/web/packages/biglm/index.h
tml

bindr 0.1.1 https://cran.r-

project.org/web/packages/bindr/index.h
tml

bindrcpp 0.2.2 https://cran.r-

project.org/web/packages/bindrcpp/ind
ex.html

binom 1.1-1 https://cran.r-

project.org/web/packages/binom/index.
html

bisoreg 1.4 https://cran.r-

project.org/web/packages/bisoreg/index
.html

bit 1.1-12 https://cran.r-

project.org/web/packages/bit/index.html

bit64 0.9-7 https://cran.r-

project.org/web/packages/bit64/index.h
tml

bitops 1.0-6 https://cran.r-

project.org/web/packages/bitops/index.
html

bizdays 1.0.6 https://cran.r-

project.org/web/packages/bizdays/index
.html

blme 1.0-4 https://cran.r-

project.org/web/packages/blme/index.ht
ml

blob 1.1.1 https://cran.r-

project.org/web/packages/blob/index.ht
ml
PA C K A GE VERSIO N L IN K

BLR 1.4 https://cran.r-

project.org/web/packages/BLR/index.ht
ml

BMA 3.18.8 https://cran.r-

project.org/web/packages/BMA/index.ht
ml

Bmix 0.6 https://cran.r-

project.org/web/packages/Bmix/index.ht
ml

bmp 0.3 https://cran.r-

project.org/web/packages/bmp/index.ht
ml

BMS 0.3.4 https://cran.r-

project.org/web/packages/BMS/index.ht
ml

bnlearn 4.3 https://cran.r-

project.org/web/packages/bnlearn/index
.html

boa 1.1.8-2 https://cran.r-

project.org/web/packages/boa/index.ht
ml

bomrang 0.1.4 https://cran.r-

project.org/web/packages/bomrang/ind
ex.html

boot 1.3-20 https://cran.r-

project.org/web/packages/boot/index.ht
ml

bootstrap 2017.2 https://cran.r-

project.org/web/packages/bootstrap/ind
ex.html

Boruta 5.3.0 https://cran.r-

project.org/web/packages/Boruta/index.
html

bqtl 1.0-32 https://cran.r-

project.org/web/packages/bqtl/index.ht
ml

BradleyTerry2 1.0-8 https://cran.r-

project.org/web/packages/BradleyTerry2
/index.html

brew 1.0-6 https://cran.r-

project.org/web/packages/brew/index.ht
ml
PA C K A GE VERSIO N L IN K

brglm 0.6.1 https://cran.r-

project.org/web/packages/brglm/index.h
tml

broom 0.4.4 https://cran.r-

project.org/web/packages/broom/index.
html

bspec 1.5 https://cran.r-

project.org/web/packages/bspec/index.h
tml

bspmma 0.1-1 https://cran.r-

project.org/web/packages/bspmma/inde
x.html

bupaR 0.4.0 https://cran.r-

project.org/web/packages/bupaR/index.
html

BVS 4.12.1 https://cran.r-

project.org/web/packages/BVS/index.ht
ml

C50 0.1.1 https://cran.r-

project.org/web/packages/C50/index.ht
ml

Cairo 1.5-9 https://cran.r-

project.org/web/packages/Cairo/index.h
tml

cairoDevice 2.24 https://cran.r-

project.org/web/packages/cairoDevice/i
ndex.html

calibrate 1.7.2 https://cran.r-

project.org/web/packages/calibrate/inde
x.html

calibrator 1.2-6 https://cran.r-

project.org/web/packages/calibrator/ind
ex.html

callr 2.0.2 https://cran.r-

project.org/web/packages/callr/index.ht
ml

car 2.1-6 https://cran.r-

project.org/web/packages/car/index.htm
l

carData 3.0-1 https://cran.r-

project.org/web/packages/carData/index
.html
PA C K A GE VERSIO N L IN K

caret 6.0-78 https://cran.r-

project.org/web/packages/caret/index.ht
ml

catnet 1.15.3 https://cran.r-

project.org/web/packages/catnet/index.
html

caTools 1.17.1 https://cran.r-

project.org/web/packages/caTools/index.
html

cclust 0.6-21 https://cran.r-

project.org/web/packages/cclust/index.h
tml

cellranger 1.1.0 https://cran.r-

project.org/web/packages/cellranger/ind
ex.html

ChainLadder 0.2.5 https://cran.r-

project.org/web/packages/ChainLadder/
index.html

checkmate 1.8.5 https://cran.r-

project.org/web/packages/checkmate/in
dex.html

checkpoint 0.4.3 https://cran.r-

project.org/web/packages/checkpoint/in
dex.html

choroplethrMaps 1.0.1 https://cran.r-

project.org/web/packages/choroplethrM
aps/index.html

chron 2.3-52 https://cran.r-

project.org/web/packages/chron/index.h
tml

circlize 0.4.3 https://cran.r-

project.org/web/packages/circlize/index.
html

Ckmeans.1d.dp 4.2.1 https://cran.r-

project.org/web/packages/Ckmeans.1d.
dp/index.html

class 7.3-14 https://cran.r-

project.org/web/packages/class/index.ht
ml

classInt 0.1-24 https://cran.r-

project.org/web/packages/classInt/index
.html
PA C K A GE VERSIO N L IN K

cli 1.0.0 https://cran.r-

project.org/web/packages/cli/index.html

ClickClust 1.1.5 https://cran.r-

project.org/web/packages/ClickClust/ind
ex.html

clickstream 1.3.0 https://cran.r-

project.org/web/packages/clickstream/in
dex.html

clue 0.3-54 https://cran.r-

project.org/web/packages/clue/index.ht
ml

cluster 2.0.6 https://cran.r-

project.org/web/packages/cluster/index.
html

clv 0.3-2.1 https://cran.r-

project.org/web/packages/clv/index.html

cmprsk 2.2-7 https://cran.r-

project.org/web/packages/cmprsk/index.
html

coda 0.19-1 https://cran.r-

project.org/web/packages/coda/index.ht
ml

codetools 0.2-15 https://cran.r-

project.org/web/packages/codetools/ind
ex.html

coefplot 1.2.6 https://cran.r-

project.org/web/packages/coefplot/inde
x.html

coin 1.2-2 https://cran.r-

project.org/web/packages/coin/index.ht
ml

collapsibleTree 0.1.6 https://cran.r-

project.org/web/packages/collapsibleTre
e/index.html

colorRamps 2.3 https://cran.r-

project.org/web/packages/colorRamps/i
ndex.html

colorspace 1.3-2 https://cran.r-

project.org/web/packages/colorspace/in
dex.html
PA C K A GE VERSIO N L IN K

combinat 0.0-8 https://cran.r-

project.org/web/packages/combinat/ind
ex.html

commonmark 1.4 https://cran.r-

project.org/web/packages/commonmar
k/index.html

compiler 3.4.4 NA

compositions 1.40-1 https://cran.r-

project.org/web/packages/compositions
/index.html

CORElearn 1.52.0 https://cran.r-

project.org/web/packages/CORElearn/in
dex.html

corpcor 1.6.9 https://cran.r-

project.org/web/packages/corpcor/index
.html

corrgram 1.12 https://cran.r-

project.org/web/packages/corrgram/ind
ex.html

corrplot 0.84 https://cran.r-

project.org/web/packages/corrplot/inde
x.html

covr 3.0.1 https://cran.r-

project.org/web/packages/covr/index.ht
ml

cowplot 0.9.2 https://cran.r-

project.org/web/packages/cowplot/inde
x.html

cplm 0.7-5 https://cran.r-

project.org/web/packages/cplm/index.ht
ml

crayon 1.3.4 https://cran.r-

project.org/web/packages/crayon/index.
html

crosstalk 1.0.0 https://cran.r-

project.org/web/packages/crosstalk/inde
x.html

cslogistic 0.1-3 https://cran.r-

project.org/web/packages/cslogistic/ind
ex.html
PA C K A GE VERSIO N L IN K

cts 1.0-21 https://cran.r-

project.org/web/packages/cts/index.htm
l

ctv 0.8-4 https://cran.r-

project.org/web/packages/ctv/index.htm
l

cubature 1.3-11 https://cran.r-

project.org/web/packages/cubature/ind
ex.html

Cubist 0.2.1 https://cran.r-

project.org/web/packages/Cubist/index.
html

curl 3.2 https://cran.r-

project.org/web/packages/curl/index.ht
ml

CVST 0.2-1 https://cran.r-

project.org/web/packages/CVST/index.h
tml

cvTools 0.3.2 https://cran.r-

project.org/web/packages/cvTools/index.
html

d3heatmap 0.6.1.2 https://cran.r-

project.org/web/packages/d3heatmap/i
ndex.html

d3Network 0.5.2.1 https://cran.r-

project.org/web/packages/d3Network/in
dex.html

d3r 0.8.0 https://cran.r-

project.org/web/packages/d3r/index.ht
ml

data.table 1.10.4-3 https://cran.r-

project.org/web/packages/data.table/ind
ex.html

data.tree 0.7.5 https://cran.r-

project.org/web/packages/data.tree/ind
ex.html

datasets 3.4.4 NA

date 1.2-38 https://cran.r-

project.org/web/packages/date/index.ht
ml
PA C K A GE VERSIO N L IN K

DBI 0.8 https://cran.r-

project.org/web/packages/DBI/index.ht
ml

dbplyr 1.2.1 https://cran.r-

project.org/web/packages/dbplyr/index.
html

dbscan 1.1-1 https://cran.r-

project.org/web/packages/dbscan/index.
html

dclone 2.2-0 https://cran.r-

project.org/web/packages/dclone/index.
html

ddalpha 1.3.1.1 https://cran.r-

project.org/web/packages/ddalpha/inde
x.html

deal 1.2-37 https://cran.r-

project.org/web/packages/deal/index.ht
ml

debugme 1.1.0 https://cran.r-

project.org/web/packages/debugme/ind
ex.html

deepnet 0.2 https://cran.r-

project.org/web/packages/deepnet/inde
x.html

deldir 0.1-14 https://cran.r-

project.org/web/packages/deldir/index.h
tml

dendextend 1.12.0 https://cran.r-

project.org/web/packages/dendextend/i
ndex.html

DEoptimR 1.0-8 https://cran.r-

project.org/web/packages/DEoptimR/in
dex.html

deployrRserve 9.0.0 NA

Deriv 3.8.4 https://cran.r-

project.org/web/packages/Deriv/index.h
tml

desc 1.1.1 https://cran.r-

project.org/web/packages/desc/index.ht
ml
PA C K A GE VERSIO N L IN K

descr 1.1.4 https://cran.r-

project.org/web/packages/descr/index.h
tml

deSolve 1.20 https://cran.r-

project.org/web/packages/deSolve/index
.html

devtools 1.13.5 https://cran.r-

project.org/web/packages/devtools/inde
x.html

DiagrammeR 1.0.0 https://cran.r-

project.org/web/packages/DiagrammeR/
index.html

DiagrammeRsvg 0.1 https://cran.r-

project.org/web/packages/DiagrammeR
svg/index.html

dichromat 2.0-0 https://cran.r-

project.org/web/packages/dichromat/in
dex.html

digest 0.6.15 https://cran.r-

project.org/web/packages/digest/index.
html

dimRed 0.1.0 https://cran.r-

project.org/web/packages/dimRed/index
.html

diptest 0.75-7 https://cran.r-

project.org/web/packages/diptest/index.
html

DistributionUtils 0.6-0 https://cran.r-

project.org/web/packages/DistributionU
tils/index.html

distrom 1.0 https://cran.r-

project.org/web/packages/distrom/index
.html

dlm 1.1-4 https://cran.r-

project.org/web/packages/dlm/index.ht
ml

DMwR 0.4.1 https://cran.r-

project.org/web/packages/DMwR/index.
html

doBy 4.6-1 https://cran.r-

project.org/web/packages/doBy/index.ht
ml
PA C K A GE VERSIO N L IN K

doParallel 1.0.12 https://cran.r-

project.org/web/packages/doParallel/ind
ex.html

doSNOW 1.0.16 https://cran.r-

project.org/web/packages/doSNOW/ind
ex.html

dotCall64 0.9-5.2 https://cran.r-

project.org/web/packages/dotCall64/ind
ex.html

downloader 0.4 https://cran.r-

project.org/web/packages/downloader/i
ndex.html

dplyr 0.8.0.1 https://cran.r-

project.org/web/packages/dplyr/index.ht
ml

DPpackage 1.1-7.4 https://cran.r-

project.org/web/packages/DPpackage/in
dex.html

DRR 0.0.3 https://cran.r-

project.org/web/packages/DRR/index.ht
ml

dse 2015.12-1 https://cran.r-

project.org/web/packages/dse/index.ht
ml

DT 0.4 https://cran.r-
project.org/web/packages/DT/index.html

dtt 0.1-2 https://cran.r-

project.org/web/packages/dtt/index.htm
l

dtw 1.18-1 https://cran.r-

project.org/web/packages/dtw/index.ht
ml

dygraphs 1.1.1.4 https://cran.r-

project.org/web/packages/dygraphs/ind
ex.html

dynlm 0.3-5 https://cran.r-

project.org/web/packages/dynlm/index.
html

e1071 1.6-8 https://cran.r-

project.org/web/packages/e1071/index.
html
PA C K A GE VERSIO N L IN K

earth 4.6.2 https://cran.r-

project.org/web/packages/earth/index.h
tml

EbayesThresh 1.4-12 https://cran.r-

project.org/web/packages/EbayesThresh
/index.html

ebdbNet 1.2.5 https://cran.r-

project.org/web/packages/ebdbNet/inde
x.html

ecm 4.4.0 https://cran.r-

project.org/web/packages/ecm/index.ht
ml

edeaR 0.8.0 https://cran.r-

project.org/web/packages/edeaR/index.
html

effects 4.0-1 https://cran.r-

project.org/web/packages/effects/index.
html

ellipse 0.4.1 https://cran.r-

project.org/web/packages/ellipse/index.
html

ellipsis 0.1.0 https://cran.r-

project.org/web/packages/ellipsis/index.
html

emmeans 1.1.2 https://cran.r-

project.org/web/packages/emmeans/ind
ex.html

emulator 1.2-15 https://cran.r-

project.org/web/packages/emulator/ind
ex.html

energy 1.7-2 https://cran.r-

project.org/web/packages/energy/index.
html

english 1.2-3 https://cran.r-

project.org/web/packages/english/index.
html

ensembleBMA 5.1.5 https://cran.r-

project.org/web/packages/ensembleBM
A/index.html

entropy 1.2.1 https://cran.r-

project.org/web/packages/entropy/inde
x.html
PA C K A GE VERSIO N L IN K

estimability 1.3 https://cran.r-

project.org/web/packages/estimability/i
ndex.html

eulerr 5.1.0 https://cran.r-

project.org/web/packages/eulerr/index.h
tml

EvalEst 2015.4-2 https://cran.r-

project.org/web/packages/EvalEst/index.
html

evaluate 0.10.1 https://cran.r-

project.org/web/packages/evaluate/inde
x.html

evd 2.3-2 https://cran.r-

project.org/web/packages/evd/index.ht
ml

evdbayes 1.1-1 https://cran.r-

project.org/web/packages/evdbayes/ind
ex.html

eventdataR 0.2.0 https://cran.r-

project.org/web/packages/eventdataR/i
ndex.html

exactLoglinTest 1.4.2 https://cran.r-

project.org/web/packages/exactLoglinTe
st/index.html

exactRankTests 0.8-29 https://cran.r-

project.org/web/packages/exactRankTest
s/index.html

expint 0.1-4 https://cran.r-

project.org/web/packages/expint/index.
html

expm 0.999-2 https://cran.r-

project.org/web/packages/expm/index.h
tml

extraDistr 1.8.8 https://cran.r-

project.org/web/packages/extraDistr/ind
ex.html

extrafont 0.17 https://cran.r-

project.org/web/packages/extrafont/ind
ex.html

extrafontdb 1.0 https://cran.r-

project.org/web/packages/extrafontdb/i
ndex.html
PA C K A GE VERSIO N L IN K

extremevalues 2.3.2 https://cran.r-

project.org/web/packages/extremevalue
s/index.html

ez 4.4-0 https://cran.r-
project.org/web/packages/ez/index.html

factoextra 1.0.5 https://cran.r-

project.org/web/packages/factoextra/ind
ex.html

FactoMineR 1.40 https://cran.r-

project.org/web/packages/FactoMineR/i
ndex.html

factorQR 0.1-4 https://cran.r-

project.org/web/packages/factorQR/ind
ex.html

fansi 0.4.0 https://cran.r-

project.org/web/packages/fansi/index.ht
ml

faoutlier 0.7.2 https://cran.r-

project.org/web/packages/faoutlier/inde
x.html

farver 1.1.0 https://cran.r-

project.org/web/packages/farver/index.h
tml

fastICA 1.2-1 https://cran.r-

project.org/web/packages/fastICA/index.
html

fastmatch 1.1-0 https://cran.r-

project.org/web/packages/fastmatch/ind
ex.html

fBasics 3042.89 https://cran.r-

project.org/web/packages/fBasics/index.
html

fdrtool 1.2.15 https://cran.r-

project.org/web/packages/fdrtool/index.
html

fGarch 3042.83.1 https://cran.r-

project.org/web/packages/fGarch/index.
html

fields 9.6 https://cran.r-

project.org/web/packages/fields/index.ht
ml
PA C K A GE VERSIO N L IN K

filehash 2.4-1 https://cran.r-

project.org/web/packages/filehash/index
.html

FinCal 0.6.3 https://cran.r-

project.org/web/packages/FinCal/index.
html

fitdistrplus 1.0-9 https://cran.r-

project.org/web/packages/fitdistrplus/in
dex.html

flashClust 1.01-2 https://cran.r-

project.org/web/packages/flashClust/ind
ex.html

flexclust 1.3-5 https://cran.r-

project.org/web/packages/flexclust/inde
x.html

flexmix 2.3-14 https://cran.r-

project.org/web/packages/flexmix/index.
html

FME 1.3.5 https://cran.r-

project.org/web/packages/FME/index.ht
ml

fmsb 0.6.1 https://cran.r-

project.org/web/packages/fmsb/index.ht
ml

FNN 1.1 https://cran.r-

project.org/web/packages/FNN/index.ht
ml

fontBitstreamVera 0.1.1 https://cran.r-

project.org/web/packages/fontBitstream
Vera/index.html

fontLiberation 0.1.0 https://cran.r-

project.org/web/packages/fontLiberatio
n/index.html

fontquiver 0.2.1 https://cran.r-

project.org/web/packages/fontquiver/in
dex.html

forcats 0.3.0 https://cran.r-

project.org/web/packages/forcats/index.
html

foreach 1.4.4 https://cran.r-

project.org/web/packages/foreach/index
.html
PA C K A GE VERSIO N L IN K

forecast 8.7 https://cran.r-

project.org/web/packages/forecast/inde
x.html

forecastHybrid 2.1.11 https://cran.r-

project.org/web/packages/forecastHybri
d/index.html

foreign 0.8-69 https://cran.r-

project.org/web/packages/foreign/index.
html

formatR 1.5 https://cran.r-

project.org/web/packages/formatR/inde
x.html

formattable 0.2.0.1 https://cran.r-

project.org/web/packages/formattable/i
ndex.html

Formula 1.2-2 https://cran.r-

project.org/web/packages/Formula/inde
x.html

fpc 2.1-11 https://cran.r-

project.org/web/packages/fpc/index.htm
l

fracdiff 1.4-2 https://cran.r-

project.org/web/packages/fracdiff/index.
html

fTrading 3042.79 https://cran.r-

project.org/web/packages/fTrading/inde
x.html

fUnitRoots 3042.79 https://cran.r-

project.org/web/packages/fUnitRoots/in
dex.html

futile.logger 1.4.3 https://cran.r-

project.org/web/packages/futile.logger/i
ndex.html

futile.options 1.0.0 https://cran.r-

project.org/web/packages/futile.options/
index.html

gam 1.15 https://cran.r-

project.org/web/packages/gam/index.ht
ml

gamlr 1.13-4 https://cran.r-

project.org/web/packages/gamlr/index.h
tml
PA C K A GE VERSIO N L IN K

gamlss 5.0-6 https://cran.r-

project.org/web/packages/gamlss/index.
html

gamlss.data 5.0-0 https://cran.r-

project.org/web/packages/gamlss.data/i
ndex.html

gamlss.dist 5.0-4 https://cran.r-

project.org/web/packages/gamlss.dist/in
dex.html

gbm 2.1.3 https://cran.r-

project.org/web/packages/gbm/index.ht
ml

gclus 1.3.1 https://cran.r-

project.org/web/packages/gclus/index.ht
ml

gdalUtils 2.0.1.7 https://cran.r-

project.org/web/packages/gdalUtils/inde
x.html

gdata 2.18.0 https://cran.r-

project.org/web/packages/gdata/index.h
tml

gdtools 0.1.7 https://cran.r-

project.org/web/packages/gdtools/index
.html

gee 4.13-19 https://cran.r-

project.org/web/packages/gee/index.ht
ml

genalg 0.2.0 https://cran.r-

project.org/web/packages/genalg/index.
html

genetics 1.3.8.1 https://cran.r-

project.org/web/packages/genetics/inde
x.html

GenSA 1.1.7 https://cran.r-

project.org/web/packages/GenSA/index.
html

geojson 0.2.0 https://cran.r-

project.org/web/packages/geojson/inde
x.html

geojsonio 0.6.0 https://cran.r-

project.org/web/packages/geojsonio/ind
ex.html
PA C K A GE VERSIO N L IN K

geojsonlint 0.2.0 https://cran.r-

project.org/web/packages/geojsonlint/in
dex.html

geoR 1.7-5.2 https://cran.r-

project.org/web/packages/geoR/index.ht
ml

geoRglm 0.9-11 https://cran.r-

project.org/web/packages/geoRglm/inde
x.html

geosphere 1.5-7 https://cran.r-

project.org/web/packages/geosphere/in
dex.html

GGally 1.3.2 https://cran.r-

project.org/web/packages/GGally/index.
html

ggalt 0.4.0 https://cran.r-

project.org/web/packages/ggalt/index.ht
ml

gganimate 1.0.3 https://cran.r-

project.org/web/packages/gganimate/in
dex.html

ggcorrplot 0.1.1 https://cran.r-

project.org/web/packages/ggcorrplot/in
dex.html

ggdendro 0.1-20 https://cran.r-

project.org/web/packages/ggdendro/ind
ex.html

ggeffects 0.3.2 https://cran.r-

project.org/web/packages/ggeffects/ind
ex.html

ggforce 0.1.1 https://cran.r-

project.org/web/packages/ggforce/index
.html

ggformula 0.6.2 https://cran.r-

project.org/web/packages/ggformula/in
dex.html

ggfortify 0.4.3 https://cran.r-

project.org/web/packages/ggfortify/inde
x.html

ggimage 0.1.2 https://cran.r-

project.org/web/packages/ggimage/inde
x.html
PA C K A GE VERSIO N L IN K

ggjoy 0.4.0 https://cran.r-

project.org/web/packages/ggjoy/index.h
tml

ggm 2.3 https://cran.r-

project.org/web/packages/ggm/index.ht
ml

ggmap 2.6.1 https://cran.r-

project.org/web/packages/ggmap/index.
html

ggmcmc 1.1 https://cran.r-

project.org/web/packages/ggmcmc/inde
x.html

ggplot2 3.2.0 https://cran.r-

project.org/web/packages/ggplot2/inde
x.html

ggplot2movies 0.0.1 https://cran.r-

project.org/web/packages/ggplot2movi
es/index.html

ggpmisc 0.2.16 https://cran.r-

project.org/web/packages/ggpmisc/inde
x.html

ggpubr 0.1.6 https://cran.r-

project.org/web/packages/ggpubr/index
.html

ggQC 0.0.31 https://cran.r-

project.org/web/packages/ggQC/index.h
tml

ggraph 1.0.1 https://cran.r-

project.org/web/packages/ggraph/index.
html

ggrepel 0.7.0 https://cran.r-

project.org/web/packages/ggrepel/index
.html

ggridges 0.4.1 https://cran.r-

project.org/web/packages/ggridges/inde
x.html

ggsci 2.8 https://cran.r-

project.org/web/packages/ggsci/index.ht
ml

ggsignif 0.4.0 https://cran.r-

project.org/web/packages/ggsignif/inde
x.html
PA C K A GE VERSIO N L IN K

ggsoccer 0.1.4 https://cran.r-

project.org/web/packages/ggsoccer/ind
ex.html

ggstance 0.3 https://cran.r-

project.org/web/packages/ggstance/ind
ex.html

ggtern 2.2.1 https://cran.r-

project.org/web/packages/ggtern/index.
html

ggthemes 3.4.0 https://cran.r-

project.org/web/packages/ggthemes/in
dex.html

gistr 0.4.0 https://cran.r-

project.org/web/packages/gistr/index.ht
ml

git2r 0.21.0 https://cran.r-

project.org/web/packages/git2r/index.ht
ml

glasso 1.8 https://cran.r-

project.org/web/packages/glasso/index.
html

glmmBUGS 2.4.0 https://cran.r-

project.org/web/packages/glmmBUGS/i
ndex.html

glmmTMB 0.2.0 https://cran.r-

project.org/web/packages/glmmTMB/in
dex.html

glmnet 2.0-13 https://cran.r-

project.org/web/packages/glmnet/index.
html

GlobalOptions 0.0.13 https://cran.r-

project.org/web/packages/GlobalOption
s/index.html

glue 1.3.1 https://cran.r-

project.org/web/packages/glue/index.ht
ml

gmodels 2.16.2 https://cran.r-

project.org/web/packages/gmodels/inde
x.html

gmp 0.5-13.1 https://cran.r-

project.org/web/packages/gmp/index.ht
ml
PA C K A GE VERSIO N L IN K

gnm 1.0-8 https://cran.r-

project.org/web/packages/gnm/index.ht
ml

goftest 1.1-1 https://cran.r-

project.org/web/packages/goftest/index.
html

googleVis 0.6.2 https://cran.r-

project.org/web/packages/googleVis/ind
ex.html

gower 0.1.2 https://cran.r-

project.org/web/packages/gower/index.
html

GPArotation 2014.11-1 https://cran.r-

project.org/web/packages/GPArotation/i
ndex.html

gplots 3.0.1 https://cran.r-

project.org/web/packages/gplots/index.
html

graphics 3.4.4 NA

grDevices 3.4.4 NA

grid 3.4.4 NA

gridBase 0.4-7 https://cran.r-

project.org/web/packages/gridBase/inde
x.html

gridExtra 2.3 https://cran.r-

project.org/web/packages/gridExtra/ind
ex.html

gridGraphics 0.2-1 https://cran.r-

project.org/web/packages/gridGraphics/
index.html

growcurves 0.2.4.1 https://cran.r-

project.org/web/packages/growcurves/i
ndex.html

grpreg 3.1-2 https://cran.r-

project.org/web/packages/grpreg/index.
html

gss 2.1-7 https://cran.r-

project.org/web/packages/gss/index.ht
ml
PA C K A GE VERSIO N L IN K

gstat 1.1-5 https://cran.r-

project.org/web/packages/gstat/index.ht
ml

gsubfn 0.7 https://cran.r-

project.org/web/packages/gsubfn/index.
html

gtable 0.2.0 https://cran.r-

project.org/web/packages/gtable/index.
html

gtools 3.5.0 https://cran.r-

project.org/web/packages/gtools/index.
html

gtrendsR 1.4.3 https://cran.r-

project.org/web/packages/gtrendsR/ind
ex.html

gWidgets 0.0-54 https://cran.r-

project.org/web/packages/gWidgets/ind
ex.html

gWidgetsRGtk2 0.0-86 https://cran.r-

project.org/web/packages/gWidgetsRGt
k2/index.html

gWidgetstcltk 0.0-55 https://cran.r-

project.org/web/packages/gWidgetstcltk
/index.html

haplo.stats 1.7.7 https://cran.r-

project.org/web/packages/haplo.stats/in
dex.html

hash 2.2.6 https://cran.r-

project.org/web/packages/hash/index.ht
ml

haven 1.1.1 https://cran.r-

project.org/web/packages/haven/index.
html

hbsae 1.0 https://cran.r-

project.org/web/packages/hbsae/index.h
tml

HDInterval 0.2.0 https://cran.r-

project.org/web/packages/HDInterval/in
dex.html

hdrcde 3.2 https://cran.r-

project.org/web/packages/hdrcde/index.
html
PA C K A GE VERSIO N L IN K

heatmaply 0.16.0 https://cran.r-

project.org/web/packages/heatmaply/in
dex.html

heavy 0.38.19 https://cran.r-

project.org/web/packages/heavy/index.h
tml

hexbin 1.27.2 https://cran.r-

project.org/web/packages/hexbin/index.
html

hflights 0.1 https://cran.r-

project.org/web/packages/hflights/index
.html

HH 3.1-34 https://cran.r-
project.org/web/packages/HH/index.ht
ml

HI 0.4 https://cran.r-
project.org/web/packages/HI/index.html

highcharter 0.5.0 https://cran.r-

project.org/web/packages/highcharter/i
ndex.html

highr 0.6 https://cran.r-

project.org/web/packages/highr/index.h
tml

HistData 0.8-2 https://cran.r-

project.org/web/packages/HistData/inde
x.html

Hmisc 4.1-1 https://cran.r-

project.org/web/packages/Hmisc/index.
html

hms 0.4.2 https://cran.r-

project.org/web/packages/hms/index.ht
ml

hoardr 0.2.0 https://cran.r-

project.org/web/packages/hoardr/index.
html

HSAUR 1.3-9 https://cran.r-

project.org/web/packages/HSAUR/index.
html

htmlTable 1.11.2 https://cran.r-

project.org/web/packages/htmlTable/ind
ex.html
PA C K A GE VERSIO N L IN K

htmltools 0.3.6 https://cran.r-

project.org/web/packages/htmltools/ind
ex.html

htmlwidgets 1.3 https://cran.r-

project.org/web/packages/htmlwidgets/i
ndex.html

hts 5.1.5 https://cran.r-

project.org/web/packages/hts/index.htm
l

httpuv 1.3.6.2 https://cran.r-

project.org/web/packages/httpuv/index.
html

httr 1.3.1 https://cran.r-

project.org/web/packages/httr/index.ht
ml

huge 1.2.7 https://cran.r-

project.org/web/packages/huge/index.ht
ml

hunspell 2.9 https://cran.r-

project.org/web/packages/hunspell/inde
x.html

IBrokers 0.9-12 https://cran.r-

project.org/web/packages/IBrokers/inde
x.html

ifultools 2.0-4 https://cran.r-

project.org/web/packages/ifultools/inde
x.html

igraph 1.2.1 https://cran.r-

project.org/web/packages/igraph/index.
html

imager 0.40.2 https://cran.r-

project.org/web/packages/imager/index.
html

influenceR 0.1.0 https://cran.r-

project.org/web/packages/influenceR/in
dex.html

inline 0.3.14 https://cran.r-

project.org/web/packages/inline/index.h
tml

intervals 0.15.1 https://cran.r-

project.org/web/packages/intervals/inde
x.html
PA C K A GE VERSIO N L IN K

inum 1.0-0 https://cran.r-

project.org/web/packages/inum/index.ht
ml

ipred 0.9-6 https://cran.r-

project.org/web/packages/ipred/index.ht
ml

irlba 2.3.2 https://cran.r-

project.org/web/packages/irlba/index.ht
ml

irr 0.84 https://cran.r-

project.org/web/packages/irr/index.html

ISOcodes 2017.09.27 https://cran.r-

project.org/web/packages/ISOcodes/ind
ex.html

iterators 1.0.9 https://cran.r-

project.org/web/packages/iterators/inde
x.html

janeaustenr 0.1.5 https://cran.r-

project.org/web/packages/janeaustenr/i
ndex.html

janitor 1.0.0 https://cran.r-

project.org/web/packages/janitor/index.
html

jpeg 0.1-8 https://cran.r-

project.org/web/packages/jpeg/index.ht
ml

jqr 1.0.0 https://cran.r-

project.org/web/packages/jqr/index.html

jsonlite 1.5 https://cran.r-

project.org/web/packages/jsonlite/index.
html

jsonvalidate 1.0.0 https://cran.r-

project.org/web/packages/jsonvalidate/i
ndex.html

jtools 0.9.4 https://cran.r-

project.org/web/packages/jtools/index.h
tml

kableExtra 0.7.0 https://cran.r-

project.org/web/packages/kableExtra/in
dex.html
PA C K A GE VERSIO N L IN K

Kendall 2.2 https://cran.r-

project.org/web/packages/Kendall/index.
html

kernlab 0.9-25 https://cran.r-

project.org/web/packages/kernlab/index
.html

KernSmooth 2.23-15 https://cran.r-

project.org/web/packages/KernSmooth/i
ndex.html

KFKSDS 1.6 https://cran.r-

project.org/web/packages/KFKSDS/index
.html

kinship2 1.6.4 https://cran.r-

project.org/web/packages/kinship2/inde
x.html

kknn 1.3.1 https://cran.r-

project.org/web/packages/kknn/index.ht
ml

klaR 0.6-14 https://cran.r-

project.org/web/packages/klaR/index.ht
ml

km.ci 0.5-2 https://cran.r-

project.org/web/packages/km.ci/index.ht
ml

KMsurv 0.1-5 https://cran.r-

project.org/web/packages/KMsurv/index
.html

knitr 1.20 https://cran.r-

project.org/web/packages/knitr/index.ht
ml

ks 1.11.0 https://cran.r-
project.org/web/packages/ks/index.html

labeling 0.3 https://cran.r-

project.org/web/packages/labeling/index
.html

labelled 1.0.1 https://cran.r-

project.org/web/packages/labelled/index
.html

laeken 0.4.6 https://cran.r-

project.org/web/packages/laeken/index.
html
PA C K A GE VERSIO N L IN K

Lahman 6.0-0 https://cran.r-

project.org/web/packages/Lahman/inde
x.html

lambda.r 1.2 https://cran.r-

project.org/web/packages/lambda.r/inde
x.html

lars 1.2 https://cran.r-

project.org/web/packages/lars/index.ht
ml

latex2exp 0.4.0 https://cran.r-

project.org/web/packages/latex2exp/ind
ex.html

lattice 0.20-35 https://cran.r-

project.org/web/packages/lattice/index.h
tml

latticeExtra 0.6-28 https://cran.r-

project.org/web/packages/latticeExtra/in
dex.html

lava 1.6.1 https://cran.r-

project.org/web/packages/lava/index.ht
ml

lavaan 0.5-23.1097 https://cran.r-

project.org/web/packages/lavaan/index.
html

lazyeval 0.2.1 https://cran.r-

project.org/web/packages/lazyeval/index
.html

lda 1.4.2 https://cran.r-

project.org/web/packages/lda/index.htm
l

leaflet 2.0.2 https://cran.r-

project.org/web/packages/leaflet/index.h
tml

leaflet.esri 0.2 https://cran.r-

project.org/web/packages/leaflet.esri/ind
ex.html

leaflet.extras 0.2 https://cran.r-

project.org/web/packages/leaflet.extras/i
ndex.html

leaps 3.0 https://cran.r-

project.org/web/packages/leaps/index.ht
ml
PA C K A GE VERSIO N L IN K

LearnBayes 2.15.1 https://cran.r-

project.org/web/packages/LearnBayes/i
ndex.html

lexicon 1.2.1 https://cran.r-

project.org/web/packages/lexicon/index.
html

libcoin 1.0-1 https://cran.r-

project.org/web/packages/libcoin/index.
html

LiblineaR 2.10-8 https://cran.r-

project.org/web/packages/LiblineaR/ind
ex.html

LICORS 0.2.0 https://cran.r-

project.org/web/packages/LICORS/index
.html

likert 1.3.5 https://cran.r-

project.org/web/packages/likert/index.ht
ml

limSolve 1.5.5.3 https://cran.r-

project.org/web/packages/limSolve/inde
x.html

linprog 0.9-2 https://cran.r-

project.org/web/packages/linprog/index.
html

lm.beta 1.5-1 https://cran.r-

project.org/web/packages/lm.beta/index
.html

lme4 1.1-16 https://cran.r-

project.org/web/packages/lme4/index.ht
ml

lmm 1.0 https://cran.r-

project.org/web/packages/lmm/index.ht
ml

lmtest 0.9-35 https://cran.r-

project.org/web/packages/lmtest/index.
html

locfit 1.5-9.1 https://cran.r-

project.org/web/packages/locfit/index.ht
ml

locpol 0.6-0 https://cran.r-

project.org/web/packages/locpol/index.h
tml
PA C K A GE VERSIO N L IN K

LogicReg 1.5.9 https://cran.r-

project.org/web/packages/LogicReg/ind
ex.html

lpSolve 5.6.13 https://cran.r-

project.org/web/packages/lpSolve/index.
html

lsa 0.73.1 https://cran.r-

project.org/web/packages/lsa/index.html

lsmeans 2.27-61 https://cran.r-

project.org/web/packages/lsmeans/inde
x.html

lubridate 1.7.2 https://cran.r-

project.org/web/packages/lubridate/ind
ex.html

magic 1.5-8 https://cran.r-

project.org/web/packages/magic/index.h
tml

magick 1.8 https://cran.r-

project.org/web/packages/magick/index.
html

magrittr 1.5 https://cran.r-

project.org/web/packages/magrittr/inde
x.html

manipulateWidget 0.9.0 https://cran.r-

project.org/web/packages/manipulateWi
dget/index.html

MAPA 2.0.4 https://cran.r-

project.org/web/packages/MAPA/index.
html

mapdata 2.3.0 https://cran.r-

project.org/web/packages/mapdata/ind
ex.html

mapproj 1.2.6 https://cran.r-

project.org/web/packages/mapproj/inde
x.html

maps 3.2.0 https://cran.r-

project.org/web/packages/maps/index.h
tml

maptools 0.9-2 https://cran.r-

project.org/web/packages/maptools/ind
ex.html
PA C K A GE VERSIO N L IN K

maptree 1.4-7 https://cran.r-

project.org/web/packages/maptree/inde
x.html

mapview 2.3.0 https://cran.r-

project.org/web/packages/mapview/ind
ex.html

marima 2.2 https://cran.r-

project.org/web/packages/marima/index
.html

markdown 0.8 https://cran.r-

project.org/web/packages/markdown/in
dex.html

MASS 7.3-49 https://cran.r-

project.org/web/packages/MASS/index.h
tml

MasterBayes 2.55 https://cran.r-

project.org/web/packages/MasterBayes/
index.html

Matching 4.9-5 https://cran.r-

project.org/web/packages/Matching/ind
ex.html

MatchIt 3.0.2 https://cran.r-

project.org/web/packages/MatchIt/inde
x.html

Matrix 1.2-12 https://cran.r-

project.org/web/packages/Matrix/index.
html

matrixcalc 1.0-3 https://cran.r-

project.org/web/packages/matrixcalc/ind
ex.html

MatrixModels 0.4-1 https://cran.r-

project.org/web/packages/MatrixModels
/index.html

matrixStats 0.54.0 https://cran.r-

project.org/web/packages/matrixStats/in
dex.html

maxent 1.3.3.1 https://cran.r-

project.org/web/packages/maxent/index
.html

maxLik 1.3-4 https://cran.r-

project.org/web/packages/maxLik/index.
html
PA C K A GE VERSIO N L IN K

maxstat 0.7-25 https://cran.r-

project.org/web/packages/maxstat/inde
x.html

mboost 2.8-1 https://cran.r-

project.org/web/packages/mboost/index
.html

mclust 5.4 https://cran.r-

project.org/web/packages/mclust/index.
html

mcmc 0.9-5 https://cran.r-

project.org/web/packages/mcmc/index.h
tml

MCMCglmm 2.25 https://cran.r-

project.org/web/packages/MCMCglmm/
index.html

mda 0.4-10 https://cran.r-

project.org/web/packages/mda/index.ht
ml

memoise 1.1.0 https://cran.r-

project.org/web/packages/memoise/ind
ex.html

merTools 0.3.0 https://cran.r-

project.org/web/packages/merTools/ind
ex.html

methods 3.4.4 NA

metricsgraphics 0.9.0 https://cran.r-

project.org/web/packages/metricsgraphi
cs/index.html

mgcv 1.8-23 https://cran.r-

project.org/web/packages/mgcv/index.h
tml

mgsub 1.7.1 https://cran.r-

project.org/web/packages/mgsub/index.
html

mi 1.0 https://cran.r-
project.org/web/packages/mi/index.html

mice 2.46.0 https://cran.r-

project.org/web/packages/mice/index.ht
ml
PA C K A GE VERSIO N L IN K

microbenchmark 1.4-4 https://cran.r-

project.org/web/packages/microbenchm
ark/index.html

MicrosoftR 3.4.4.0105 NA

mime 0.5 https://cran.r-

project.org/web/packages/mime/index.h
tml

miniCRAN 0.2.11 https://cran.r-

project.org/web/packages/miniCRAN/in
dex.html

miniUI 0.1.1 https://cran.r-

project.org/web/packages/miniUI/index.
html

minpack.lm 1.2-1 https://cran.r-

project.org/web/packages/minpack.lm/i
ndex.html

minqa 1.2.4 https://cran.r-

project.org/web/packages/minqa/index.
html

mirt 1.27.1 https://cran.r-

project.org/web/packages/mirt/index.ht
ml

misc3d 0.8-4 https://cran.r-

project.org/web/packages/misc3d/index.
html

miscTools 0.6-22 https://cran.r-

project.org/web/packages/miscTools/ind
ex.html

mitools 2.3 https://cran.r-

project.org/web/packages/mitools/index
.html

mixtools 1.1.0 https://cran.r-

project.org/web/packages/mixtools/inde
x.html

mlapi 0.1.0 https://cran.r-

project.org/web/packages/mlapi/index.h
tml

mlbench 2.1-1 https://cran.r-

project.org/web/packages/mlbench/inde
x.html
PA C K A GE VERSIO N L IN K

mlogitBMA 0.1-6 https://cran.r-

project.org/web/packages/mlogitBMA/i
ndex.html

mnormt 1.5-5 https://cran.r-

project.org/web/packages/mnormt/inde
x.html

MNP 3.1-0 https://cran.r-

project.org/web/packages/MNP/index.ht
ml

ModelMetrics 1.1.0 https://cran.r-

project.org/web/packages/ModelMetrics
/index.html

modelr 0.1.1 https://cran.r-

project.org/web/packages/modelr/index.
html

modeltools 0.2-21 https://cran.r-

project.org/web/packages/modeltools/in
dex.html

mombf 1.9.6 https://cran.r-

project.org/web/packages/mombf/index.
html

moments 0.14 https://cran.r-

project.org/web/packages/moments/ind
ex.html

monomvn 1.9-7 https://cran.r-

project.org/web/packages/monomvn/in
dex.html

monreg 0.1.3 https://cran.r-

project.org/web/packages/monreg/inde
x.html

mosaic 1.1.1 https://cran.r-

project.org/web/packages/mosaic/index.
html

mosaicCore 0.4.2 https://cran.r-

project.org/web/packages/mosaicCore/i
ndex.html

mosaicData 0.16.0 https://cran.r-

project.org/web/packages/mosaicData/i
ndex.html

MSBVAR 0.9-3 https://cran.r-

project.org/web/packages/MSBVAR/inde
x.html
PA C K A GE VERSIO N L IN K

msm 1.6.6 https://cran.r-

project.org/web/packages/msm/index.ht
ml

multcomp 1.4-8 https://cran.r-

project.org/web/packages/multcomp/in
dex.html

multicool 0.1-10 https://cran.r-

project.org/web/packages/multicool/ind
ex.html

munsell 0.5.0 https://cran.r-

project.org/web/packages/munsell/index
.html

mvoutlier 2.0.9 https://cran.r-

project.org/web/packages/mvoutlier/ind
ex.html

mvtnorm 1.0-7 https://cran.r-

project.org/web/packages/mvtnorm/ind
ex.html

NbClust 3.0 https://cran.r-

project.org/web/packages/NbClust/inde
x.html

ncvreg 3.9-1 https://cran.r-

project.org/web/packages/ncvreg/index.
html

network 1.13.0 https://cran.r-

project.org/web/packages/network/inde
x.html

networkD3 0.4 https://cran.r-

project.org/web/packages/networkD3/in
dex.html

neuralnet 1.33 https://cran.r-

project.org/web/packages/neuralnet/ind
ex.html

ngram 3.0.4 https://cran.r-

project.org/web/packages/ngram/index.
html

nlme 3.1-131.1 https://cran.r-

project.org/web/packages/nlme/index.ht
ml

nloptr 1.0.4 https://cran.r-

project.org/web/packages/nloptr/index.
html
PA C K A GE VERSIO N L IN K

NLP 0.1-11 https://cran.r-

project.org/web/packages/NLP/index.ht
ml

NMF 0.21.0 https://cran.r-

project.org/web/packages/NMF/index.ht
ml

nnet 7.3-12 https://cran.r-

project.org/web/packages/nnet/index.ht
ml

nnls 1.4 https://cran.r-

project.org/web/packages/nnls/index.ht
ml

nortest 1.0-4 https://cran.r-

project.org/web/packages/nortest/index.
html

numbers 0.6-6 https://cran.r-

project.org/web/packages/numbers/ind
ex.html

numDeriv 2016.8-1 https://cran.r-

project.org/web/packages/numDeriv/ind
ex.html

numform 0.4.0 https://cran.r-

project.org/web/packages/numform/ind
ex.html

OceanView 1.0.4 https://cran.r-

project.org/web/packages/OceanView/in
dex.html

openair 2.3-0 https://cran.r-

project.org/web/packages/openair/index
.html

openssl 1.0.1 https://cran.r-

project.org/web/packages/openssl/index
.html

osmar 1.1-7 https://cran.r-

project.org/web/packages/osmar/index.
html

OutlierDC 0.3-0 https://cran.r-

project.org/web/packages/OutlierDC/in
dex.html

OutlierDM 1.1.1 https://cran.r-

project.org/web/packages/OutlierDM/in
dex.html
PA C K A GE VERSIO N L IN K

outliers 0.14 https://cran.r-

project.org/web/packages/outliers/index
.html

pacbpred 0.92.2 https://cran.r-

project.org/web/packages/pacbpred/ind
ex.html

padr 0.4.0 https://cran.r-

project.org/web/packages/padr/index.ht
ml

parallel 3.4.4 NA

partitions 1.9-19 https://cran.r-

project.org/web/packages/partitions/ind
ex.html

party 1.2-4 https://cran.r-

project.org/web/packages/party/index.h
tml

partykit 1.2-0 https://cran.r-

project.org/web/packages/partykit/index
.html

PAWL 0.5 https://cran.r-

project.org/web/packages/PAWL/index.h
tml

pbapply 1.3-4 https://cran.r-

project.org/web/packages/pbapply/inde
x.html

pbivnorm 0.6.0 https://cran.r-

project.org/web/packages/pbivnorm/ind
ex.html

pbkrtest 0.4-7 https://cran.r-

project.org/web/packages/pbkrtest/inde
x.html

PCAmixdata 3.1 https://cran.r-

project.org/web/packages/PCAmixdata/i
ndex.html

pcaPP 1.9-73 https://cran.r-

project.org/web/packages/pcaPP/index.
html

pdc 1.0.3 https://cran.r-

project.org/web/packages/pdc/index.ht
ml
PA C K A GE VERSIO N L IN K

PerformanceAnalytics 1.5.2 https://cran.r-

project.org/web/packages/Performance
Analytics/index.html

permute 0.9-4 https://cran.r-

project.org/web/packages/permute/inde
x.html

perry 0.2.0 https://cran.r-

project.org/web/packages/perry/index.h
tml

petrinetR 0.1.0 https://cran.r-

project.org/web/packages/petrinetR/ind
ex.html

pheatmap 1.0.8 https://cran.r-

project.org/web/packages/pheatmap/in
dex.html

pillar 1.4.2 https://cran.r-

project.org/web/packages/pillar/index.ht
ml

pixmap 0.4-11 https://cran.r-

project.org/web/packages/pixmap/index.
html

pkgconfig 2.0.2 https://cran.r-

project.org/web/packages/pkgconfig/ind
ex.html

pkgmaker 0.22 https://cran.r-

project.org/web/packages/pkgmaker/in
dex.html

platetools 0.1.0 https://cran.r-

project.org/web/packages/platetools/ind
ex.html

plogr 0.2.0 https://cran.r-

project.org/web/packages/plogr/index.h
tml

plot3D 1.1.1 https://cran.r-

project.org/web/packages/plot3D/index.
html

plot3Drgl 1.0.1 https://cran.r-

project.org/web/packages/plot3Drgl/ind
ex.html

plotly 4.7.1 https://cran.r-

project.org/web/packages/plotly/index.h
tml
PA C K A GE VERSIO N L IN K

plotmo 3.3.6 https://cran.r-

project.org/web/packages/plotmo/index.
html

plotrix 3.7 https://cran.r-

project.org/web/packages/plotrix/index.
html

pls 2.6-0 https://cran.r-

project.org/web/packages/pls/index.htm
l

plyr 1.8.4 https://cran.r-

project.org/web/packages/plyr/index.ht
ml

png 0.1-7 https://cran.r-

project.org/web/packages/png/index.ht
ml

polspline 1.1.12 https://cran.r-

project.org/web/packages/polspline/ind
ex.html

polyclip 1.6-1 https://cran.r-

project.org/web/packages/polyclip/index
.html

polylabelr 0.1.0 https://cran.r-

project.org/web/packages/polylabelr/ind
ex.html

polynom 1.3-9 https://cran.r-

project.org/web/packages/polynom/ind
ex.html

ppcor 1.1 https://cran.r-

project.org/web/packages/ppcor/index.h
tml

prabclus 2.2-6 https://cran.r-

project.org/web/packages/prabclus/inde
x.html

pracma 2.1.4 https://cran.r-

project.org/web/packages/pracma/index
.html

praise 1.0.0 https://cran.r-

project.org/web/packages/praise/index.h
tml

prediction 0.2.0 https://cran.r-

project.org/web/packages/prediction/in
dex.html
PA C K A GE VERSIO N L IN K

predmixcor 1.1-1 https://cran.r-

project.org/web/packages/predmixcor/in
dex.html

PresenceAbsence 1.1.9 https://cran.r-

project.org/web/packages/PresenceAbse
nce/index.html

prettyunits 1.0.2 https://cran.r-

project.org/web/packages/prettyunits/in
dex.html

pROC 1.11.0 https://cran.r-

project.org/web/packages/pROC/index.h
tml

processmapR 0.3.2 https://cran.r-

project.org/web/packages/processmapR
/index.html

processmonitR 0.1.0 https://cran.r-

project.org/web/packages/processmonit
R/index.html

processx 2.0.0.1 https://cran.r-

project.org/web/packages/processx/inde
x.html

prodlim 1.6.1 https://cran.r-

project.org/web/packages/prodlim/index
.html

profdpm 3.3 https://cran.r-

project.org/web/packages/profdpm/inde
x.html

profileModel 0.5-9 https://cran.r-

project.org/web/packages/profileModel/
index.html

progress 1.1.2 https://cran.r-

project.org/web/packages/progress/inde
x.html

proj4 1.0-8 https://cran.r-

project.org/web/packages/proj4/index.h
tml

prophet 0.2.1 https://cran.r-

project.org/web/packages/prophet/inde
x.html

proto 1.0.0 https://cran.r-

project.org/web/packages/proto/index.h
tml
PA C K A GE VERSIO N L IN K

protolite 1.7 https://cran.r-

project.org/web/packages/protolite/inde
x.html

proxy 0.4-21 https://cran.r-

project.org/web/packages/proxy/index.h
tml

pryr 0.1.4 https://cran.r-

project.org/web/packages/pryr/index.ht
ml

pscl 1.5.2 https://cran.r-

project.org/web/packages/pscl/index.ht
ml

psych 1.8.3.3 https://cran.r-

project.org/web/packages/psych/index.h
tml

purrr 0.2.4 https://cran.r-

project.org/web/packages/purrr/index.ht
ml

pwr 1.2-2 https://cran.r-

project.org/web/packages/pwr/index.ht
ml

qap 0.1-1 https://cran.r-

project.org/web/packages/qap/index.ht
ml

qcc 2.7 https://cran.r-

project.org/web/packages/qcc/index.ht
ml

qdapDictionaries 1.0.7 https://cran.r-

project.org/web/packages/qdapDictiona
ries/index.html

qdapRegex 0.7.2 https://cran.r-

project.org/web/packages/qdapRegex/in
dex.html

qdapTools 1.3.3 https://cran.r-

project.org/web/packages/qdapTools/in
dex.html

qgraph 1.4.4 https://cran.r-

project.org/web/packages/qgraph/index.
html

qicharts 0.5.5 https://cran.r-

project.org/web/packages/qicharts/inde
x.html
PA C K A GE VERSIO N L IN K

qicharts2 0.6.0 https://cran.r-

project.org/web/packages/qicharts2/ind
ex.html

quadprog 1.5-5 https://cran.r-

project.org/web/packages/quadprog/ind
ex.html

qualityTools 1.55 https://cran.r-

project.org/web/packages/qualityTools/i
ndex.html

quanteda 1.1.1 https://cran.r-

project.org/web/packages/quanteda/ind
ex.html

quantmod 0.4-12 https://cran.r-

project.org/web/packages/quantmod/in
dex.html

quantreg 5.35 https://cran.r-

project.org/web/packages/quantreg/ind
ex.html

questionr 0.6.2 https://cran.r-

project.org/web/packages/questionr/ind
ex.html

qvcalc 0.9-1 https://cran.r-

project.org/web/packages/qvcalc/index.
html

R.matlab 3.6.1 https://cran.r-

project.org/web/packages/R.matlab/inde
x.html

R.methodsS3 1.7.1 https://cran.r-

project.org/web/packages/R.methodsS3
/index.html

R.oo 1.21.0 https://cran.r-

project.org/web/packages/R.oo/index.ht
ml

R.utils 2.6.0 https://cran.r-

project.org/web/packages/R.utils/index.h
tml

r2d3 0.2.3 https://cran.r-

project.org/web/packages/r2d3/index.ht
ml

R2HTML 2.3.2 https://cran.r-

project.org/web/packages/R2HTML/inde
x.html
PA C K A GE VERSIO N L IN K

R2jags 0.5-7 https://cran.r-

project.org/web/packages/R2jags/index.
html

R2OpenBUGS 3.2-3.2 https://cran.r-

project.org/web/packages/R2OpenBUG
S/index.html

R2WinBUGS 2.1-21 https://cran.r-

project.org/web/packages/R2WinBUGS/i
ndex.html

R6 2.2.2 https://cran.r-
project.org/web/packages/R6/index.html

ramps 0.6-15 https://cran.r-

project.org/web/packages/ramps/index.
html

RandomFields 3.1.50 https://cran.r-

project.org/web/packages/RandomField
s/index.html

RandomFieldsUtils 0.3.25 https://cran.r-

project.org/web/packages/RandomField
sUtils/index.html

randomForest 4.6-14 https://cran.r-

project.org/web/packages/randomFores
t/index.html

ranger 0.9.0 https://cran.r-

project.org/web/packages/ranger/index.
html

RApiDatetime 0.0.4 https://cran.r-

project.org/web/packages/RApiDatetime
/index.html

rappdirs 0.3.1 https://cran.r-

project.org/web/packages/rappdirs/inde
x.html

RArcInfo 0.4-12 https://cran.r-

project.org/web/packages/RArcInfo/inde
x.html

raster 2.6-7 https://cran.r-

project.org/web/packages/raster/index.h
tml

rattle 5.1.0 https://cran.r-

project.org/web/packages/rattle/index.h
tml
PA C K A GE VERSIO N L IN K

rayshader 0.10.1 https://cran.r-

project.org/web/packages/rayshader/ind
ex.html

rbenchmark 1.0.0 https://cran.r-

project.org/web/packages/rbenchmark/i
ndex.html

Rblpapi 0.3.8 https://cran.r-

project.org/web/packages/Rblpapi/index
.html

rbokeh 0.5.0 https://cran.r-

project.org/web/packages/rbokeh/index.
html

rbugs 0.5-9 https://cran.r-

project.org/web/packages/rbugs/index.h
tml

RColorBrewer 1.1-2 https://cran.r-

project.org/web/packages/RColorBrewer
/index.html

Rcpp 1.0.1 https://cran.r-

project.org/web/packages/Rcpp/index.ht
ml

RcppArmadillo 0.8.400.0.0 https://cran.r-

project.org/web/packages/RcppArmadill
o/index.html

rcppbugs 0.1.4.2 https://cran.r-

project.org/web/packages/rcppbugs/ind
ex.html

RcppDE 0.1.5 https://cran.r-

project.org/web/packages/RcppDE/index
.html

RcppEigen 0.3.3.4.0 https://cran.r-

project.org/web/packages/RcppEigen/in
dex.html

RcppExamples 0.1.8 https://cran.r-

project.org/web/packages/RcppExample
s/index.html

RcppParallel 4.4.0 https://cran.r-

project.org/web/packages/RcppParallel/i
ndex.html

RcppProgress 0.4 https://cran.r-

project.org/web/packages/RcppProgress
/index.html
PA C K A GE VERSIO N L IN K

RcppRoll 0.2.2 https://cran.r-

project.org/web/packages/RcppRoll/inde
x.html

RCurl 1.95-4.10 https://cran.r-

project.org/web/packages/RCurl/index.h
tml

readbitmap 0.1-4 https://cran.r-

project.org/web/packages/readbitmap/i
ndex.html

readr 1.1.1 https://cran.r-

project.org/web/packages/readr/index.h
tml

readxl 1.0.0 https://cran.r-

project.org/web/packages/readxl/index.h
tml

recipes 0.1.2 https://cran.r-

project.org/web/packages/recipes/index.
html

Redmonder 0.2.0 https://cran.r-

project.org/web/packages/Redmonder/i
ndex.html

registry 0.5 https://cran.r-

project.org/web/packages/registry/index
.html

relaimpo 2.2-3 https://cran.r-

project.org/web/packages/relaimpo/inde
x.html

relimp 1.0-5 https://cran.r-

project.org/web/packages/relimp/index.
html

rematch 1.0.1 https://cran.r-

project.org/web/packages/rematch/inde
x.html

Renext 3.1-0 https://cran.r-

project.org/web/packages/Renext/index.
html

reports 0.1.4 https://cran.r-

project.org/web/packages/reports/index.
html

reprex 0.1.2 https://cran.r-

project.org/web/packages/reprex/index.
html
PA C K A GE VERSIO N L IN K

reshape 0.8.7 https://cran.r-

project.org/web/packages/reshape/inde
x.html

reshape2 1.4.3 https://cran.r-

project.org/web/packages/reshape2/ind
ex.html

reticulate 1.6 https://cran.r-

project.org/web/packages/reticulate/ind
ex.html

RevoIOQ 8.0.10 NA

RevoMods 11.0.0 NA

RevoUtils 10.0.9 NA

RevoUtilsMath 10.0.1 NA

rex 1.1.2 https://cran.r-

project.org/web/packages/rex/index.htm
l

rFerns 2.0.3 https://cran.r-

project.org/web/packages/rFerns/index.
html

rfm 0.2.0 https://cran.r-

project.org/web/packages/rfm/index.ht
ml

rgdal 1.2-18 https://cran.r-

project.org/web/packages/rgdal/index.ht
ml

rgeos 0.3-26 https://cran.r-

project.org/web/packages/rgeos/index.h
tml

rgexf 0.15.3 https://cran.r-

project.org/web/packages/rgexf/index.ht
ml

rgl 0.99.16 https://cran.r-

project.org/web/packages/rgl/index.html

RgoogleMaps 1.4.1 https://cran.r-

project.org/web/packages/RgoogleMaps
/index.html

RGraphics 2.0-14 https://cran.r-

project.org/web/packages/RGraphics/in
dex.html
PA C K A GE VERSIO N L IN K

RGtk2 2.20.34 https://cran.r-

project.org/web/packages/RGtk2/index.
html

RInside 0.2.14 https://cran.r-

project.org/web/packages/RInside/index.
html

RJaCGH 2.0.4 https://cran.r-

project.org/web/packages/RJaCGH/inde
x.html

rjags 4-6 https://cran.r-

project.org/web/packages/rjags/index.ht
ml

rjson 0.2.15 https://cran.r-

project.org/web/packages/rjson/index.ht
ml

RJSONIO 1.3-0 https://cran.r-

project.org/web/packages/RJSONIO/ind
ex.html

rlang 0.3.4 https://cran.r-

project.org/web/packages/rlang/index.ht
ml

rlecuyer 0.3-4 https://cran.r-

project.org/web/packages/rlecuyer/inde
x.html

rlist 0.4.6.1 https://cran.r-

project.org/web/packages/rlist/index.ht
ml

rmapshaper 0.3.0 https://cran.r-

project.org/web/packages/rmapshaper/i
ndex.html

rmarkdown 1.9 https://cran.r-

project.org/web/packages/rmarkdown/i
ndex.html

Rmisc 1.5 https://cran.r-

project.org/web/packages/Rmisc/index.h
tml

Rmpfr 0.7-0 https://cran.r-

project.org/web/packages/Rmpfr/index.
html

rms 5.1-2 https://cran.r-

project.org/web/packages/rms/index.ht
ml
PA C K A GE VERSIO N L IN K

RMySQL 0.10.14 https://cran.r-

project.org/web/packages/RMySQL/inde
x.html

rngtools 1.2.4 https://cran.r-

project.org/web/packages/rngtools/inde
x.html

robCompositions 2.0.6 https://cran.r-

project.org/web/packages/robCompositi
ons/index.html

robfilter 4.1 https://cran.r-

project.org/web/packages/robfilter/inde
x.html

robustbase 0.92-8 https://cran.r-

project.org/web/packages/robustbase/in
dex.html

robustHD 0.5.1 https://cran.r-

project.org/web/packages/robustHD/ind
ex.html

ROCR 1.0-7 https://cran.r-

project.org/web/packages/ROCR/index.h
tml

RODBC 1.3-15 https://cran.r-

project.org/web/packages/RODBC/index
.html

Rook 1.1-1 https://cran.r-

project.org/web/packages/Rook/index.ht
ml

rootSolve 1.7 https://cran.r-

project.org/web/packages/rootSolve/ind
ex.html

roxygen2 6.0.1 https://cran.r-

project.org/web/packages/roxygen2/ind
ex.html

rpart 4.1-13 https://cran.r-

project.org/web/packages/rpart/index.ht
ml

rpart.plot 2.1.2 https://cran.r-

project.org/web/packages/rpart.plot/ind
ex.html

rpivotTable 0.3.0 https://cran.r-

project.org/web/packages/rpivotTable/in
dex.html
PA C K A GE VERSIO N L IN K

rprojroot 1.3-2 https://cran.r-

project.org/web/packages/rprojroot/ind
ex.html

rrcov 1.4-3 https://cran.r-

project.org/web/packages/rrcov/index.ht
ml

rscproxy 2.0-5 https://cran.r-

project.org/web/packages/rscproxy/inde
x.html

rsdmx 0.5-11 https://cran.r-

project.org/web/packages/rsdmx/index.
html

RSGHB 1.1.2 https://cran.r-

project.org/web/packages/RSGHB/index.
html

RSiteCatalyst 1.4.14 https://cran.r-

project.org/web/packages/RSiteCatalyst/
index.html

RSNNS 0.4-10 https://cran.r-

project.org/web/packages/RSNNS/index.
html

Rsolnp 1.16 https://cran.r-

project.org/web/packages/Rsolnp/index.
html

RSpectra 0.12-0 https://cran.r-

project.org/web/packages/RSpectra/inde
x.html

RSQLite 2.1.0 https://cran.r-

project.org/web/packages/RSQLite/inde
x.html

rstan 2.17.3 https://cran.r-

project.org/web/packages/rstan/index.ht
ml

rstudioapi 0.7 https://cran.r-

project.org/web/packages/rstudioapi/in
dex.html

rsvg 1.1 https://cran.r-

project.org/web/packages/rsvg/index.ht
ml

RTextTools 1.4.2 https://cran.r-

project.org/web/packages/RTextTools/in
dex.html
PA C K A GE VERSIO N L IN K

Rttf2pt1 1.3.6 https://cran.r-

project.org/web/packages/Rttf2pt1/inde
x.html

RUnit 0.4.31 https://cran.r-

project.org/web/packages/RUnit/index.h
tml

runjags 2.0.4-2 https://cran.r-

project.org/web/packages/runjags/index
.html

Runuran 0.24 https://cran.r-

project.org/web/packages/Runuran/inde
x.html

rvcheck 0.0.9 https://cran.r-

project.org/web/packages/rvcheck/index
.html

rvest 0.3.2 https://cran.r-

project.org/web/packages/rvest/index.ht
ml

rworldmap 1.3-6 https://cran.r-

project.org/web/packages/rworldmap/in
dex.html

rworldxtra 1.01 https://cran.r-

project.org/web/packages/rworldxtra/in
dex.html

SampleSizeMeans 1.1 https://cran.r-

project.org/web/packages/SampleSizeM
eans/index.html

SampleSizeProportions 1.0 https://cran.r-

project.org/web/packages/SampleSizePr
oportions/index.html

sandwich 2.4-0 https://cran.r-

project.org/web/packages/sandwich/ind
ex.html

sas7bdat 0.5 https://cran.r-

project.org/web/packages/sas7bdat/ind
ex.html

satellite 1.0.1 https://cran.r-

project.org/web/packages/satellite/index
.html

sbgcop 0.975 https://cran.r-

project.org/web/packages/sbgcop/index.
html
PA C K A GE VERSIO N L IN K

scales 1.0.0 https://cran.r-

project.org/web/packages/scales/index.h
tml

scatterplot3d 0.3-41 https://cran.r-

project.org/web/packages/scatterplot3d
/index.html

sciplot 1.1-1 https://cran.r-

project.org/web/packages/sciplot/index.
html

segmented 0.5-3.0 https://cran.r-

project.org/web/packages/segmented/in
dex.html

selectr 0.4-0 https://cran.r-

project.org/web/packages/selectr/index.
html

sem 3.1-9 https://cran.r-

project.org/web/packages/sem/index.ht
ml

sentimentr 2.7.1 https://cran.r-

project.org/web/packages/sentimentr/in
dex.html

seriation 1.2-3 https://cran.r-

project.org/web/packages/seriation/inde
x.html

setRNG 2013.9-1 https://cran.r-

project.org/web/packages/setRNG/index
.html

sf 0.6-1 https://cran.r-
project.org/web/packages/sf/index.html

sfsmisc 1.1-2 https://cran.r-

project.org/web/packages/sfsmisc/index.
html

sgeostat 1.0-27 https://cran.r-

project.org/web/packages/sgeostat/inde
x.html

shape 1.4.4 https://cran.r-

project.org/web/packages/shape/index.h
tml

shapefiles 0.7 https://cran.r-

project.org/web/packages/shapefiles/ind
ex.html
PA C K A GE VERSIO N L IN K

shiny 1.0.5 https://cran.r-

project.org/web/packages/shiny/index.h
tml

shinyBS 0.61 https://cran.r-

project.org/web/packages/shinyBS/index
.html

shinycssloaders 0.2.0 https://cran.r-

project.org/web/packages/shinycssloade
rs/index.html

shinyjs 1.0 https://cran.r-

project.org/web/packages/shinyjs/index.
html

shinyTime 0.2.1 https://cran.r-

project.org/web/packages/shinyTime/in
dex.html

showtext 0.5-1 https://cran.r-

project.org/web/packages/showtext/ind
ex.html

showtextdb 2.0 https://cran.r-

project.org/web/packages/showtextdb/i
ndex.html

SIS 0.8-6 https://cran.r-

project.org/web/packages/SIS/index.htm
l

SixSigma 0.9-51 https://cran.r-

project.org/web/packages/SixSigma/inde
x.html

sjlabelled 1.0.8 https://cran.r-

project.org/web/packages/sjlabelled/ind
ex.html

sjmisc 2.7.1 https://cran.r-

project.org/web/packages/sjmisc/index.h
tml

sjPlot 2.4.1 https://cran.r-

project.org/web/packages/sjPlot/index.h
tml

sjstats 0.14.2-3 https://cran.r-

project.org/web/packages/sjstats/index.
html

skmeans 0.2-11 https://cran.r-

project.org/web/packages/skmeans/inde
x.html
PA C K A GE VERSIO N L IN K

slam 0.1-42 https://cran.r-

project.org/web/packages/slam/index.ht
ml

sm 2.2-5.4 https://cran.r-
project.org/web/packages/sm/index.htm
l

smooth 2.4.1 https://cran.r-

project.org/web/packages/smooth/index
.html

smoothSurv 2.0 https://cran.r-

project.org/web/packages/smoothSurv/i
ndex.html

sna 2.4 https://cran.r-

project.org/web/packages/sna/index.ht
ml

snakecase 0.9.1 https://cran.r-

project.org/web/packages/snakecase/in
dex.html

snow 0.4-2 https://cran.r-

project.org/web/packages/snow/index.h
tml

SnowballC 0.5.1 https://cran.r-

project.org/web/packages/SnowballC/in
dex.html

snowFT 1.6-0 https://cran.r-

project.org/web/packages/snowFT/index
.html

sourcetools 0.1.6 https://cran.r-

project.org/web/packages/sourcetools/i
ndex.html

sp 1.2-7 https://cran.r-
project.org/web/packages/sp/index.html

spacetime 1.2-1 https://cran.r-

project.org/web/packages/spacetime/in
dex.html

spacyr 0.9.6 https://cran.r-

project.org/web/packages/spacyr/index.
html

spam 2.1-3 https://cran.r-

project.org/web/packages/spam/index.h
tml
PA C K A GE VERSIO N L IN K

SparseM 1.77 https://cran.r-

project.org/web/packages/SparseM/inde
x.html

sparsepp 0.2.0 https://cran.r-

project.org/web/packages/sparsepp/ind
ex.html

spatial 7.3-11 https://cran.r-

project.org/web/packages/spatial/index.
html

spatstat 1.55-0 https://cran.r-

project.org/web/packages/spatstat/inde
x.html

spatstat.data 1.2-0 https://cran.r-

project.org/web/packages/spatstat.data/
index.html

spatstat.utils 1.8-0 https://cran.r-

project.org/web/packages/spatstat.utils/
index.html

spBayes 0.4-1 https://cran.r-

project.org/web/packages/spBayes/inde
x.html

spData 0.2.8.3 https://cran.r-

project.org/web/packages/spData/index.
html

spdep 0.7-4 https://cran.r-

project.org/web/packages/spdep/index.
html

spikeslab 1.1.5 https://cran.r-

project.org/web/packages/spikeslab/ind
ex.html

splancs 2.01-40 https://cran.r-

project.org/web/packages/splancs/index.
html

splines 3.4.4 NA

spls 2.2-2 https://cran.r-

project.org/web/packages/spls/index.ht
ml

splus2R 1.2-2 https://cran.r-

project.org/web/packages/splus2R/index
.html
PA C K A GE VERSIO N L IN K

spTimer 3.0-1 https://cran.r-

project.org/web/packages/spTimer/inde
x.html

sqldf 0.4-11 https://cran.r-

project.org/web/packages/sqldf/index.ht
ml

SQUAREM 2017.10-1 https://cran.r-

project.org/web/packages/SQUAREM/in
dex.html

sROC 0.1-2 https://cran.r-

project.org/web/packages/sROC/index.h
tml

stabledist 0.7-1 https://cran.r-

project.org/web/packages/stabledist/ind
ex.html

stabs 0.6-3 https://cran.r-

project.org/web/packages/stabs/index.h
tml

StanHeaders 2.17.2 https://cran.r-

project.org/web/packages/StanHeaders/i
ndex.html

statmod 1.4.30 https://cran.r-

project.org/web/packages/statmod/inde
x.html

statnet.common 4.0.0 https://cran.r-

project.org/web/packages/statnet.comm
on/index.html

stats 3.4.4 NA

stats4 3.4.4 NA

stepPlr 0.93 https://cran.r-

project.org/web/packages/stepPlr/index.
html

stochvol 1.3.3 https://cran.r-

project.org/web/packages/stochvol/inde
x.html

stopwords 0.9.0 https://cran.r-

project.org/web/packages/stopwords/in
dex.html

stringdist 0.9.4.7 https://cran.r-

project.org/web/packages/stringdist/ind
ex.html
PA C K A GE VERSIO N L IN K

stringi 1.1.7 https://cran.r-

project.org/web/packages/stringi/index.
html

stringr 1.3.0 https://cran.r-

project.org/web/packages/stringr/index.
html

strucchange 1.5-1 https://cran.r-

project.org/web/packages/strucchange/i
ndex.html

stsm 1.9 https://cran.r-

project.org/web/packages/stsm/index.ht
ml

stsm.class 1.3 https://cran.r-

project.org/web/packages/stsm.class/ind
ex.html

sugrrants 0.2.4 https://cran.r-

project.org/web/packages/sugrrants/ind
ex.html

sunburstR 2.0.0 https://cran.r-

project.org/web/packages/sunburstR/in
dex.html

SuppDists 1.1-9.4 https://cran.r-

project.org/web/packages/SuppDists/in
dex.html

survey 3.33-2 https://cran.r-

project.org/web/packages/survey/index.
html

survival 2.41-3 https://cran.r-

project.org/web/packages/survival/index
.html

survminer 0.4.2 https://cran.r-

project.org/web/packages/survminer/in
dex.html

survMisc 0.5.4 https://cran.r-

project.org/web/packages/survMisc/ind
ex.html

svglite 1.2.1 https://cran.r-

project.org/web/packages/svglite/index.
html

svmpath 0.955 https://cran.r-

project.org/web/packages/svmpath/inde
x.html
PA C K A GE VERSIO N L IN K

svUnit 0.7-12 https://cran.r-

project.org/web/packages/svUnit/index.
html

sweep 0.2.1 https://cran.r-

project.org/web/packages/sweep/index.
html

sysfonts 0.7.2 https://cran.r-

project.org/web/packages/sysfonts/inde
x.html

systemfit 1.1-20 https://cran.r-

project.org/web/packages/systemfit/ind
ex.html

syuzhet 1.0.4 https://cran.r-

project.org/web/packages/syuzhet/index
.html

tau 0.0-20 https://cran.r-

project.org/web/packages/tau/index.ht
ml

tcltk 3.4.4 NA

tcltk2 1.2-11 https://cran.r-

project.org/web/packages/tcltk2/index.h
tml

TeachingDemos 2.10 https://cran.r-

project.org/web/packages/TeachingDem
os/index.html

tensor 1.5 https://cran.r-

project.org/web/packages/tensor/index.
html

tensorA 0.36 https://cran.r-

project.org/web/packages/tensorA/inde
x.html

testthat 2.0.0 https://cran.r-

project.org/web/packages/testthat/inde
x.html

text2vec 0.5.1 https://cran.r-

project.org/web/packages/text2vec/inde
x.html

textcat 1.0-5 https://cran.r-

project.org/web/packages/textcat/index.
html
PA C K A GE VERSIO N L IN K

textclean 0.9.3 https://cran.r-

project.org/web/packages/textclean/ind
ex.html

textir 2.0-5 https://cran.r-

project.org/web/packages/textir/index.ht
ml

textmineR 2.1.1 https://cran.r-

project.org/web/packages/textmineR/in
dex.html

textshape 1.6.0 https://cran.r-

project.org/web/packages/textshape/ind
ex.html

tfplot 2015.12-1 https://cran.r-

project.org/web/packages/tfplot/index.h
tml

tframe 2015.12-1 https://cran.r-

project.org/web/packages/tframe/index.
html

tgp 2.4-14 https://cran.r-

project.org/web/packages/tgp/index.ht
ml

TH.data 1.0-8 https://cran.r-

project.org/web/packages/TH.data/index
.html

threejs 0.3.1 https://cran.r-

project.org/web/packages/threejs/index.
html

tibble 2.1.1 https://cran.r-

project.org/web/packages/tibble/index.h
tml

tibbletime 0.1.1 https://cran.r-

project.org/web/packages/tibbletime/in
dex.html

tidycensus 0.4.1 https://cran.r-

project.org/web/packages/tidycensus/in
dex.html

tidyr 0.8.0 https://cran.r-

project.org/web/packages/tidyr/index.ht
ml

tidyselect 0.2.5 https://cran.r-

project.org/web/packages/tidyselect/ind
ex.html
PA C K A GE VERSIO N L IN K

tidytext 0.1.8 https://cran.r-

project.org/web/packages/tidytext/index
.html

tidyverse 1.2.1 https://cran.r-

project.org/web/packages/tidyverse/ind
ex.html

tiff 0.1-5 https://cran.r-

project.org/web/packages/tiff/index.html

tigris 0.6.2 https://cran.r-

project.org/web/packages/tigris/index.ht
ml

timeDate 3043.102 https://cran.r-

project.org/web/packages/timeDate/ind
ex.html

timelineS 0.1.1 https://cran.r-

project.org/web/packages/timelineS/ind
ex.html

timeSeries 3042.102 https://cran.r-

project.org/web/packages/timeSeries/in
dex.html

timetk 0.1.0 https://cran.r-

project.org/web/packages/timetk/index.
html

timevis 0.4 https://cran.r-

project.org/web/packages/timevis/index.
html

tm 0.7-3 https://cran.r-
project.org/web/packages/tm/index.htm
l

tmap 1.11-1 https://cran.r-

project.org/web/packages/tmap/index.h
tml

tmaptools 1.2-3 https://cran.r-

project.org/web/packages/tmaptools/in
dex.html

TMB 1.7.13 https://cran.r-

project.org/web/packages/TMB/index.ht
ml

tokenizers 0.2.1 https://cran.r-

project.org/web/packages/tokenizers/in
dex.html
PA C K A GE VERSIO N L IN K

tools 3.4.4 NA

topicmodels 0.2-7 https://cran.r-

project.org/web/packages/topicmodels/i
ndex.html

TraMineR 2.0-8 https://cran.r-

project.org/web/packages/TraMineR/ind
ex.html

translations 3.4.4 NA

tree 1.0-39 https://cran.r-

project.org/web/packages/tree/index.ht
ml

treemap 2.4-2 https://cran.r-

project.org/web/packages/treemap/inde
x.html

trelliscopejs 0.1.18 https://cran.r-

project.org/web/packages/trelliscopejs/i
ndex.html

trimcluster 0.1-2 https://cran.r-

project.org/web/packages/trimcluster/in
dex.html

truncnorm 1.0-8 https://cran.r-

project.org/web/packages/truncnorm/in
dex.html

TSA 1.01 https://cran.r-

project.org/web/packages/TSA/index.ht
ml

tseries 0.10-43 https://cran.r-

project.org/web/packages/tseries/index.
html

tsfa 2014.10-1 https://cran.r-

project.org/web/packages/tsfa/index.ht
ml

tsintermittent 1.9 https://cran.r-

project.org/web/packages/tsintermittent
/index.html

tsoutliers 0.6-6 https://cran.r-

project.org/web/packages/tsoutliers/ind
ex.html

TSP 1.1-5 https://cran.r-

project.org/web/packages/TSP/index.ht
ml
PA C K A GE VERSIO N L IN K

TTR 0.23-3 https://cran.r-

project.org/web/packages/TTR/index.ht
ml

tweedie 2.3.2 https://cran.r-

project.org/web/packages/tweedie/index
.html

tweenr 1.0.1 https://cran.r-

project.org/web/packages/tweenr/index.
html

twitteR 1.1.9 https://cran.r-

project.org/web/packages/twitteR/index.
html

udpipe 0.5 https://cran.r-

project.org/web/packages/udpipe/index.
html

udunits2 0.13 https://cran.r-

project.org/web/packages/udunits2/ind
ex.html

units 0.5-1 https://cran.r-

project.org/web/packages/units/index.ht
ml

UpSetR 1.3.3 https://cran.r-

project.org/web/packages/UpSetR/index
.html

urca 1.3-0 https://cran.r-

project.org/web/packages/urca/index.ht
ml

useful 1.2.3 https://cran.r-

project.org/web/packages/useful/index.h
tml

UsingR 2.0-5 https://cran.r-

project.org/web/packages/UsingR/index.
html

usmap 0.2.1 https://cran.r-

project.org/web/packages/usmap/index.
html

utf8 1.1.3 https://cran.r-

project.org/web/packages/utf8/index.ht
ml

utils 3.4.4 NA
PA C K A GE VERSIO N L IN K

uuid 0.1-2 https://cran.r-

project.org/web/packages/uuid/index.ht
ml

V8 2.2 https://cran.r-
project.org/web/packages/V8/index.htm
l

vars 1.5-2 https://cran.r-

project.org/web/packages/vars/index.ht
ml

vcd 1.4-4 https://cran.r-

project.org/web/packages/vcd/index.ht
ml

vctrs 0.1.0 https://cran.r-

project.org/web/packages/vctrs/index.ht
ml

vdiffr 0.2.2 https://cran.r-

project.org/web/packages/vdiffr/index.ht
ml

vegan 2.4-6 https://cran.r-

project.org/web/packages/vegan/index.
html

VennDiagram 1.6.20 https://cran.r-

project.org/web/packages/VennDiagram
/index.html

VGAM 1.0-5 https://cran.r-

project.org/web/packages/VGAM/index.
html

VIF 1.0 https://cran.r-

project.org/web/packages/VIF/index.ht
ml

VIM 4.7.0 https://cran.r-

project.org/web/packages/VIM/index.ht
ml

vioplot 0.2 https://cran.r-

project.org/web/packages/vioplot/index.
html

viridis 0.5.1 https://cran.r-

project.org/web/packages/viridis/index.h
tml

viridisLite 0.3.0 https://cran.r-

project.org/web/packages/viridisLite/ind
ex.html
PA C K A GE VERSIO N L IN K

visNetwork 2.0.3 https://cran.r-

project.org/web/packages/visNetwork/in
dex.html

vistime 0.4.0 https://cran.r-

project.org/web/packages/vistime/index.
html

wavethresh 4.6.8 https://cran.r-

project.org/web/packages/wavethresh/i
ndex.html

webshot 0.5.0 https://cran.r-

project.org/web/packages/webshot/inde
x.html

webutils 0.6 https://cran.r-

project.org/web/packages/webutils/inde
x.html

weco 1.1 https://cran.r-

project.org/web/packages/weco/index.ht
ml

WeibullR 1.0.10 https://cran.r-

project.org/web/packages/WeibullR/inde
x.html

weights 0.85 https://cran.r-

project.org/web/packages/weights/index
.html

whisker 0.3-2 https://cran.r-

project.org/web/packages/whisker/index
.html

withr 2.1.2 https://cran.r-

project.org/web/packages/withr/index.ht
ml

wmtsa 2.0-3 https://cran.r-

project.org/web/packages/wmtsa/index.
html

wordcloud 2.5 https://cran.r-

project.org/web/packages/wordcloud/in
dex.html

wordcloud2 0.2.1 https://cran.r-

project.org/web/packages/wordcloud2/i
ndex.html

xesreadR 0.2.2 https://cran.r-

project.org/web/packages/xesreadR/ind
ex.html
 PA C K A GE VERSIO N L IN K

xgboost 0.6.4.1 https://cran.r-

project.org/web/packages/xgboost/inde
x.html

XML 3.98-1.10 https://cran.r-

project.org/web/packages/XML/index.ht
ml

xml2 1.2.0 https://cran.r-

project.org/web/packages/xml2/index.ht
ml

xplorerr 0.1.1 https://cran.r-

project.org/web/packages/xplorerr/index
.html

xtable 1.8-2 https://cran.r-

project.org/web/packages/xtable/index.h
tml

xts 0.10-2 https://cran.r-

project.org/web/packages/xts/index.htm
l

yaml 2.1.18 https://cran.r-

project.org/web/packages/yaml/index.ht
ml

yarrr 0.1.5 https://cran.r-

project.org/web/packages/yarrr/index.ht
ml

YieldCurve 4.1 https://cran.r-

project.org/web/packages/YieldCurve/in
dex.html

zeallot 0.1.0 https://cran.r-

project.org/web/packages/zeallot/index.
html

zic 0.9.1 https://cran.r-

project.org/web/packages/zic/index.html

zipfR 0.6-10 https://cran.r-

project.org/web/packages/zipfR/index.ht
ml

zoo 1.8-1 https://cran.r-

project.org/web/packages/zoo/index.ht
ml

R scripts that are not supported in Power BI

The following table shows which packages are not suppor ted in the Power BI service.
 PA C K A GE REQ UEST DAT E REA SO N

RgoogleMaps 10/05/2016 Networking is blocked

mailR 10/03/2016 Networking is blocked

RevoScaleR 8/30/2016 ships only with Microsoft R Server

Next steps
For more information about R in Power BI, take a look at the following articles:
Creating R visuals in the Power BI service
Create Power BI visuals using R
Running R scripts in Power BI Desktop
Using R in Query Editor
 Enter data directly into Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

With Power BI Desktop, you can enter data directly and use that data in your reports and visualizations. For
example, you can copy portions of a workbook or web page, then paste it into Power BI Desktop.
To enter data directly into Power BI Desktop in the form of a new table, select Enter Data from the Home
ribbon.

Power BI Desktop may attempt to make minor transformations on the data, if appropriate, just like it does when
you load data from any source. For example, in the following case it promoted the first row of data to headers.

If you want to shape the data you entered or pasted, select Edit to open Quer y Editor . You can shape and
transform the data before bringing it into Power BI Desktop. Select Load to import the data as it appears.
When you select Load , Power BI Desktop creates a new table from your data, and makes it available in the
Fields pane. In the following image, Power BI Desktop shows my new table, called Table1, and the two fields
within that table that were created.

And that’s it. It's that easy to enter data into Power BI Desktop.
You're now ready to use the data in Power BI Desktop. You can create visuals, reports, or interact with any other
data you might want to connect with and import, such as Excel workbooks, databases, or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data sources in Power BI Desktop
Shape and combine data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
 Connect to Excel workbooks in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

Connecting to an Excel workbook from Power BI Desktop is straightforward, and this article walks you through
the steps.
In Power BI Desktop, select Get Data > Excel from the Home ribbon.

Select your workbook from the Open dialog that appears.

Power BI Desktop presents the tables on other data elements from the workbook in the Navigator window.
When you select a table in the left pane, a preview of the data appears in the right pane.

You can select the Load button to import the data, or if you want to edit the data using Quer y Editor before
bringing it into Power BI Desktop, select the Edit button.
When you load the data, Power BI Desktop displays the Load window and displays the activity associated with
loading the data.

When complete, Power BI Desktop displays the tables and fields it imported from your Excel workbook in the
Fields pane, on the right side of the Desktop.
And that’s it!
You’re now ready to use the imported data from your Excel workbook in Power BI Desktop to create visuals,
reports, or interact with any other data you might want to connect with and import, such as other Excel
workbooks, databases, or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to SSAS multidimensional models in Power
BI Desktop
9/9/2020 • 4 minutes to read • Edit Online

With Power BI Desktop, you can access SSAS multidimensional models, commonly referred to as SSAS MD.
To connect to an SSAS MD database, select Get Data , choose Database > SQL Ser ver Analysis Ser vices
database , and then select Connect :

The Power BI service and Power BI Desktop both support SSAS multidimensional models in live connection mode.
You can publish and upload reports that use SSAS Multidimensional models in live mode to the Power BI
service.

Capabilities and features of SSAS MD

The following sections describe features and capabilities of Power BI and SSAS MD connections.
Tabular metadata of multidimensional models
The following table shows the correspondence between multidimensional objects and the tabular metadata that's
returned to Power BI Desktop. Power BI queries the model for tabular metadata. Based on the returned metadata,
Power BI Desktop runs appropriate DAX queries against SSAS when you create a visualization (such as a table,
matrix, chart, or slicer).

B ISM - M ULT IDIM EN T IO N A L O B JEC T TA B UL A R M ETA DATA

Cube Model
 B ISM - M ULT IDIM EN T IO N A L O B JEC T TA B UL A R M ETA DATA

Cube dimension Table

Dimension attributes (keys), name Columns

Measure group Table

Measure Measure

Measures without associated measure group Within table called Measures

Measure group -> Cube dimension relationship Relationship

Perspective Perspective

KPI KPI

User/parent-child hierarchies Hierarchies

Measures, measure groups, and KPIs

Measure groups in a multidimensional cube are exposed as tables with a sigma (∑) beside them in the Fields pane.
Calculated measures without an associated measure group are grouped under a special table called Measures in
the tabular metadata.
To help simplify complex models in a multidimensional model, you can define a set of measures or KPIs in a cube to
be located within a display folder. Power BI recognizes display folders in tabular metadata, and it shows measures
and KPIs within the display folders. KPIs in multidimensional databases support Value, Goal, Status Graphic, and
Trend Graphic.
Dimension attribute type
Multidimensional models also support associating dimension attributes with specific dimension attribute types. For
example, a Geography dimension where the City, State-Province, Country, and Postal Code dimension attributes
have appropriate geography types associated with them are exposed in the tabular metadata. Power BI recognizes
the metadata, enabling you to create map visualizations. You'll recognize these associations by the map icon next to
the element in the Field pane in Power BI.
Power BI can also render images when you provide a field that contains URLs (uniform resource locators) of the
images. You may specify these fields as ImageURL types in SQL Server Data Tools (or then in Power BI). Its type
information is then provided to Power BI in the tabular metadata. Power BI can then retrieve those images from the
URL and display them in visuals.
Parent-child hierarchies
Multidimensional models support parent-child hierarchies, which are presented as a hierarchy in the tabular
metadata. Each level of the parent-child hierarchy is exposed as a hidden column in the tabular metadata. The key
attribute of the parent-child dimension isn't exposed in the tabular metadata.
Dimension calculated members
Multidimensional models support creation of various types of calculated members. The two most common types of
calculated members are:
Calculated members on attribute hierarchies that aren't siblings of All
Calculated members on user hierarchies
Multidimensional models expose calculated members on attribute hierarchies as values of a column. You have a
few additional options and constraints if you expose this type of calculated member:
A dimension attribute can have an optional UnknownMember.
An attribute containing calculated members can't be the key attribute of the dimension unless it's the only
attribute of the dimension.
An attribute containing calculated members can't be a parent-child attribute.
The calculated members of user hierarchies aren't exposed in Power BI. You can instead connect to a cube that
contains calculated members on user hierarchies. However, you'll be unable to see calculated members if they don't
meet the constraints that we mentioned in the previous bulleted list.
Security
Multidimensional models support dimension and cell level security by way of roles. When you connect to a cube
with Power BI, you're authenticated and evaluated for appropriate permissions. If a user has dimension security
applied, the respective dimension members aren't seen by the user in Power BI. However, when a user has defined a
cell security permission where certain cells are restricted, that user can't connect to the cube using Power BI.

Considerations and limitations

There are certain limitations to using SSAS MD:
Only enterprise and BI editions of SQL Server 2014 support live connections. For the standard edition of
SQL Server, SQL Server 2016 or later is required for live connections.
Actions and named sets aren't exposed to Power BI. To create visuals and reports, you can still connect to
cubes that also contain actions or named sets.
When Power BI displays metadata for an SSAS model, occasionally you can't retrieve data from the model.
This scenario can occur if you've installed the 32-bit version of the MSOLAP provider, but not the 64-bit
version. Installing the 64-bit version may resolve the issue.
You can't create report level measures when authoring a report that is connected live to an SSAS
multidimensional model. The only measures that are available are measures defined in the MD model.

Supported features of SSAS MD in Power BI Desktop

Consumption of the following elements is supported in this release of SSAS MD. For more information about these
features, see Understanding power view for multidimensional models.
Default members
Dimension attributes
Dimension attribute types
Dimension calculated members, which:
must be a single real member when the dimension has more than one attribute;
can't be the key attribute of the dimension unless it's the only attribute; and
can't be a parent-child attribute.
Dimension security
Display folders
Hierarchies
ImageUrls
KPIs
KPI trends
 Measures (with or without measure groups)
Measures as variant

Troubleshooting
The following list describes all known issues when connecting to SQL Server Analysis Services (SSAS).
Error : Couldn't load model schema - This error usually occurs when the user connecting to Analysis
Services doesn't have access to database/cube.
 Connect to CSV files in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

Connecting to a comma-separated value (CSV) file from Power BI Desktop is a lot like connecting to an Excel
workbook. Both are easy, and this article steps you through how to connect to any CSV file to which you have
access.
To start with, from Power BI Desktop select Get Data > CSV from the Home ribbon.

Select your CSV file from the Open dialog that appears.
When you select Open , Power BI Desktop accesses the file and determines certain file attributes, such as the file
origin, delimiter type, and how many rows should be used to detect the data types in the file.
These file attributes and options are shown in the drop-down selections at the top of the CSV impor t dialog
window, shown below. You can change any of these detected settings manually, by choosing another option from
any of the drop-down selectors.

When you’re satisfied with the selections, you can select Load to import the file into Power BI Desktop, or you can
select Edit to open Quer y Editor and further shape or transform the data before importing it.
Once you load the data into Power BI Desktop, you see the table and its columns (which are presented as Fields in
Power BI Desktop) in the Fields pane, along the right of the Report view in Power BI Desktop.
That’s all you have to do – the data from your CSV file is now in Power BI Desktop.
You can use that data in Power BI Desktop to create visuals, reports, or interact with any other data you might want
to connect with and import, such as Excel workbooks, databases, or any other data source.

IMPORTANT
When you import a CSV file, Power BI Desktop generates a columns=x (where x is the number of columns in the CSV file
during initial import) as a step in Power Query Editor. If you subsequently add more columns and the data source is set to
refresh, any columns beyond the initial x count of columns are not refreshed.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources,
check out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to a Google BigQuery database in Power BI
Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a Google BigQuer y database and use the underlying data just like any
other data source in Power BI Desktop.

Connect to Google BigQuery

To connect to a Google BigQuer y database select Get Data from the Home ribbon in Power BI Desktop. Select
Database from the categories on the left, and you see Google BigQuer y .

In the Google BigQuer y window that appears, sign in to your Google BigQuery account and select Connect .
When you're signed in, you see the following window indicated you've been authenticated.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop .
Considerations and Limitations
There are a few limits and considerations to keep in mind with the Google BigQuer y connector:
The Google BigQuery connector is available in Power BI Desktop and in the Power BI service. In the Power BI
service, the connector can be accessed using the Cloud-to-Cloud connection from Power BI to Google BigQuery.
You can use Power BI with the Google BigQuery Billing Project . By default, Power BI uses the first project from the
list returned for the user. To customize the behavior of the Billing Project when using it with Power BI, take the
following steps:
Specifying the following option in the underlying M in the Source step, which can be customized by using
Power Quer y Editor in Power BI Desktop:
Source = GoogleBigQuery.Database([BillingProject="Include-Billing-Project-Id-Here"])

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to an Impala database in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to an Impala database and use the underlying data just like you can with any
other data source in Power BI Desktop.

Connect to an Impala database

To connect to an Impala database, take the following steps:
1. Select Get Data from the Home ribbon in Power BI Desktop.
2. Select Database from the categories on the left. Then you see Impala .

3. In the Impala window that appears, type or paste the name of your Impala server into the box. Then select
OK . You can Impor t data directly into Power BI or you can use DirectQuer y . Learn more about using
DirectQuery.
4. When prompted, enter your credentials or connect anonymously. The Impala connector supports
Anonymous, Basic (user name + password), and Windows authentication.

NOTE
After you put in your user name and password for a particular Impala server, Power BI Desktop uses those same
credentials in subsequent connection attempts. You can modify those credentials by going to File > Options and
settings > Data source settings .

5. After you connect, a Navigator window appears and displays the data that's available on the server. Choose
elements from this data to import and use in Power BI Desktop .
Considerations and limitations
There are a few limitations and considerations to keep in mind with the Impala connector:
The Impala connector is supported on the on-premises data gateway, using any of the three supported
authentication mechanisms.

Next steps
There are many different data sources that you can connect to by using Power BI Desktop. For more information
about data sources, check out the following resources:
What is Power BI Desktop?
Data sources in Power BI Desktop
Shape and combine data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to OData feeds in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to an OData feed and use the underlying data just like any other data source
in Power BI Desktop.
To connect to an OData feed, select Get Data > OData Feed from the Home ribbon in Power BI Desktop.

In the OData Feed window that appears, type or paste your OData feed URL into the box, and select OK .

Power BI Desktop connects to the OData feed, and displays the available tables and other data elements in the
Navigator window. When you select an element, the right pane of the Navigator window displays a preview of
the data. You can select as many tables as you want to import. The Navigator window shows a preview of the
currently selected table.
You can choose the Edit button, which launches Quer y Editor , where you can shape and transform the data from
the OData feed before importing it into Power BI Desktop. Or you can select the Load button, and import all of the
data elements you selected in the left pane.
When we select Load , Power BI Desktop imports the selected items, and displays a Load window of the import
progress.

Once complete, Power BI Desktop makes the selected tables and other data elements available in the Fields pane,
found on the right side of the Reports view in Power BI Desktop.
And that’s it!
You’re now ready to use the imported data from the OData feed in Power BI Desktop to create visuals, reports, or
interact with any other data you might want to connect with and import, such as other Excel workbooks, databases,
or any other data source.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to an Amazon Redshift database in Power BI
Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop , you can connect to an Amazon Redshift database and use the underlying data just like any
other data source in Power BI Desktop.

Connect to an Amazon Redshift database

To connect to an Amazon Redshift database, select Get Data from the Home ribbon in Power BI Desktop. Select
Database from the categories on the left, and you see Amazon Redshift .

In the Amazon Redshift window that appears, type or paste the name of your Amazon Redshift server and
database into the box. As part of the Server field, users can specify a port in the following format: ServerURL:Port
When prompted, put in your username and password. You should use the server name that precisely matches the
SSL certificate to avoid errors.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop .

Once you make selections from the Navigator window, you can either Load or Edit the data.
 If you choose to Load data, you'll be prompted to use either Import or DirectQuery mode to load the data. For
more information, check out this article that explains DirectQuery.
If you select to Edit the data, Quer y Editor appears where you can apply all sorts of transformations and filters
to the data, many of which are applied to the underlying Amazon Redshift database itself (if supported).

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to webpages from Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

You can connect to a webpage and import its data into Power BI Desktop, to use in your visuals and in your data
models.
In Power BI Desktop, select Get Data > Web from the Home ribbon.

A dialog appears, asking for the URL of the web page from which you want to import data.

Once you’ve typed in (or pasted) the URL, select OK . Power BI Desktop connects to that page, then presents the
page’s available data in the Navigator window. When you select one of the available data elements, such as a table
of the entire page, the Navigator window displays a preview of that data on the right side of the window.
You can choose the Edit button, which launches Quer y Editor , where you can shape and transform the data on
that Web page before importing it into Power BI Desktop. Or you can select the Load button, and import all of the
data elements you selected in the left pane.
When we select Load , Power BI Desktop imports the selected items, and makes them available in the Fields pane,
found on the right side of the Reports view in Power BI Desktop.
That’s all there is to connecting to a web page and bringing its data into Power BI Desktop.
From there, you can drag those fields onto the Report canvas and create all the visualizations you want. You can
also use the data from that Web page just like you would any other data – you can shape it, you can create
relationships between it and other data sources in your model, and otherwise do what you’d like to create the
Power BI report you want.
To see connecting to a Web page in more depth and action, take a look at the Power BI Desktop Getting Started
Guide.

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Connect to CSV files in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to a Snowflake computing warehouse in
Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

In Power BI Desktop, you can connect to a Snowflake computing warehouse and use the underlying data just like
any other data source in Power BI Desktop.

Connect to a Snowflake computing warehouse

To connect to a Snowflake computing warehouse, select Get Data from the Home ribbon in Power BI Desktop.
Select Database from the categories on the left, and you see Snowflake .

In the Snowflake window that appears, type or paste the name of your Snowflake computing warehouse into the
box and select OK . Note that you can choose to Impor t data directly into Power BI, or you can use DirectQuer y .
You can learn more about using DirectQuery. Please note that AAD SSO only supports DirectQuery.
When prompted, put in your username and password.

NOTE
Once you put in your username and password for a particular Snowflake server, Power BI Desktop uses those same
credentials in subsequent connection attempts. You can modify those credentials by going to File > Options and settings
> Data source settings .

If you want to use the Microsoft account option, the Snowflake AAD integration must be configured on the
Snowflake side. To do this, read the Getting Started section of the Snowflake documentation on the topic.

Once you successfully connect, a Navigator window appears and displays the data available on the server, from
which you can select one or multiple elements to import and use in Power BI Desktop .
You can Load the selected table, which brings the entire table into Power BI Desktop , or you can Edit the query,
which opens Quer y Editor so you can filter and refine the set of data you want to use, and then load that refined
set of data into Power BI Desktop .

Next steps
There are all sorts of data you can connect to using Power BI Desktop. For more information on data sources, check
out the following resources:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Snowflake in Power BI Service
9/9/2020 • 3 minutes to read • Edit Online

Introduction
Connecting to Snowflake in the Power BI service differs from other connectors in only one way. Snowflake has an
additional capability for Azure Active Directory (AAD), with an option for SSO. Parts of the integration require
different administrative roles across Snowflake, Power BI, and Azure. You can also choose to enable AAD
authentication without using SSO. Basic authentication works similarly to other connectors in the service.
To configure AAD integration and optionally enable SSO, follow the steps in this article:
If you're the Snowflake admin, read the Power BI SSO to Snowflake - Getting Started article in the Snowflake
documentation.
If you're a Power BI admin, reference Power BI Service configuration - Admin Portal to learn how to enable SSO.
If you're a Power BI dataset creator, reference Power BI Service configuration - Configuring a dataset with AAD to
learn how to enable SSO.

Power BI Service configuration

Admin portal
To enable SSO, a global admin has to turn on the setting in the Power BI Admin portal. This setting approves
sending AAD credentials to Snowflake for authentication for the entire organization. Follow these steps to enable
SSO:
1. Sign in to Power BI using global admin credentials.
2. Select Settings from the page header menu, then select Admin por tal .
3. Select Tenant settings , then scroll to locate Integration settings .
4. Expand Snowflake SSO , toggle the setting to Enabled , then select Apply .
This step is required to consent to sending your AAD token to the Snowflake servers. After you enable the setting, it
may take up to an hour for it to take effect.
After SSO is enabled you can use reports with SSO.
Configuring a Dataset with AAD
After a report that is based on the Snowflake connector is published to the Power BI service, the dataset creator has
to update settings for the appropriate workspace so that it will use SSO.
Because of the way that Power BI works, SSO will only work when no data sources are run through the on-premises
data gateway. Limitations are listed below:
If you're using only a Snowflake source in your data model, then you can use SSO if you choose not to use the
on-premises data gateway.
If you're using a Snowflake source and another source, then you can use SSO if none of the sources use the on-
premises data gateway.
If you're using a Snowflake source through the on-premises data gateway, AAD credentials aren't currently
supported. This consideration might be relevant in case you're trying to access a VNet from a single IP with the
gateway installed on it, rather than from the entire Power BI IP range.
If you're using a Snowflake source and another source that requires a gateway, you need to use Snowflake
through the on-premises data gateway as well. You won't be able to use SSO in this case.
Learn more about how to use the on-premises data gateway, in What is an on-premises data gateway?
If you aren't using the gateway, you're all set. When you have Snowflake credentials configured on your on-
premises data gateway, but are only using that data source in your model, you can click the toggle on the Dataset
settings page to turn off the gateway for that data model.
To turn on SSO for a dataset, follow these steps:
1. Sign in to Power BI using dataset creator credentials.
2. Select the appropriate workspace, then choose Settings from the more options menu that's located next to
the dataset name.

3. Select Data source credentials and sign in. The dataset can be signed into Snowflake with Basic or
OAuth2 (AAD) credentials. if you use AAD, you can enable SSO in the next step.
4. Select the option End users use their own OAuth2 credentials when accessing this data source via
DirectQuer y . This setting will enable AAD SSO. Whether the first user signs in with Basic authentication or
OAuth2 (AAD), the AAD credentials are what will be sent for SSO.
After these steps are done, users should automatically use their AAD authentication to connect to data from that
Snowflake dataset.
If you choose not to enable SSO, then users refreshing the report will use the credentials of the user who signed in,
like most other Power BI reports.
Troubleshooting
If you run into any issues with the integration, refer to the Snowflake troubleshooting guide.

Next steps
Data sources for the Power BI service
Connect to datasets in the Power BI service from Power BI desktop
Connect to a Snowflake computing warehouse
 Create visuals and reports with the Azure Cost
Management connector in Power BI Desktop
9/9/2020 • 3 minutes to read • Edit Online

You can use the Azure Cost Management connector for Power BI Desktop to make powerful, customized
visualizations and reports that help you better understand your Azure spend. The Azure Cost Management
connector currently supports customers with a Microsoft Customer Agreement or an Enterprise Agreement (EA).
The Azure Cost Management connector uses OAuth 2.0 for authentication with Azure and identifies users who are
going to use the connector. Tokens generated in this process are valid for a specific period. Power BI preserves the
token for the next login. OAuth 2.0, is a standard for the process that goes on behind the scenes to ensure the
secure handling of these permissions. To connect, you must use an Enterprise Administrator account for Enterprise
Agreements, or a Billing account owner for Microsoft Customer Agreements.

NOTE
This connector replaces the previously available Azure Consumption Insights and Azure Cost Management (Beta) connectors.
Any reports created with the previous connector must be recreated using this connector.

Connect using Azure Cost Management

To use the Azure Cost Management connector in Power BI Desktop, take the following steps:
1. In the Home ribbon, select Get Data .
2. Select Azure from the list of data catagories.
3. Select Azure Cost Management .
4. In the dialog that appears, enter either your Billing Profile ID for Microsoft Customer Agreements , or
your Enrollment Number for Enterprise Agreements (EA) .

Connect to a Microsoft Customer Agreement account

To connect with a Microsoft Customer Agreement account, you can get your Billing profile ID from the Azure
portal:
1. In the Azure portal, navigate to Cost Management + Billing .
2. Select your Billing profile.
3. Under Settings in the menu, select Proper ties in the sidebar.
4. Under Billing profile , copy the ID .
5. For Choose Scope , select Billing Profile ID and paste the billing profile ID from the previous step.
6. Enter the number of months and select OK .
7. When prompted, sign in with your Azure user account and password.

Connect to an Enterprise Agreement account

To connect with an Enterprise Agreement (EA) account, you can get your enrollment ID from the Azure portal:
1. In the Azure portal, navigate to Cost Management + Billing .
2. Select your billing account.
3. On the Over view menu, copy the Billing account ID .
4. For Choose Scope , select Enrollment Number and paste the billing account ID from the previous step.
5. Enter the number of months and then select OK .

6. When prompted, sign in with your Azure user account and password.

Data available through the connector

Once you successfully authenticate, a Navigator window appears with the following available data tables:

TA B L E DESC RIP T IO N

Balance summar y Summary of the balance for Enterprise Agreements (EA).

Billing events Event log of new invoices, credit purchases, etc. Microsoft
Customer Agreement only.
 TA B L E DESC RIP T IO N

Budgets Budget details to view actual costs or usage against existing

budget targets.

Charges A month-level summary of Azure usage, Marketplace charges,

and charges billed separately. Microsoft Customer Agreement
only.

Credit lots Azure credit lot purchase details for the provided billing
profile. Microsoft Customer Agreement only.

Pricesheets Applicable meter rates for the provided billing profile or EA

enrollment.

RI charges Charges associated to your Reserved Instances over the last

24 months.

RI recommendations (shared) Reserved Instance purchase recommendations based on all

your subscription usage trends for the last 7, 30 or 60 days.

RI recommendations (single) Reserved Instance purchase recommendations based on your

single subscription usage trends for the last 7, 30 or 60 days.

RI usage details Consumption details for your existing Reserved Instances over
the last month.

RI usage summar y Daily Azure reservation usage percentage.

Usage details A breakdown of consumed quantities and estimated charges

for the given billing profile on EA enrollment.

Usage details amor tized A breakdown of consumed quantities and estimated

amortized charges for the given billing profile on EA
enrollment.

You can select a table to see a preview dialog. You can select one or more tables by selecting the boxes beside their
name and then select Load .
When you select Load , the data is loaded into Power BI Desktop.
When the data you selected is loaded, the data tables and fields are shown in the Fields pane.

Next steps
You can connect to many different data sources using Power BI Desktop. For more information, see the following
articles:
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to Azure Consumption Insights data in
Power BI Desktop
9/9/2020 • 7 minutes to read • Edit Online

You can use Power BI desktop to connect to Azure and get in-depth data about your organization's Azure service
usage. With this data, you can create custom reports and measures to better understand and analyze your Azure
spend.

NOTE
There is limited support for the Microsoft Azure Consumption Insights (Beta). For new functionality, use the Azure Cost
Management connector for Power BI.

Connect with Azure Consumption Insights

Azure Consumption Insights allows you to connect to Azure Enterprise Agreement billing accounts.
In this section, you learn how to get the data you need migrate using the Azure Enterprise Connector. You'll also
find a usage details columns mapping available in the ACI (Azure Consumption Insights) API.
To successfully use the Azure Consumption Insights connector, you need access to the Azure portal Enterprise
features.
To use the Azure Consumption Insights connector in Power BI Desktop :
1. From the Home ribbon, select Get Data .
2. From the categories on the left, select Online Ser vices .
3. Select Microsoft Azure Consumption Insights (Beta) .
4. Select Connect .
In the dialog that appears, enter your Azure Enrollment Number .

You can get your enrollment number from the Azure Enterprise Portal, in the location shown in the
following image:
This connector version only supports enterprise enrollments from https://ea.azure.com. China enrollments aren't
currently supported.
Next, provide your Access key to connect.

Your Access key for enrollment can be found on the Azure Enterprise Portal.

Once you provide your Access key and select Connect , a Navigator window appears and shows nine available
tables:

TA B L E DESC RIP T IO N

Budgets Budget details to view actual costs or usage against existing

budget targets.

MarketPlace Usage-based Azure Marketplace charges.

PriceSheets Applicable rates by meter for an enrollment.

RICharges Charges associated to your Reserved Instances over the last

24 months.

RIRecommendations_Single Reserved Instance purchase recommendations based on your

single subscription usage trends over the last 7, 30, or 60
days.

RIRecommendations_Shared Reserved Instance purchase recommendations based on your

usage trends across all your subscriptions over the last 7, 30
or 60 days.

RIUsage Consumption details for your existing Reserved Instances over

the last month.

Summaries A monthly summary for balances, new purchases, Azure

Marketplace service charges, adjustments, and overage
charges.

UsageDetails A consumed quantities breakdown and estimated enrollment

charges.

You can select a checkbox beside any table to see a preview. You can select one or more tables by checking the box
beside their name, then select Load .
 NOTE
The Summary and PriceSheet tables are only available for the enrollment-level API Key. Also, the data in these tables has, by
default, the current month's data for Usage and PriceSheet. The Summary and MarketPlace tables are not constrained to the
current month.

When you select Load , the data is loaded into Power BI Desktop .

Once the data you selected is loaded, the tables and fields you selected can be seen in the Fields pane.
Using Azure Consumption Insights
To use the Azure Consumption Insights connector, you access to the Azure portal Enterprise features.
Once you successfully load data using the Azure Consumption Insights connector, you can create your own
custom measures and columns using Quer y Editor . You can also create visuals, reports, and dashboards for
sharing in the Power BI ser vice .
With a blank query, you can retrieve a sample Azure custom queries collection. There are two ways you can do this
retrieval:
In Power BI Desktop :
1. Select the Home ribbon
2. Select Get Data > Blank Quer y
Or, in Quer y Editor :
1. Right-click in the left Queries pane
2. Select New Quer y > Blank Quer y from the menu that appears
In the Formula bar , type:

= MicrosoftAzureConsumptionInsights.Contents

The following image shows a samples collection that appears.

When working with reports and creating queries, you can:
To define the number of months starting from the current date, use numberOfMonth
Use a value between one and 36. Represent the number of months, from the current date, you want to
import. We recommend getting no more than 12 months of data. This limit avoids Power BI query
import constraints and data volume thresholds.
To define a period of months in a historical time window, use startBillingDataWindow and
endBillingDataWindow
Don't use numberOfMonth together with startBillingDataWindow or endBillingDataWindow

Migrate from the Azure Enterprise Connector

Some customers created visuals using the Azure Enterprise Connector (Beta). Eventually, it will be replaced with the
Azure Consumption Insights connector. The new connector has features and enhancements that include:
Additional data sources available for Balance Summary and Marketplace Purchases
New and advanced parameters, such as startBillingDataWindow and endBillingDataWindow
Better performance and responsiveness
The next steps show how to transition to the Azure Consumption Insights connector. These steps preserve the
work you've already done in creating custom dashboards or reports.
Step 1: Connect to Azure using the new connector
The first step is use the Azure Consumption Insights connector described in detail earlier in this article. In this
step, select Get Data > Blank Quer y from the Home ribbon in Power BI Desktop .
Step 2: Create a query in Advanced Editor
In Quer y Editor , select Advanced Editor from the Home ribbon's Quer y section. In the Advanced Editor
window that appears, enter this query:

let
enrollmentNumber = "100",
optionalParameters = [ numberOfMonth = 6, dataType="DetailCharges" ],
data = MicrosoftAzureConsumptionInsights.Contents(enrollmentNumber, optionalParameters)
in
data
You'll need to replace the enrollmentNumber value with your enrollment number. You can get your number from
the Azure Enterprise Portal. The numberOfMonth parameter is how many months of data you want going back,
from the current dat. Use zero (0) for the current month.
Once you select Done in the Advanced Editor window, the preview refreshes and data from the specified month
range appears in the table. Select Close & Apply and return.
Step 3: Move measures and custom columns to the new report
Next, you'll need to move any custom columns or measures you created into the new details table. Here are the
steps.
1. Open Notepad (or another text editor).
2. Select the measure you want to move, copy the text from the Formula field, and place it in Notepad.

3. Rename Query1 to the original details table name.

4. To create new table measures and custom columns, right-click on your table, and choose New Measure .
Then, cut and paste your stored measures and columns until they're all done.
Step 4: Relink tables that had relationships
Many dashboards have additional tables that are used for lookup or filtering, such as date tables or tables used for
custom projects. Reestablishing those relationships resolves most remaining issues. Here's how to do it.
In the Modeling tab in Power BI Desktop , select Manage Relationships to bring up a window that lets
you manage relationships within the model. Relink your tables, as needed.
Step 5: Verify your visuals, and adjust field formatting as needed
At this point, most of your original visuals, tables, and drill-downs should be working as expected. Some minor
tweaks may be necessary, however, to precisely format the look and feel. Take a bit of time to look over each of
your dashboards and visuals to ensure they look how you want them.

Using the Azure Consumption and Insights (ACI) API to get

consumption data
Azure also provides the Azure Consumption and Insights (ACI) API . You can create your own custom solutions
to gathering, reporting, and visualizing Azure consumption information using the ACI API.
Mapping names and usage details between the portal, the connector, and the API
The Azure portal columns and details names are similar in the API and the connector, though not always identical.
To help clarify, the following table provides a mapping. Also indicated is whether the column is obsolete. For more
information, and term definitions, see the Azure billing data dictionary.

A C I C O N N EC TO R /
C O N T EN T PA C K O B SO L ET E / P RESEN T F O R
C O L UM N N A M E A C I A P I C O L UM N N A M E EA C O L UM N N A M E B A C K WA RD C O M PAT IB IL IT Y

AccountName accountName Account Name No

AccountId accountId Yes

AccountOwnerId accountOwnerEmail AccountOwnerId No

AdditionalInfo additionalInfo AdditionalInfo No

A C I C O N N EC TO R /
C O N T EN T PA C K O B SO L ET E / P RESEN T F O R
C O L UM N N A M E A C I A P I C O L UM N N A M E EA C O L UM N N A M E B A C K WA RD C O M PAT IB IL IT Y

AdditionalInfold Yes

Consumed Quantity consumedQuantity Consumed Quantity No

Consumed Service consumedService Consumed Service No

ConsumedServiceId consumedServiceId Yes

Cost cost ExtendedCost No

Cost Center costCenter Cost Center No

Date date Date No

Day Day No

DepartmentName departmentName Department Name No

DepartmentID departmentId Yes

Instance ID Yes

InstanceId instanceId Instance ID No

Location Yes

Meter Category meterCategory Meter Category No

Meter ID Yes

Meter Name meterName Meter Name No

Meter Region meterRegion Meter Region No

Meter Sub-Category meterSubCategory Meter Sub-Category No

MeterId meterId Meter ID No

Month Month No

Product product Product No

ProductId productId Yes

Resource Group resourceGroup Resource Group No

Resource Location resourceLocation Resource Location No

ResourceGroupId Yes
 A C I C O N N EC TO R /
C O N T EN T PA C K O B SO L ET E / P RESEN T F O R
C O L UM N N A M E A C I A P I C O L UM N N A M E EA C O L UM N N A M E B A C K WA RD C O M PAT IB IL IT Y

ResourceLocationId resourceLocationId Yes

ResourceRate resourceRate ResourceRate No

ServiceAdministratorId serviceAdministratorId ServiceAdministratorId No

ServiceInfo1 serviceInfo1 ServiceInfo1 No

ServiceInfo1Id Yes

ServiceInfo2 serviceInfo2 ServiceInfo2 No

ServiceInfo2Id Yes

Store Service Identifier storeServiceIdentifier Store Service Identifier No

StoreServiceIdentifierId Yes

Subscription Name subscriptionName Subscription Name No

Tags tags Tags No

TagsId Yes

Unit Of Measure unitOfMeasure Unit Of Measure No

Year Year No

SubscriptionId subscriptionId SubscriptionId Yes

SubscriptionGuid subscriptionGuid SubscriptionGuid No

Next steps
You can connect to many different data sources using Power BI Desktop. For more information, see the following
articles:
Connect to Azure cost management data in Power BI desktop
What is Power BI Desktop?
Data Sources in Power BI Desktop
Shape and Combine Data with Power BI Desktop
Connect to Excel workbooks in Power BI Desktop
Enter data directly into Power BI Desktop
 Connect to SAP HANA databases in Power BI
9/9/2020 • 3 minutes to read • Edit Online

With Power BI Desktop, you can now access SAP HANA databases. To use SAP HANA, you must have the SAP HANA
ODBC driver installed on the local client computer for the Power BI Desktop's SAP HANA data connection to work
properly. You can download the SAP HANA Client tools from SAP Development Tools, which contains the necessary
ODBC driver. Or you can get it from the SAP Software Download Center. In the Software portal, search for the SAP
HANA CLIENT for Windows computers. Since the SAP Software Download Center changes its structure frequently,
more specific guidance for navigating that site isn't available.
To connect to a SAP HANA database, select Get Data , choose Database > SAP HANA Database , and then select
Connect :

When you connect to a SAP HANA database, specify the server name. Then from the dropdown and input box,
specify the port.
In this release, SAP HANA in DirectQuery mode is supported in Power BI Desktop and the Power BI service. You can
publish and upload reports that use SAP HANA in DirectQuery mode to the Power BI service. You can also publish
and upload reports to the Power BI Service when not using SAP HANA in DirectQuery mode.

Supported features for SAP HANA

This release has many capabilities for SAP HANA, as shown in the following list:
The Power BI connector for SAP HANA uses the SAP ODBC driver to provide the best user experience.
SAP HANA supports both DirectQuery and Import options.
Power BI supports HANA information models, such as Analytic and Calculation Views, and has optimized
 navigation.
With SAP HANA, you can also use the direct SQL feature to connect to Row and Column Tables.
Power BI includes Optimized Navigation for HANA Models.
Power BI supports SAP HANA Variables and Input parameters.
Power BI supports HDI-container-based Calculation Views.
Support for HDI-container-based Calculation Views is in public preview in the August 2019 release of
Power BI Desktop. To access your HDI-container-based Calculation Views in Power BI, ensure that the
HANA database users you use with Power BI have permission to access the HDI runtime container
that stores the views you want to access. To grant this access, create a Role that allows access to your
HDI container. Then assign the role to the HANA database user you'll use with Power BI. (This user
must also have permission to read from the system tables in the _SYS_BI schema, as usual.) Consult
the official SAP documentation for detailed instructions on how to create and assign database roles.
This SAP blog post may be a good place to start.
There are currently some limitations for HANA variables attached to HDI-based Calculation Views.
These limitations are because of errors on the HANA side.
First, it isn't possible to apply a HANA variable to a shared column of an HDI-container-based
Calculation View. To fix this limitation, upgrade to HANA 2 version 37.02 and onwards or to HANA 2
version 42 and onwards. Second, multi-entry default values for variables and parameters currently
don't show up in the Power BI UI. An error in SAP HANA causes this limitation, but SAP hasn't
announced a fix yet.

Limitations of SAP HANA

There are also a few limitations to using SAP HANA, shown below:
NVARCHAR strings are truncated to a maximum length of 4000 Unicode characters.
SMALLDECIMAL isn't supported.
VARBINARY isn't supported.
Valid Dates are between 1899/12/30 and 9999/12/31.
SAP HANA refresh with SSO is currently not supported for Excel workbook refreshes at the current time. To
refresh the data in Power BI, you can use a Power BI report with SAP HANA SSO.

Next steps
For more information about DirectQuery and SAP HANA, see the following resources:
DirectQuery and SAP HANA
Use DirectQuery in Power BI
Power BI data sources
Enable encryption for SAP HANA
 Enable encryption for SAP HANA
9/9/2020 • 3 minutes to read • Edit Online

We recommend that you encrypt connections to an SAP HANA server from Power BI Desktop and the Power BI
service. You can enable HANA encryption using both OpenSSL and SAP's proprietary CommonCryptoLib (formerly
known as sapcrypto) library. SAP recommends using CommonCryptoLib, but basic encryption features are
available using either library.
This article provides an overview of enabling encryption using OpenSSL and references some specific areas of the
SAP documentation. We update content and links periodically, but for comprehensive instructions and support,
always refer to the official SAP documentation. If you want to set up encryption using CommonCryptoLib instead
of OpenSSL, see How to Configure TLS/SSL in SAP HANA 2.0 For steps on how to migrate from OpenSSL to
CommonCryptoLib, see SAP Note 2093286 (s-user required).

NOTE
The setup steps for encryption detailed in this article overlap with the setup and configuration steps for SAML SSO. Whether
you choose OpenSSL or CommonCryptoLib as your HANA server's encryption provider, make sure that your choice is
consistent across SAML and encryption configurations.

There are four phases to enabling encryption for SAP HANA using OpenSSL. We cover these phases next. For more
information, see Securing the Communication between SAP HANA Studio and SAP HANA Server through SSL.

Use OpenSSL
Ensure your HANA server is configured to use OpenSSL as its cryptographic provider. Replace the missing path
information below with the server ID (sid) of your HANA server.

Create a certificate signing request

Create an X509 certificate signing request for the HANA server.
1. Using SSH, connect to the Linux machine that the HANA server runs on as <sid>adm.
2. Go to the Home directory _/_usr/sap/<sid>/home.
3. Create a hidden directory with the name _.__ssl_if one does not already exist.
4. Execute the following command:

openssl req -newkey rsa:2048 -days 365 -sha256 -keyout Server\_Key.pem -out Server\_Req.pem -nodes

This command creates a certificate signing request and private key. Once signed, the certificate is valid for a year
(see the -days parameter). When prompted for the common name (CN), enter the fully qualified domain name
(FQDN) of the computer the HANA server is installed on.

Get the certificate signed

Get the certificate signed by a certificate authority (CA) that is trusted by the client(s) you'll use to connect to the
HANA server.
1. If you already have a trusted company CA (represented by CA_Cert.pem and CA_Key.pem in the following
example), sign the certificate request by running the following command:

openssl x509 -req -days 365 -in Server\_Req.pem -sha256 -extfile /etc/ssl/openssl.cnf -extensions
usr\_cert -CA CA\_Cert.pem -CAkey CA\_Key.pem -CAcreateserial -out Server\_Cert.pem

If you don't already have a CA you can use, you can create a root CA yourself by following the steps outlined
in Securing the Communication between SAP HANA Studio and SAP HANA Server through SSL.
2. Create the HANA server certificate chain by combining the server certificate, key, and the CA's certificate
(the key.pem name is the convention for SAP HANA):

cat Server\_Cert.pem Server\_Key.pem CA\_Cert.pem \> key.pem

3. Create a copy of CA_Cert.pem named trust.pem (the trust.pem name is the convention for SAP HANA):

cp CA\_Cert.pem trust.pem

4. Restart the HANA server.

5. Verify the trust relationship between a client and the CA you used to sign the SAP HANA server's certificate.
The client must trust the CA used to sign the HANA server's X509 certificate before an encrypted connection
can be made to the HANA server from the client's machine.
There are various ways to ensure this trust relationship exists using Microsoft Management Console (mmc)
or the command line. You can import the CA's X509 certificate (trust.pem) into the Trusted Root
Cer tification Authorities folder for the user that will establish the connection, or into the same folder for
the client machine itself, if that is desirable.

You must first convert trust.pem into a .crt file before you can import the certificate into the Trusted Root
Certification Authorities folder, for example by executing the following OpenSSL command:

openssl x509 -outform der -in your-cert.pem -out your-cert.crt

 For information about using OpenSSL for the conversion, see the OpenSSL documentation.

Test the connection

Test the connection in Power BI Desktop or the Power BI service.
1. In Power BI Desktop or in the Manage gateways page of the Power BI service, ensure that Validate
ser ver cer tificate is enabled before attempting to establish a connection to your SAP HANA server. For
SSL cr ypto provider , select mscrypto if you've followed the OpenSSL setup steps and commoncrypto if
you've configured that library as your crypto provider. Leave the SSL key store and SSL trust store fields
blank.
Power BI Desktop

Power BI service

2. Verify that you can successfully establish an encrypted connection to the server with the Validate ser ver
cer tificate option enabled, by loading data in Power BI Desktop or refreshing a published report in Power
BI service.
 Connect to Analysis Services tabular data in Power BI
Desktop
9/9/2020 • 5 minutes to read • Edit Online

With Power BI Desktop, there are two ways you can connect to and get data from your SQL Server Analysis
Services tabular models: Explore by using a live connection or select items and import them into Power BI Desktop.
Let’s take a closer look.
Explore by using a live connection : When using a live connection, items in your tabular model or perspective,
like tables, columns, and measures appear in your Power BI Desktop Fields pane list. You can use Power BI
Desktop’s advanced visualization and report tools to explore your tabular model in new, highly interactive ways.
When connecting live, no data from the tabular model is imported into Power BI Desktop. Each time you interact
with a visualization, Power BI Desktop queries the tabular model and calculates the results you see. You’re always
looking at the latest data that is available in the tabular model, either from the last processing time, or from
DirectQuery tables available in the tabular model.
Keep in mind that tabular models are highly secure. Items that appear in Power BI Desktop depend on your
permissions for the tabular model you’re connected to.
When you’ve created dynamic reports in Power BI Desktop, you can share them by publishing to your Power BI site.
When you publish a Power BI Desktop file with a live connection to a tabular model to your Power BI site, an on-
premises data gateway must be installed and configured by an administrator. To learn more, see On-premises data
gateway.
Select items and impor t into Power BI Desktop : When you connect with this option, you can select items like
tables, columns, and measures in your tabular model or perspective and load them into a Power BI Desktop model.
Use Power BI Desktop’s Power Query Editor to further shape what you want and its modeling features to further
model the data. Because no live connection between Power BI Desktop and the tabular model is maintained, you
can then explore your Power BI Desktop model offline or publish to your Power BI site.

To connect to a tabular model

1. In Power BI Desktop, on the Home tab, select Get Data > More > Database .
2. Select SQL Ser ver Analysis Ser vices database , and then select Connect .
3. In the SQL Ser ver Analysis Ser vices database window, enter the Ser ver name, choose a connection
mode, and then select OK .

4. This step in the Navigator window depends on the connection mode you selected:
If you’re connecting live, select a tabular model or perspective.
 If you chose to select items and get data, select a tabular model or perspective, and then select a
particular table or column to load. To shape your data before loading, select Edit Queries to open
Power Query Editor. When you’re ready, select Load to import the data into Power BI Desktop.

Frequently asked questions

Question: Do I need an on-premises data gateway?
Answer : It depends. If you use Power BI Desktop to connect live to a tabular model, but have no intention to
publish to your Power BI site, you don't need a gateway. On the other hand, if you do intend on publishing to your
Power BI site, a data gateway is necessary to ensure secure communication between the Power BI service and your
on-premises Analysis Services server. Be sure to talk to your Analysis Services server administrator before
installing a data gateway.
If you choose to select items and get data, you import tabular model data directly into your Power BI Desktop file,
so no gateway is necessary.
Question: What’s the difference between connecting live to a tabular model from the Power BI service versus
connecting live from Power BI Desktop?
Answer : When connecting live to a tabular model from your site in the Power BI service to an Analysis Services
database on-premises in your organization, an on-premises data gateway is required to secure communications
between them. When connecting live to a tabular model from Power BI Desktop, a gateway isn't required because
the Power BI Desktop and the Analysis Services server you’re connecting to are both running on-premises in your
organization. However, if you publish your Power BI Desktop file to your Power BI site, a gateway is required.
Question: If I created a live connection, can I connect to another data source in the same Power BI Desktop file?
Answer : No. You can't explore live data and connect to another type of data source in the same file. If you’ve
already imported data or connected to a different data source in a Power BI Desktop file, you need to create a new
file to explore live.
Question: If I created a live connection, can I edit the model or query in Power BI Desktop?
Answer : You can create report level measures in the Power BI Desktop, but all other query and modeling features
are disabled when exploring live data.
Question: If I created a live connection, is it secure?
Answer : Yes. Your current Windows credentials are used to connect to the Analysis Services server. You can't use
basic or stored credentials in either the Power BI service or Power BI Desktop when exploring live.
Question: In Navigator, I see a model and a perspective. What’s the difference?
Answer : A perspective is a particular view of a tabular model. It might include only particular tables, columns, or
measures depending on a unique data analysis need. A tabular model always contains at least one perspective,
which could include everything in the model. If you’re unsure which perspective you should select, check with your
administrator.
Question: Are there any features of Analysis Services that change the way Power BI behaves?
Answer : Yes. Depending on the features your Tabular model uses, the experience in Power BI Desktop might
change. Some examples include:
You may see measures in the model grouped together at the top of the Fields pane list rather than in tables
alongside columns. Don't worry, you can still use them as normal, it's just easier to find them this way.
If the tabular model has calculation groups defined, you can use them only in conjunction with model
measures and not with implicit measures you create by adding numeric fields to a visual. The model might
also have had the DiscourageImplicitMeasures flag set manually, which has the same effect. To learn
more, see Calculation groups in Analysis Services.

To change the server name after initial connection

After you create a Power BI Desktop file with an explore live connection, there might be some cases where you want
to switch the connection to a different server. For example, if you created your Power BI Desktop file when
connecting to a development server, and before publishing to the Power BI service, you want to switch the
connection to production server.
To change the server name:
1. Select Edit Queries from the Home tab.
2. In the SQL Ser ver Analysis Ser vices database window, enter the new Ser ver name, and then select OK .

Troubleshooting
The following list describes all known issues when connecting to SQL Server Analysis Services (SSAS) or Azure
Analysis Services:
Error : Couldn't load model schema : This error usually occurs when the user connecting to Analysis Services
doesn't have access to the database/model.
 Use DirectQuery in Power BI Desktop
9/9/2020 • 6 minutes to read • Edit Online

With Power BI Desktop, when you connect to your data source, it's always possible to import a copy of the data
into the Power BI Desktop. For some data sources, an alternative approach is available: connect directly to the
data source using DirectQuery.

Supported data sources

For a full listing of data sources that support DirectQuery, see Data sources supported by DirectQuery.

How to connect using DirectQuery

When you use Get Data to connect to a data source supported by DirectQuery, the connection dialog box lets
you select how you want to connect. For example, in Power BI Desktop, under the Home ribbon, select Get Data
> SQL Ser ver . In the SQL Ser ver Database dialog box, the Data Connectivity mode shows options of
Impor t and DirectQuer y :

Here are the differences between selecting Impor t and DirectQuer y :

Impor t : The selected tables and columns are imported into Power BI Desktop. As you create or interact
with a visualization, Power BI Desktop uses the imported data. To see underlying data changes since the
initial import or the most recent refresh, you must refresh the data, which imports the full dataset again.
DirectQuer y : No data is imported or copied into Power BI Desktop. For relational sources, the selected
tables and columns appear in the Fields list. For multi-dimensional sources like SAP Business Warehouse,
the dimensions and measures of the selected cube appear in the Fields list. As you create or interact with
a visualization, Power BI Desktop queries the underlying data source, so you’re always viewing current
data.
Many data modeling and data transformations are available when using DirectQuery, though with some
limitations. When you create or interact with a visualization, you must query the underlying source. The time
that's needed to refresh the visualization depends on the performance of the underlying data source. When the
data needed to service the request has recently been requested, Power BI Desktop uses recent data to reduce the
required time to show the visualization. If you select Refresh from the Home ribbon, all visualizations are
refreshed with current data.
The Power BI and DirectQuery article describes DirectQuery in detail. For more information about benefits,
limitations, and important considerations when using DirectQuery, see the following sections.

Benefits of using DirectQuery

There are a few benefits to using DirectQuery:
DirectQuery lets you build visualizations over very large datasets, where it would otherwise be unfeasible to
first import all the data with pre-aggregation.
Underlying data changes can require a refresh of data. For some reports, the need to display current data can
require large data transfers, making reimporting data unfeasible. By contrast, DirectQuery reports always use
current data.
The 1-GB dataset limitation doesn't apply to DirectQuery.

Limitations of DirectQuery
There are currently a few limitations to using DirectQuery:
If the Quer y Editor query is overly complex, an error occurs. To remedy the error, either delete the
problematic step in Quer y Editor , or import the data instead of using DirectQuery. For multi-dimensional
sources like SAP Business Warehouse, there's no Quer y Editor .
Time intelligence capabilities are unavailable in DirectQuery. For example, special treatment of date
columns (such as year, quarter, month, or day) isn't supported in DirectQuery mode.
Calculated tables and calculated columns that reference a DirectQuery table from a data source with Single
Sign-on (SSO) authentication are not supported in the Power BI Service.
Limitations are placed on DAX expressions allowed in measures to ensure that queries sent to the
underlying data source have acceptable performance.
There's a one-million-row limit for cloud sources, with on-premises sources limited to a defined payload of
about 4 MB per row (depending on proprietary compression algorithm) or 16MB data size for the entire
visual. Certain limits may be raised when using Premium capacity. The limit doesn't affect aggregations or
calculations used to create the dataset returned using DirectQuery. It only affects the rows returned.
Premium capacities can set maximum row limits, as described in this post.
For example, you can aggregate 10 million rows with your query that runs on the data source. The query
accurately returns the results of that aggregation to Power BI using DirectQuery if the returned Power BI
data is less than 1 million rows. If over 1 million rows are returned from DirectQuery, Power BI returns an
error (unless in Premium capacity, and the row count is under the admin-set limit).

Important considerations when using DirectQuery

The following three points should be taken into consideration when using DirectQuery:
Performance and load : All DirectQuery requests are sent to the source database, so the required visual
refresh time depends on how long that back-end source takes to respond with the results from the query
(or queries). Five seconds or less is the recommended response time (with requested data being returned)
for using DirectQuery for visuals; the maximum recommended time is 30 seconds. Any longer, and the
experience of a user consuming the report becomes unacceptably poor. After a report is published to the
Power BI service, any query that takes longer than a few minutes will time out, and the user will receive an
 error.
Load on the source database should also be considered, based on the number of Power BI users who will
consume the published report. Using Row Level Security (RLS) can have a significant impact as well. A
non-RLS dashboard tile shared by multiple users results in a single query to the database. Using RLS on a
dashboard tile, however, usually means the refresh of a tile requires one query per user, significantly
increasing load on the source database and potentially impacting performance.
Power BI creates queries that are as efficient as possible. Under certain situations, however, the generated
query may not be efficient enough to avoid a refresh that would fail. One example of this situation is when
a generated query retrieves an excessively large number of rows from the back-end data source. In this
case, the following error occurs:

The resultset of a query to external data source has exceeded

This situation can occur with a simple chart that includes a very high cardinality column, with the
aggregation option set to Don’t Summarize . The visual needs to only have columns with a cardinality
below 1 million, or it must apply the appropriate filters.
Security : By default, all users who consume a published report connect to the back-end data source using
the credentials entered after publication to the Power BI service. This process is the same for data that's
imported: all users see the same data, regardless of any security rules defined in the backend source.
Customers who want per-user security implemented with DirectQuery sources should either use RLS or
configure Kerberos-constrained authentication against the source. Kerberos isn't available for all sources.
Learn more about RLS. Learn more about Kerberos in DirectQuery.
Suppor ted features : Some features in Power BI Desktop are unsupported in DirectQuery mode, or they
have limitations. Also, some capabilities in the Power BI service (such as Quick Insights) aren't available for
datasets using DirectQuery. When determining whether to use DirectQuery, you should consider these
feature limitations.

NOTE
When using DirectQuery with an Azure SQL Database and a private IP address, an on-premises gateway is required.

Publish to the Power BI service

Reports created using DirectQuery can be published to the Power BI service.
If the used data source doesn't need the On-premises data gateway (Azure SQL Database , Azure SQL
Data Warehouse , or Redshift ), you must provide credentials before the Power BI service shows the published
report. Follow these instructions to provide the credentials:
1. Sign in to Power BI.
2. In the Power BI service, select the Settings gear icon and choose the Settings menu item.
3. In the Power BI service's Settings page, select the Datasets tab, choose the dataset that uses DirectQuery,
and select Edit credentials .
4. Add the credentials. Otherwise, an error occurs when you open a published report or explore a dataset
that's created with a DirectQuery connection.
To make a data connection for data sources other than Azure SQL Database , Azure SQL Data Warehouse ,
Redshift , or Snowflake Data Warehouse that use DirectQuery, install an On-premises data gateway and
register the data source. For more information, see What is an on-premises data gateway?

Next steps
For more information about DirectQuery, check out the following resources:
Using DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP Business Warehouse (BW)
DirectQuery and SAP HANA
What is an on-premises data gateway?
 Connect to SAP Business Warehouse by using
DirectQuery in Power BI
9/9/2020 • 9 minutes to read • Edit Online

You can connect to SAP Business Warehouse (BW) data sources directly using DirectQuer y . Given the
OLAP/multidimensional nature of SAP BW, there are many important differences between DirectQuery over SAP
BW versus relational sources like SQL Server. These differences are summarized as follows:
In DirectQuer y over relational sources there are a set of queries (as defined in the Get Data or Quer y
Editor dialog) that logically define the data that is available in the field list. This is not the case when
connecting to an OLAP source such as SAP BW. Instead, when connecting to the SAP server using Get Data ,
just the Infocube or BEx Query is selected. Then all the Key Figures and dimensions of the selected
Infocube/BEx Query will be available in the field list.
Similarly, there is no Quer y Editor when connecting to SAP BW. The data source settings (for example, server
name) can be changed by selecting Edit Queries > Data source settings . The settings for any Parameters
can be changed by selecting Edit Queries > Manage Parameters .
Given the unique nature of OLAP sources, there are additional restrictions (for both modeling and
visualizations) that apply, in addition to the normal restrictions imposed for DirectQuery. These restrictions are
described later in this article.
In addition, it is extremely important to understand that there are many features of SAP BW that are not
supported in Power BI, and that because of the nature of the public interface to SAP BW, there are important
cases where the results seen through Power BI will not match those seen when using an SAP tool. These
limitations are described later in this article. These limitations and behavior differences should be carefully
reviewed, to ensure that the results seen through Power BI, as returned by the SAP public interface, are
interpreted correctly.

NOTE
The ability to use DirectQuery over SAP BW was in preview until the March 2018 update to Power BI Desktop. During the
preview, feedback and suggested improvements prompted a change that impacts reports that were created using that
preview version. Now that General Availability (GA) of DirectQuery over SAP BW has released, you must discard any
existing (preview-based) reports using DirectQuery over SAP BW that were created with the pre-GA version. In reports
created with the pre-GA version of DirectQuery over SAP BW, errors will occur with those pre-GA reports upon invoking
Refresh, as a result of attempting to refresh the metadata with any changes to the underlying SAP BW cube. Please re-
create those reports from a blank report, using the GA version of DirectQuery over SAP BW.

Additional Modeling Restrictions

The primary additional modeling restrictions when connecting to SAP BW using DirectQuery in Power BI are the
following:
No suppor t for calculated columns: The ability to create calculated columns is disabled. This also means
that Grouping and Clustering, which create calculated columns, are not available.
Additional limitations for measures: There are additional limitations imposed on the DAX expressions
that can be used in measures, to reflect the level of support offered by SAP BW.
No suppor t for defining relationships: The relationships are inherent in the external SAP source, and
additional relationships cannot be defined in the model.
 No Data View: The Data View normally displays the detail level data in the tables. Given the nature of OLAP
sources like SAP BW, this view is not available over SAP BW.
Column and measure details are fixed: The list of columns and measures seen in the field list are fixed by
the underlying source, and cannot be modified. For example, it is not possible to delete a column, nor change
its datatype (it can, however, be renamed).
Additional limitations in DAX: There are additional limitations on the DAX that can be used in measure
definitions, to reflect limitations in the source. For example, it is not possible to use an aggregate function over
a table.

Additional Visualization Restrictions

The primary additional restrictions in visualizations when connecting to SAP BW using DirectQuery in Power BI
are the following:
No aggregation of columns: It is not possible to change the aggregation for a column on a visual; it is
always Do Not Summarize
Measure filtering is disabled: Measure filtering is disabled to reflect the support offered by SAP BW.
Multi-select and include/exclude: The ability to multi-select data points on a visual is disabled if the points
represent values from more than one column. For example, given a bar chart showing Sales by Country, with
Category on the Legend, it would not be possible to select the point for (USA, Bikes) and (France, Clothes).
Similarly, it would not be possible to select the point for (USA, Bikes) and exclude it from the visual. Both
limitations are imposed to reflect the support offered by SAP BW.

Support for SAP BW features

The following table lists all SAP BW features that are not fully supported, or will behave differently when using
Power BI.

F EAT URE DESC RIP T IO N

Local calculations Local calculations defined in a BEx Query will change the
numbers as displayed through tools like BEx Analyzer.
However, they are not reflected in the numbers returned
from SAP, through the public MDX interface.

As such, the numbers seen in a Power BI visual will

not necessarily match those for a corresponding
visual in an SAP tool.

For example, when connecting to a query cube from a BEx

query that sets the aggregation to be Cumulated (i.e.
running sum), Power BI would get back the base numbers,
ignoring that setting. An analyst could certainly then apply a
running sum calculation locally in Power BI, but would need
to exercise caution in how the numbers are interpreted if this
is not done.
F EAT URE DESC RIP T IO N

Aggregations In some cases (particularly when dealing with multiple

currencies), the aggregate numbers returned by the SAP
public interface do not match those shown by SAP tools.

As such, the numbers seen in a Power BI visual will

not necessarily match those for a corresponding
visual in an SAP tool.

For example, totals over different currencies would show as

"*" in BEx Analyzer, but the total would get returned by the
SAP public interface, without any information that such an
aggregate number is meaningless. Thus the number
(aggregating, say, $, EUR, and AUD) would get displayed by
Power BI.

Currency formatting Any currency formatting (for example, $2,300 or 4000 AUD)
is not reflected in Power BI.

Units of measure Units of measure (for example, 230 KG) are not reflected in
Power BI.

Key versus text (short, medium, long) For an SAP BW characteristic like CostCenter, the field list will
show a single column Cost Center. Using that column will
display the default text. By showing hidden fields, it will also
be possible to see the unique name column (that returns the
unique name assigned by SAP BW, and is the basis of
uniqueness).

The key and other text fields are not available.

Multiple hierarchies of a characteristic In SAP , a characteristic can have multiple hierarchies. Then in
tools like BEx Analyzer, when a characteristic is included in a
query, the user can select the hierarchy to use.

In Power BI , the various hierarchies can be seen in the field

list as different hierarchies on the same dimension. However,
selecting multiple levels from two different hierarchies on the
same dimension will result in empty data being returned by
SAP.

Treatment of ragged hierarchies

F EAT URE DESC RIP T IO N

Scaling factor/reverse sign In SAP, a key figure can have a scaling factor (for example,
1000) defined as a formatting option, meaning that all
display will be scaled by that factor.

It can similarly have a property set that reverses the sign.

Use of such a key figure in Power BI (in a visual, or as part of
a calculation) will result in the unscaled number being used
(and the sign is not reversed). The underlying scaling factor is
not available. In Power BI visuals, the scale units shown on
the axis (K,M,B) can be controlled as part of the visual
formatting.

Hierarchies where levels appear/disappear dynamically Initially when connecting to SAP BW, the information on the
levels of a hierarchy will be retrieved, resulting in a set of
fields in the field list. This is cached, and if the set of levels
changes, then the set of fields do not change until Refresh is
invoked.

This is only possible in Power BI Desktop . Such Refresh to

reflect changes to the levels cannot be invoked in the Power
BI service after Publish.

Default filter A BEx query can include Default Filters, which will be applied
automatically by SAP BEx Analyzer. These are not exposed,
and hence the equivalent usage in Power BI will not apply the
same filters by default.

Hidden Key figures A BEx query can control visibility of Key Figures, and those
that are hidden will not appear in SAP BEx Analyzer. This is
not reflected through the public API, and hence such hidden
key figures will still appear in the field list. However, they can
then be hidden within Power BI.

Numeric formatting Any numeric formatting (number of decimal positions,

decimal point, etc.) will not automatically be reflected in
Power BI. However, it is possible to then control such
formatting within Power BI.

Hierarchy versioning SAP BW allows different versions of a hierarchy to be

maintained, for example, the cost center hierarchy in 2007
versus 2008. Only the latest version will be available in Power
BI, as information on versions is not exposed by the public
API.

Time dependent hierarchies When using Power BI, time dependent hierarchies are
evaluated at the current date.

Currency conversion SAP BW supports currency conversion, based on rates held in

the cube. Such capabilities are not exposed by the public API,
and are therefore not available in Power BI.

Sort Order The sort order (by Text, or by Key) for a characteristic can be
defined in SAP. This sort order is not reflected in Power BI. For
example, months might appear as “April”, “Aug”, and so on.

It is not possible to change this sort order in Power BI.

 F EAT URE DESC RIP T IO N

Technical names In Get Data , the characteristic/measure names (descriptions)

and technical names can both be seen. The field list will
contain just the characteristic/measure names (descriptions).

Attributes It is not possible to access the attributes of a characteristic

within Power BI.

End user language setting The locale used to connect to SAP BW is set as part of the
connection details, and does not reflect the locale of the final
report consumer.

Text Variables SAP BW allows field names to contain placeholders for

variables (for example, "$YEAR$ Actuals") that would then get
replaced by the selected value. For example, the field appears
as "2016 Actuals" in BEx tools, if the year 2016 were selected
for the variable.

The column name in Power BI will not be changed depending

on the variable value, and therefore would appear as
"$YEAR$ Actuals". However, the column name can then be
changed in Power BI.

Customer Exit Variables Customer Exit variables are not exposed by the public API,
and are therefore not supported by Power BI.

Characteristic Structures Any Characteristic structures in the underlying SAP BW

source will result in an ‘explosion’ of measures being exposed
in Power BI. For example, with two measures Sales and Costs,
and a characteristic structure containing Budget and Actual,
four measures will be exposed: Sales.Budget, Sales.Actual,
Costs.Budget, Costs.Actual.

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
Data Sources supported by DirectQuery
DirectQuery and SAP HANA
 Connect to SAP HANA data sources by using
DirectQuery in Power BI
9/9/2020 • 12 minutes to read • Edit Online

You can connect to SAP HANA data sources directly using DirectQuer y . There are two options when
connecting to SAP HANA:
Treat SAP HANA as a multi-dimensional source (default): In this case, the behavior will be similar
to when Power BI connects to other multi-dimensional sources like SAP Business Warehouse, or Analysis
Services. When connecting to SAP HANA using this setting, a single analytic or calculation view is selected
and all the measures, hierarchies and attributes of that view will be available in the field list. As visuals are
created, the aggregate data will always be retrieved from SAP HANA. This is the recommended approach,
and is the default for new DirectQuery reports over SAP HANA.
Treat SAP HANA as a relational source: In this case, Power BI treats SAP HANA as a relational source.
This offers greater flexibility. Care must be taken with this approach to ensure that measures are
aggregated as expected, and to avoid performance issues.
The connection approach is determined by a global tool option, which is set by selecting File > Options and
settings and then Options > DirectQuer y , then selecting the option Treat SAP HANA as a relational
source , as shown in the following image.
The option to treat SAP HANA as a relational source controls the approach used for any new report using
DirectQuery over SAP HANA. It has no effect on any existing SAP HANA connections in the current report, nor on
connections in any other reports that are opened. So if the option is currently unchecked, then upon adding a
new connection to SAP HANA using Get Data , that connection will be made treating SAP HANA as a multi-
dimensional source. However, if a different report is opened that also connects to SAP HANA, then that report
will continue to behave according to the option that was set at the time it was created, which means that any
reports connecting to SAP HANA that were created prior to February 2018 will continue to treat SAP HANA as a
relational source.
The two approaches constitute different behavior, and it's not possible to switch an existing report from one
approach to the other.
Let's look at more detail about each of these two approaches, in turn.

Treat SAP HANA as a multi-dimensional source (default)

All new connections to SAP HANA use this connection method by default, treating SAP HANA as a multi-
dimensional source. In order to treat a connection to SAP HANA as a relational source, you must select File >
Options and settings > Options , then check the box under Direct Quer y > Treat SAP HANA as a
relational source . While this feature is in Preview , reports created using the multi-dimensional approach
cannot be published to the Power BI service, and doing so will result in errors when the report is opened within
the Power BI service.
When connecting to SAP HANA as a multi-dimensional source, the following considerations apply:
In the Get Data Navigator , a single SAP HANA view can be selected. It is not possible to select individual
measures or attributes. There is no query defined at the time of connecting, which is different from
importing data or when using DirectQuery while treating SAP HANA as a relational source. This also
means that it's not possible to directly use an SAP HANA SQL query when selecting this connection
method.
All the measures, hierarchies, and attributes of the selected view will be displayed in the field list.
As a measure is used in a visual, SAP HANA will be queried to retrieve the measure value at the level of
aggregation necessary for the visual. So when dealing with non-additive measures (counters, ratios, and
so on) all aggregations are performed by SAP HANA, and no further aggregation is performed by Power
BI.
To ensure the correct aggregate values can always be obtained from SAP HANA, certain restrictions must
be imposed. For example, it's not possible to add calculated columns, or to combine data from multiple
SAP HANA views within the same report.
Treating SAP HANA as a multi-dimensional source does not offer the greater flexibility provided by the
alternative relational approach, but it is simpler, and ensures correct aggregate values when dealing with more
complex SAP HANA measures, and generally results in higher performance.
The Field list will include all measures, attributes, and hierarchies from the SAP HANA view. Note the following
behaviors that apply when using this connection method:
Any attribute that is included in at least one hierarchy will be hidden by default. However, they can be seen
if required by selecting View hidden from the context menu on the field list. From the same context
menu they can be made visible, if required.
In SAP HANA, an attribute can be defined to use another attribute as its label. For example, Product (with
values 1,2,3, and so on) could use ProductName (with values Bike, Shirt, Gloves, and so on) as its label. In
this case, a single field Product will be shown in the field list, whose values will be the labels Bike, Shirt,
Gloves, and so on, but which will be sorted by, and with uniqueness determined by, the key values 1,2,3. A
 hidden column Product.Key is also created, allowing access to the underlying key values if required.
Any variables defined in the underlying SAP HANA view will be displayed at the time of connecting, and the
necessary values can be entered. Those values can subsequently be changed by selecting Edit Queries from the
ribbon, and then Manage Parameters from the drop-down menu displayed.
The modeling operations allowed are more restrictive than in the general case when using DirectQuery, given
the need to ensure that correct aggregate data can always be obtained from SAP HANA. However, it's still
possible to make many additions and changes, including defining measures, renaming and hiding fields, and
defining display formats. All such changes will be preserved on refresh, and any non-conflicting changes made
to the SAP HANA view will be applied.
Additional modeling restrictions
The primary additional modeling restrictions when connecting to SAP HANA using DirectQuery (treat as multi-
dimensional source) are the following:
No suppor t for calculated columns: The ability to create calculated columns is disabled. This also means
that Grouping and Clustering, which create calculated columns, are not available.
Additional limitations for measures: There are additional limitations imposed on the DAX expressions
that can be used in measures, to reflect the level of support offered by SAP HANA.
No suppor t for defining relationships: Only a single view can be queried within a report, and as such,
there's no support for defining relationships.
No Data View: The Data View normally displays the detail level data in the tables. Given the nature of
OLAP sources such as SAP HANA, this view is not available over SAP HANA.
Column and measure details are fixed: The list of columns and measures seen in the field list are fixed by
the underlying source, and cannot be modified. For example, it's not possible to delete a column, nor change
its datatype (it can, however, be renamed).
Additional limitations in DAX: There are additional limitations on the DAX that can be used in measure
definitions, to reflect limitations in the source. For example, it's not possible to use an aggregate function over
a table.
Additional visualization restrictions
There are restrictions in visuals when connecting to SAP HANA using DirectQuery (treat as multi-dimensional
source):
No aggregation of columns: It's not possible to change the aggregation for a column on a visual, and it is
always Do Not Summarize.

Treat SAP HANA as a relational source

When choosing to connect to SAP HANA as a relational source, some additional flexibility becomes available. For
example, you can create calculated columns, include data from multiple SAP HANA views, and create
relationships between the resulting tables. However, when using SAP HANA in this manner, it's important to
understand certain aspects of how connections are treated, to ensure the following:
The results are as expected, when the SAP HANA view contains non-additive measures (for example, distinct
counts, or averages, rather than simple sums).
The resulting queries are efficient
It's useful to start by clarifying the behavior of a relational source such as SQL Server, when the query defined in
Get Data or Quer y Editor performs an aggregation. In the example that follows, a query defined in Quer y
Editor returns the average price by ProductID.
If the data is being imported into Power BI (versus using DirectQuery), the following would result:
The data is imported at the level of aggregation defined by the query created in Quer y Editor . For example,
average price by product. This results in a table with the two columns ProductID and AveragePrice that can be
used in visuals.
In a visual, any subsequent aggregation (such as Sum, Average, Min, others) is performed over that imported
data. For example, including AveragePrice on a visual will use the Sum aggregate by default, and would return
the sum over the AveragePrice for each ProductID – which in this example case would be 13.67. The same
applies to any alternative aggregate function (such as Min, Average, so on) used on the visual. For example,
Average of AveragePrice returns the average of 6.66, 4 and 3, which equates to 4.56, and not the average of
Price on the six records in the underlying table, which is 5.17.
If DirectQuer y (over that same relational source) is being used instead of Import, the same semantics apply and
the results would be exactly the same:
Given the same query, logically exactly the same data is presented to the reporting layer – even though
the data is not actually imported.
In a visual, any subsequent aggregation (Sum, Average, Min, others) is again performed over that logical
table from the query. And again, a visual containing Average of AveragePrice returns the same 4.56.
Now let's consider SAP HANA, when the connection is treated as a relational source. Power BI can work with both
Analytic Views and Calculation Views in SAP HANA, both of which can contain measures. Yet today the approach
for SAP HANA follows the same principles as described previously in this section: the query defined in Get Data
or Quer y Editor will determine the data available, and then any subsequent aggregation in a visual is over that
data, and the same applies for both Import and DirectQuery.
However, given the nature of SAP HANA, the query defined in the initial Get Data dialog or Quer y Editor is
always an aggregate query, and generally will include measures where the actual aggregation that will be used is
defined by the SAP HANA view.
The equivalent of the SQL Server example above is that there is a SAP HANA view containing ID, ProductID,
DepotID, and measures including AveragePrice, defined in the view as Average of Price.
If in the Get Data experience, the selections made were for ProductID and the AveragePrice measure, then
that is defining a query over the view, requesting that aggregate data (in the earlier example, for simplicity
pseudo-SQL is used that doesn’t match the exact syntax of SAP HANA SQL). Then any further aggregations
defined in a visual are further aggregating the results of such a query. Again, as described above for SQL Server,
this applies both for the Import and DirectQuery case. In the DirectQuery case, the query from Get Data or
Quer y Editor will be used in a subselect within a single query sent to SAP HANA, and thus it is not actually the
case that all the data would be read in, prior to aggregating further.
All of these considerations and behaviors necessitate the following important considerations when using
DirectQuery over SAP HANA:
Attention must be paid to any further aggregation performed in visuals, whenever the measure in SAP
HANA is non-additive (for example, not a simple Sum, Min, or Max).
In Get Data or Quer y Editor , only the required columns should be included to retrieve the necessary
data, reflecting the fact that the result will be a query, that must be a reasonable query that can be sent to
SAP HANA. For example, if dozens of columns were selected, with the thought that they might be needed
on subsequent visuals, then even for DirectQuery a simple visual will mean the aggregate query used in
the subselect will contain those dozens of columns, which will generally perform poorly.
Let's look at an example. In the following example, selecting five columns (CalendarQuar ter , Color ,
LastName , ProductLine , SalesOrderNumber ) in the Get Data dialog, along with the measure
OrderQuantity, will mean that later creating a simple visual containing the Min OrderQuantity will result in the
following SQL query to SAP HANA. The shaded is the subselect, containing the query from Get Data / Quer y
Editor . If this subselect gives a high cardinality result, then the resulting SAP HANA performance will likely be
poor.

Because of this behavior, we recommend the items selected in Get Data or Quer y Editor be limited to those
items that are needed, while still resulting in a reasonable query for SAP HANA.

Best practices
For both approaches to connecting to SAP HANA, recommendations for using DirectQuery also apply to SAP
HANA, particularly those related to ensuring good performance. These recommendations are described in detail
in the article using DirectQuery in Power BI.

Limitations
The following list describes all SAP HANA features that are not fully supported, or features that behave
differently when using Power BI.
Parent Child Hierarchies - Parent child hierarchies will not be visible in Power BI. This is because Power BI
accesses SAP HANA using the SQL interface, and parent child hierarchies cannot be fully accessed via SQL.
Other hierarchy metadata - The basic structure of hierarchies is displayed in Power BI, however some
hierarchy metadata (such as controlling the behavior of ragged hierarchies) will have no effect. Again, this is
due to the limitations imposed by the SQL interface.
Connection using SSL - You can connect using Import and multi-dimensional with SSL, buy cannot connect
to SAP HANA instances configured to use SSL for the relational connector.
Suppor t for Attribute views - Power BI can connect to Analytic and Calculation views, but cannot connect
directly to Attribute views.
Suppor t for Catalog objects - Power BI cannot connect to Catalog objects.
Change to Variables after publish - You cannot change the values for any SAP HANA variables directly in
the Power BI service, after the report is published.

Known issues
The following list describes all known issues when connecting to SAP HANA (DirectQuery) using Power BI.
SAP HANA issue when quer y for Counters, and other measures - Incorrect data is returned from
SAP HANA if connecting to an Analytical View, and a Counter measure and some other ratio measure, are
included in the same visual. This is covered by SAP Note 2128928 (Unexpected results when query a
Calculated Column and a Counter). The ratio measure will be incorrect in this case.
Multiple Power BI columns from single SAP HANA column - For some calculation views, where a
SAP HANA column is used in more than one hierarchy, SAP HANA exposes this as two separate attributes.
This results in two columns being created in Power BI. Those columns are hidden by default, however, and
all queries involving the hierarchies, or the columns directly, behave correctly.

Next steps
For more information about DirectQuery, check out the following resources:
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
On-premises data gateway
 Apply the Assume Referential Integrity setting in
Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

When connecting to a data source using DirectQuer y , you can use the Assume Referential Integrity selection
to enable running more efficient queries against your data source. This feature has a few requirements of the
underlying data, and it is only available when using DirectQuer y .
Setting Assume referential integrity enables queries on the data source to use INNER JOIN statements rather
than OUTER JOIN , which improves query efficiency.

Requirements for using Assume referential integrity

This is an advanced setting, and is only enabled when connecting to data using DirectQuer y . The following
requirements are necessary for Assume referential integrity to work properly:
Data in the From column in the relationship is never Null or blank
For each value in the From column, there is a corresponding value in the To column
In this context, the From column is the Many in a One-to-Many relationship, or it is the column in the first table in a
One-to-One relationship.

Example of using Assume referential integrity

The following example demonstrates how Assume referential integrity behaves when used in data connections.
The example connects to a data source that includes an Orders table, a Products table, and a Depots table.
1. In the following image that shows the Orders table and the Products table, note that referential integrity
 exists between Orders[ProductID] and Products[ProductID] . The [ProductID] column in the Orders
table is never Null, and every value also appears in the Products table. As such, Assume Referential
Integrity should be set to get more efficient queries (using this setting does not change the values shown in
visuals).

2. In the next image, notice that no referential integrity exists between Orders[DepotID] and
Depots[DepotID] , because the DepotID is Null for some Orders. As such, Assume Referential Integrity
should not be set.

3. Finally, no referential integrity exists between Orders[CustomerID] and Customers[CustID] in the

following tables; the CustomerID contains some values (in this case, CustX) that do not exist in the
Customers table. As such, Assume Referential Integrity should not be set.

Setting Assume referential integrity

To enable this feature, select the checkbox next to Assume Referential Integrity as shown in the following image.
When selected, the setting is validated against the data to ensure there are no Null or mismatched rows. However,
for cases with a very large number of values, the validation is not a guarantee that there are no referential integrity
issues.
In addition, the validation occurs at the time of editing the relationship, and does not reflect any subsequent
changes to the data.

What happens if you incorrectly set Assume referential integrity?

If you set Assume Referential Integrity when there are referential integrity issues in the data, this will not result
in errors. However, it will result in apparent inconsistencies in the data. For example, in the case of the relationship
to the Depots table described above, it would result in the following:
A visual showing the total Order Qty would show a value of 40
A visual showing the total Order Qty by Depot City would show a total value of only 30, because it would not
include Order ID 1, where DepotID is Null.

Next steps
Learn more about DirectQuery
Get more information about Relationships in Power BI
Learn more about Relationship View in Power BI Desktop.
 Use the SAP Business Warehouse connector in Power
BI Desktop
9/9/2020 • 10 minutes to read • Edit Online

With Power BI Desktop, you can access SAP Business Warehouse (BW) data.
For information about how SAP customers can benefit from connecting Power BI to their existing SAP BW systems,
see the Power BI and SAP BW whitepaper. For details about using DirectQuery with SAP BW, see DirectQuery and
SAP Business Warehouse (BW).
Starting with the June 2018 release of Power BI Desktop and generally available in October 2018, you can use the
SAP BW connector with an implementation that has significant improvements in performance and capabilities.
Microsoft developed SAP BW connector Implementation 2.0. Select either version 1 of the SAP BW Connector, or
the Implementation 2.0 SAP Connector. The following sections describe the installation of each version, in turn. You
can choose one or the other connector when connecting to SAP BW from Power BI Desktop.
We suggest you use the Implementation 2.0 SAP Connector whenever possible.

Installation of version 1 of the SAP BW Connector

We recommend using the Implementation 2.0 SAP Connector whenever possible. This section describes installation
of version 1 of the SAP BW Connector.
1. Install the SAP NetWeaver library on your local computer. You can get the SAP NetWeaver library from your
SAP administrator or directly from the SAP Software Download Center. Since the SAP Software Download
Center changes its structure frequently, more specific guidance for navigating that site isn't available. The
SAP NetWeaver library is usually included in the SAP Client Tools installation.
You can search for SAP Note #1025361 to get the download location for the most recent version. Make sure
the architecture for the SAP NetWeaver library (32-bit or 64-bit) matches your Power BI Desktop installation.
Install all files included in the SAP NetWeaver RFC SDK according to the SAP Note.
2. In Power BI Desktop, select Get Data . The Database options include SAP Business Warehouse Application
Server and SAP Business Warehouse Message Server.
Installation of Implementation 2.0 SAP Connector
Implementation 2.0 of the SAP Connector requires the SAP .NET Connector 3.0. Access to the download requires a
valid S-user. Contact your SAP Basis team to get the SAP .NET Connector 3.0.
You can download the SAP .NET Connector 3.0 from SAP.
The connector comes in 32-bit and 64-bit versions. Choose the version that matches your Power BI Desktop
installation. Currently, the website lists two versions for .NET 4.0 framework:
SAP Connector for Microsoft .NET 3.0.22.0 for Windows 32-bit (x86) as zip file (6.896 KB), June 1, 2019
SAP Connector for Microsoft .NET 3.0.22.0 for Windows 64-bit (x64) as zip file (7.180 KB), June 1, 2019
When you install, in Optional setup steps , make sure you select Install assemblies to GAC.
 NOTE
The first version of SAP BW implementation required NetWeaver DLLs. If you're using Implementation 2.0 of the SAP
Connector, and not using the first version, the NetWeaver DLLs are not required.

Version 1 SAP BW Connector features

The version 1 SAP BW Connector in Power BI Desktop lets you import data from your SAP Business Warehouse
Server cubes or use DirectQuery.
To learn more about the SAP BW Connector and how to use it with DirectQuery, see DirectQuery and SAP Business
Warehouse (BW).
When you connect, specify a Ser ver , System Number , and Client ID to establish the connection.

You can also specify two additional Advanced options : Language code , and a custom MDX statement to run
against the specified server.
If you don't specify an MDX statement, the connection setting displays the list of cubes available in the server. You
can drill down and select items from the available cubes, including dimensions and measures. Power BI exposes
queries and cubes exposed by the Open Analysis Interfaces.
When you select one or more items from the server, the Navigator dialog creates a preview of the output table.

The Navigator dialog also provides display options:

 Display Only selected items . By default, Navigator displays all items. This option is useful for verifying the
final set of items selected. An alternative approach to viewing selected items is to select the column names in the
preview area.
Enable data previews . This value is the default. Displays data previews. Disabling data previews reduces the
number of server calls, since it no longer requests data for the previews.
Technical names . SAP BW supports the notion of technical names for objects within a cube. Technical names
allow a cube owner to expose friendly names for cube objects, as opposed to only exposing the physical names
for those objects in the cube.

After selecting all necessary objects, you can decide what to do next by selecting one of the following options:
Select Load to load the entire set of rows for the output table into the Power BI Desktop data model. The
Repor t view opens. You can begin visualizing the data or making further modifications using the Data or
Relationships views.
Select Edit to open Quer y Editor . Specify additional data transformation and filtering steps before the entire
set of rows is brought into the Power BI Desktop data model.
In addition to importing data from SAP BW cubes, you can also import data from a wide range of other data
sources in Power BI Desktop, and then you can combine them into a single report. This ability presents all sorts of
interesting scenarios for reporting and analytics on top of SAP BW data.

Using Implementation 2.0 SAP BW Connector

Create a new connection to use Implementation 2.0 of the SAP BW Connector. To create a new connection, take the
following steps.
1. Select Get Data . Select either SAP Business Warehouse Application Ser ver or SAP Business
Warehouse Message Ser ver , and then connect.
2. In the new connection dialog, select the implementation. Selecting 2.0 for Implementation , as shown in the
following image, enables Execution mode , Batch size and Enable characteristic structures .
3. Select OK . After this point, experience is the same as described in Version 1 SAP BW Connector features for
the version 1 SAP BW Connector.
New options for Implementation 2.0
Implementation 2.0 supports the following options:
ExecutionMode specifies the MDX interface used to execute queries on the server. The following options are
valid:
SapBusinessWarehouseExecutionMode.BasXml

SapBusinessWarehouseExecutionMode.BasXmlGzip

SapBusinessWarehouseExecutionMode.DataStream

The default value is SapBusinessWarehouseExecutionMode.BasXmlGzip .

Using SapBusinessWarehouseExecutionMode.BasXmlGzip may improve performance when experiencing
high latency for large datasets.
 BatchSize specifies the maximum number of rows to retrieve at a time when executing an MDX statement. A
small number translates into more calls to the server while retrieving a large dataset. A large number of
rows may improve performance, but could cause memory issues on the SAP BW server. The default value is
50000 rows.
EnableStructures indicates whether characteristic structures are recognized. The default value for this option
is false. Affects the list of objects available for selection. Not supported in Native query mode.
The ScaleMeasures option has been deprecated in this implementation. The behavior is now the same as setting
ScaleMeasures to false, always showing unscaled values.
Additional improvements for Implementation 2.0
The following list describes some of the additional improvements that come with the new implementation:
Improved performance.
Ability to retrieve several million rows of data, and fine-tuning through the batch size parameter.
Ability to switch execution modes.
Support for compressed mode. Especially beneficial for high latency connections or large datasets.
Improved detection of Date variables.
[Experimental] Expose Date (ABAP type DATS) and Time (ABAP type TIMS) dimensions as dates and times
respectively, instead of text values.
Better exception handling. Errors that occur in BAPI calls are now surfaced.
Column folding in BasXml and BasXmlGzip modes. For example, if the generated MDX query retrieves 40
columns but the current selection only needs 10, this request will be passed onto the server to retrieve a smaller
dataset.
Changing existing reports to use Implementation 2.0
Changing existing reports to use Implementation 2.0 is only possible in import mode. Follow these steps:
1. Open an existing report, select Edit Queries in the ribbon, and then select the SAP Business Warehouse
query to update.
2. Right-click the query and select Advanced Editor .
3. In the Advanced Editor , change the SapBusinessWarehouse.Cubes call as follows:
Determine whether the query already contains an option record, such as the following example:

If so, add the Implementation 2.0 option, and remove the ScaleMeasures option, if present, as shown:

If the query doesn't already include an options record, just add it. For the following option:
 Just change it to:

Every effort has been made to make Implementation 2.0 of the SAP BW Connector compatible with version 1.
However, there may be some differences because of the different SAP BW MDX execution modes being used. To
resolve any discrepancies, try switching between execution modes.

Troubleshooting
This section provides troubleshooting situations (and solutions) for working with the SAP BW connector.
1. Numeric data from SAP BW returns decimal points instead of commas. For example, 1,000,000 is returned
as 1.000.000.
SAP BW returns decimal data with either a , (comma) or a . (dot) as the decimal separator. To specify
which of those SAP BW should use for the decimal separator, the driver used by Power BI Desktop makes a
call to BAPI_USER_GET_DETAIL . This call returns a structure called DEFAULTS , which has a field called DCPFM
that stores Decimal Format Notation. The field takes one of the following values:
' ' (space) = Decimal point is comma: N.NNN,NN
'X' = Decimal point is period: N,NNN.NN
'Y' = Decimal point is N NNN NNN,NN
Customers who have reported this issue found that the call to BAPI_USER_GET_DETAIL is failing for a
particular user, who is showing the incorrect data, with an error message similar to the following message:

You are not authorized to display users in group TI:

<item>
<TYPE>E</TYPE>
<ID>01</ID>
<NUMBER>512</NUMBER>
<MESSAGE>You are not authorized to display users in group TI</MESSAGE>
<LOG_NO/>
<LOG_MSG_NO>000000</LOG_MSG_NO>
<MESSAGE_V1>TI</MESSAGE_V1>
<MESSAGE_V2/>
<MESSAGE_V3/>
<MESSAGE_V4/>
<PARAMETER/>
<ROW>0</ROW>
<FIELD>BNAME</FIELD>
<SYSTEM>CLNTPW1400</SYSTEM>
</item>

To solve this error, users must ask their SAP admin to grant the SAPBW user being used in Power BI the right
to execute BAPI_USER_GET_DETAIL . It’s also worth verifying that the user has the required DCPFM value, as
described earlier in this troubleshooting solution.
2. Connectivity for SAP BEx queries
You can perform BEx queries in Power BI Desktop by enabling a specific property, as shown in the following
image:
3. The Navigator window doesn't display a data preview and instead provides an object reference not set to
an instance of an object error message.
SAP users need access to specific BAPI function modules to get metadata and retrieve data from SAP BW's
InfoProviders. These modules include:
BAPI_MDPROVIDER_GET_CATALOGS
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_DIMENSIONS
BAPI_MDPROVIDER_GET_HIERARCHYS
BAPI_MDPROVIDER_GET_LEVELS
BAPI_MDPROVIDER_GET_MEASURES
BAPI_MDPROVIDER_GET_MEMBERS
BAPI_MDPROVIDER_GET_VARIABLES
BAPI_IOBJ_GETDETAIL
To solve this issue, verify that the user has access to the various MDPROVIDER modules and
BAPI_IOBJ_GETDETAIL . To further troubleshoot this or similar issues, you can enable tracing. Select File >
Options and settings > Options . In Options , select Diagnostics , then select Enable tracing . Attempt to
retrieve data from SAP BW while tracing is active, and examine the trace file for more detail.

SAP BW Connection support

The following table details the current support for SAP BW.
 A UT H EN T IC AT IO
P RO DUC T M O DE N C O N N EC TO R SN C L IB RA RY SUP P O RT ED

Power BI Desktop Any User / password Application N/A Yes

Server

Power BI Desktop Any Windows Application sapcrypto + Yes

Server gsskrb5/gx64krb
5

Power BI Desktop Any Windows via Application sapcrypto + Yes

impersonation Server gsskrb5/gx64krb
5

Power BI Desktop Any User / password Message Server N/A Yes

Power BI Desktop Any Windows Message Server sapcrypto + Yes

gsskrb5/gx64krb
5

Power BI Desktop Any Windows via Message Server sapcrypto + Yes

impersonation gsskrb5/gx64krb
5

Power BI Import Same as Power BI

Gateway Desktop

Power BI DirectQuery User / password Application N/A Yes

Gateway Server

Power BI DirectQuery Windows via Application sapcrypto + Yes

Gateway impersonation Server gsskrb5/gx64krb
(fixed user, no 5
SSO)

Power BI DirectQuery Use SSO via Application sapcrypto + Yes

Gateway Kerberos for Server gsskrb5/gx64krb
DirectQuery 5
queries option

Power BI DirectQuery User / password Message Server N/A Yes

Gateway

Power BI DirectQuery Windows via Message Server sapcrypto + Yes

Gateway impersonation gsskrb5/gx64krb
(fixed user, no 5
SSO)

Power BI DirectQuery Use SSO via Message Server gsskrb5/gx64krb No

Gateway Kerberos for 5
DirectQuery
queries option

Power BI DirectQuery Use SSO via Message Server sapcrypto Yes

Gateway Kerberos for
DirectQuery
queries option
Next steps
For more information about SAP and DirectQuery, check out the following resources:
DirectQuery and SAP HANA
DirectQuery and SAP Business Warehouse (BW)
Using DirectQuery in Power BI
Power BI data sources
Power BI and SAP BW whitepaper
 Use OneDrive for Business links in Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

Many people have Excel workbooks stored in OneDrive for Business that would be great for use with Power BI
Desktop. With Power BI Desktop, you can use online links for Excel files stored in OneDrive for Business to create
reports and visuals. You can use a OneDrive for Business group account or your individual OneDrive for Business
account.
Getting an online link from OneDrive for Business requires a few specific steps. The following sections explain
those steps, which let you share the file link among groups, across different machines, and with your coworkers.

Get a link from Excel

1. Navigate to your OneDrive for Business location using a browser. Right-click the file you want to use, and
select Open in Excel .

NOTE
Your browser interface might not look exactly like the following image. There are many ways to select Open in Excel
for files in your OneDrive for Business browser interface. You can use any option that allows you to open the file in
Excel.

2. In Excel, select File > Info , and then select the Copy path button, as shown in the following image.
Use the link in Power BI Desktop
In Power BI Desktop, you can use the link you just copied to the clipboard. Take the following steps:
1. In Power BI Desktop, select Get Data > Web .
2. With the Basic option selected, paste the link into the From Web dialog box.
3. Remove the ?web=1 string at the end of the link so that Power BI Desktop can properly navigate to your file,
and then select OK .

4. If Power BI Desktop prompts you for credentials, choose either Windows (for on-premises SharePoint sites)
or Organizational Account (for Microsoft 365 or OneDrive for Business sites).

A Navigator dialog box appears, allowing you to select from the list of tables, sheets, and ranges found in
the Excel workbook. From there, you can use the OneDrive for Business file just like any other Excel file. You
can create reports and use it in datasets like you would with any other data source.

NOTE
To use a OneDrive for Business file as a data source in the Power BI service, with Ser vice Refresh enabled for that file, make
sure you select OAuth2 as the Authentication method when configuring your refresh settings. Otherwise, you may
encounter an error (such as, Failed to update data source credentials) when you attempt to connect or to refresh. Selecting
OAuth2 as the authentication method remedies that credentials error.
 Use the Facebook connector for Power BI Desktop
9/9/2020 • 2 minutes to read • Edit Online

The Facebook connector in Power BI Desktop relies on the Facebook Graph API. As such, features and availability
may vary over time.
You can see a tutorial about the Facebook Connector for Power BI Desktop.

IMPORTANT
Deprecation of Facebook data connector notice: Import and refresh data from Facebook in Excel will no longer work
properly beginning in April, 2020. You can use the Facebook Get & Transform (Power Query) connector until then. After that
date, you will not be able to connect to Facebook, and will receive an error message. We recommend revising or removing
any existing Get & Transform (Power Query) queries that use the Facebook connector as soon as possible to avoid
unexpected results.

Facebook expired v1.0 of its Graph API on April 30 2015. Power BI uses the Graph API behind the scenes for the
Facebook connector, allowing you to connect to your data and analyze it.
Queries that were built before April 30 2015 may no longer work or return less data. Subsequent to April 30 2015,
Power BI leverages v2.8 in all calls to the Facebook API. If your query was built prior to April 30, 2015 and you have
not used it since, you’ll likely need to authenticate again, to approve the new set of permissions that we’ll ask for.
Although we attempt to release updates in accordance with any changes, the API may change in a way that affects
the results of the queries we generate. In some cases, certain queries may no longer be supported. Due to this
dependency, we cannot guarantee the results of your queries when using this connector.
More details on the change in the Facebook API are available here.
 Use the Google Analytics connector for Power BI
Desktop
9/9/2020 • 2 minutes to read • Edit Online

NOTE
The Google Analytics content pack and the connector in Power BI Desktop rely on the Google Analytics Core Reporting API.
As such, features and availability may vary over time.

You can connect to Google Analytics data using the Google Analytics connector. To connect, follow these steps:
1. In Power BI Desktop , select Get Data from the Home ribbon tab.
2. In the Get Data window, select Online Ser vices from the categories in the left pane.
3. Select Google Analytics from the selections in the right pane.
4. At the bottom of the window, select Connect .
You're prompted with a dialog that explains that the connector is a Third-Party Service, and warns about how
features and availability may change over time, and other clarifications.

When you select Continue , you're prompted to sign in to Google Analytics.

When you enter your credentials, you're prompted that Power BI would like to have offline access. This is how you
use Power BI Desktop to access your Google Analytics data.
Once you accept, Power BI Desktop shows that you're currently signed in.

Select Connect , and your Google Analytics data is connected to Power BI Desktop , and loads the data.

Changes to the API

Although we attempt to release updates in accordance with any changes, the API may change in a way that affects
the results of the queries we generate. In some cases, certain queries may no longer be supported. Due to this
dependency we cannot guarantee the results of your queries when using this connector.
More details on changes to the Google Analytics API can be found in their changelog.
 Connect to Project Online data through Power BI
Desktop
9/9/2020 • 2 minutes to read • Edit Online

You can connect to data in Project Online through Power BI Desktop.

Step 1: Download Power BI Desktop

1. Download Power BI Desktop, then run the installer to get Power BI Desktop on your computer.

Step 2: Connect to Project Online with OData

1. Open Power BI Desktop .
2. On the Welcome screen, select Get Data .
3. Choose OData feed and select Connect .
4. Enter the address for your OData feed in the URL box, and then click OK.
If the address for your Project Web App site resembles https://<tenantname>.sharepoint.com/sites/pwa,
then the address you’ll enter for your OData Feed is
https://<tenantname>.sharepoint.com/sites/pwa/_api/Projectdata.
For our example, we’re using:
https://contoso.sharepoint.com/sites/pwa/default.aspx

5. Power BI Desktop will prompt you to authenticate with your work or school account. Select Organizational
account and then enter your credentials.

The account you use to connect to the OData feed must have at least Portfolio Viewer access to the Project Web
App site.
From here, you can choose which tables you would like to connect to and build a query. Want an idea of how to get
started? The following blog post shows how to build a burn down chart from your Project Online data. The blog
post refers to using Power Query to connect to Project Online, but this applies to Power BI Desktop as well.
Creating burn down charts for Project using Power Pivot and Power Query
 Get data from files for Power BI
9/9/2020 • 3 minutes to read • Edit Online

In Power BI, you can connect to or import data and reports from three types of files.
Microsoft Excel (.xlsx or .xlsm)
Power BI Desktop (.pbix)
Comma Separated Value (.csv)

What does get data from a file really mean?

In Power BI the data you explore comes from a dataset. But in order to have a dataset, you first need to get some
data. For this article, we're going to focus on getting data from files.
To better understand the importance of datasets, and how we get data for them, let’s look at an automobile. Take a
seat in your car and look at the dashboard. That’s a lot like sitting in front of your computer looking at a dashboard
in Power BI. The dashboard shows you all the things your car is doing; how fast the engine is revving, temperature,
what gear you’re in, your speed, etc.
In Power BI, a dataset is like the engine in your car. The dataset provides the data, metrics, and information that’s
displayed in your Power BI dashboard. Of course your engine, or dataset, needs fuel, and in Power BI, that fuel is
data. Your car has a fuel tank that provides gas to the engine. Much the same in Power BI, you need a fuel tank that
has data you can feed to your dataset. In our case, that fuel tank is a Power BI Desktop file, an Excel workbook file,
or a .CSV file.
We can even take it one step further. A fuel tank in a car has to be filled with gas. The gas for our Power BI Desktop,
Excel, or .CSV file is data from another data source. We get data from another data source and put it into an Excel,
Power BI Desktop, or .CSV file. If it's an Excel workbook or .CSV file, we can manually enter rows of data. Or, we can
connect to an external data source to query and load data into our file. Once we have a file with some data, we can
get it into Power BI as a dataset.

NOTE
Data in Excel workbooks must be in a table, or in the data model, to be imported by Power BI.

Where your file is saved makes a difference

Local - If you save your file to a local drive on your computer or another location in your organization, from Power
BI, you can import your file into Power BI. Your file will actually remain on your local drive, so the whole file isn’t
really imported into Power BI. What really happens is a new dataset is created in your Power BI site and data, and in
some cases the data model, are loaded into the dataset. If your file has any reports, those will appear in your Power
BI site under Reports.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Excel Power BI Desktop, or a .CSV file
and your dataset, reports, and dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the
cloud, Power BI connects to your file on OneDrive about every hour. If any changes are found, your dataset, reports,
and dashboards are automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing in with your OneDrive with your
Microsoft account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to your
file about every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team-Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

Ready to get started?

See the following articles to learn more about getting your file into Power BI.
Get data from Excel workbook files
Get data from Power BI Desktop files
Get data from Comma Separated Value files
 Get data from Excel workbook files
9/9/2020 • 8 minutes to read • Edit Online

Microsoft Excel is one of the most widely used business applications around. It’s also one of the most common
ways to get your data into Power BI.

What types of workbooks does Power BI support?

Power BI supports importing or connecting to workbooks created in Excel 2007 and later. Workbooks must be
saved as .xlsx or .xlsm file type and be under 1 GB. Some features described in this article are only available in later
versions of Excel.
Workbooks with ranges or tables of data
If your workbook has simple worksheets with ranges of data, to get the most out of your data in Power BI, be sure
to format those ranges as tables. This way, when creating reports in Power BI, you’ll see named tables and columns
in the Fields pane, making it much easier to visualize your data.
Workbooks with data models
Workbooks can contain a data model with one or more tables of data loaded into it by using linked tables, Power
Query (Get & Transform in Excel 2016), or Power Pivot. Power BI supports all data model properties such as
relationships, measures, hierarchies, and KPIs.

NOTE
Workbooks with data models cannot be shared across Power BI tenants. For example, a user who logs in to Power BI using a
contoso.com account cannot share an Excel workbook with a user who logs in using a Power BI login account from
woodgrovebank.com.

Workbooks with connections to external data sources

If you use Excel to connect to an external data source, once your workbook is in Power BI, you can create reports
and dashboards based on data from that connected data source. You can also setup Scheduled Refresh to
automatically connect right to the data source and get updates. You’ll no longer need to refresh manually from the
Data ribbon in Excel. Any visualizations in reports and tiles in dashboards based on data from that data source are
updated automatically. To learn more, see Data refresh in Power BI.
Workbooks with Power View sheets, PivotTables and charts
How your PowerView sheets and PivotTables and charts appear, or not appear, in Power BI depends on where your
workbook file is saved and how you choose to get it into Power BI. We'll go into this more below.

Data types
Power BI supports the following data types: Whole Number, Decimal Number, Currency, Date, True/False, Text.
Marking data as specific data types in Excel will improve the Power BI experience.

Prepare your workbook for Power BI

Watch this helpful video to learn more about how to make sure your Excel workbooks are ready for Power BI.
https://www.youtube.com/embed/l2wy4XgQIu0

Where your workbook file is saved makes a difference

Local - If you save your workbook file to a local drive on your computer or another location in your organization,
from Power BI you can load your file into Power BI. Your file will actually remain on your local drive, so the whole
file isn’t really imported into Power BI. What really happens is a new dataset is created in Power BI and data and
the data model (if any) from the workbook are loaded into the dataset. If your workbook has any Power View
sheets, those will appear in your Power BI site under Reports. Excel 2016 also has the Publish feature (under the
File menu). Using Publish is effectively the same as using Get Data > Files > Local File from Power BI, but is
often easier to update your dataset in Power BI if you’re regularly making changes to the workbook.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Excel and your dataset, reports, and
dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI connects to your
workbook file on OneDrive about every hour. If any changes are found, your dataset, reports, and dashboards are
automatically updated in Power BI. Just like if you saved your workbook to a local drive, you can also use Publish
to update your dataset and reports in Power BI immediately; otherwise Power BI will automatically synchronize,
usually within an hour.
OneDrive - Personal – If you save your workbook files to your own OneDrive account, you’ll get many of the
same benefits as you would with OneDrive for Business. The biggest difference is when you first connect to your
file (using Get Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft
account, which is usually different from what you use to sign in to Power BI. When signing in with your OneDrive
with your Microsoft account, be sure to select the Keep me signed in option. This way, Power BI will be able to
connect to your workbook file about every hour and make sure your dataset and reports in Power BI are in-sync.
SharePoint Team-Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

One Excel workbook – two ways to use it

If you save your workbook files to OneDrive , you'll have a couple of ways you can explore your data in Power BI
Import Excel data into Power BI
When you choose Impor t , any supported data in tables and/or a data model are imported into a new dataset in
Power BI. If you have any Power View sheets, those will be re-created in Power BI as reports.
You can continue editing your workbook. When your changes are saved, they’ll be synchronized with the dataset in
Power BI, usually within about an hour. If you need more immediate gratification, you can just click Publish again,
and your changes are exported right then and there. Any visualizations you have in reports and dashboards will be
updated, too.
Choose this option if you’ve used Get & Transform data or Power Pivot to load data into a data model, or if your
workbook has Power View sheets with visualizations you want to see in Power BI.
In Excel 2016, you can also use Publish > Export. It's pretty much the same thing. To learn more, see Publish to
Power BI from Excel 2016.
Connect, manage and view Excel in Power BI
When you choose Connect , your workbook will appear in Power BI just like it would in Excel Online. But, unlike
Excel Online, you’ll have some great features to help you pin elements from your worksheets right to your
dashboards.
You can’t edit your workbook in Power BI. But if you need to make some changes, you can click Edit, and then
choose to edit your workbook in Excel Online or open it in Excel on your computer. Any changes you make are
saved to the workbook on OneDrive.
Choose this option if you only have data in worksheets, or you have ranges, PivotTables and charts you want to pin
to dashboards.
In Excel 2016, you can also use Publish > Upload. It's pretty much the same thing. To learn more, see Publish to
Power BI from Excel 2016.

Import or connect to an Excel workbook from Power BI

1. In Power BI, in the nav pane, click Get Data .
2. In Files, click Get .

3. Find your file.

4. If your workbook file is on OneDrive or SharePoint - Team Sites, choose Impor t or Connect .

Local Excel workbooks

You can also use a local Excel file and upload it into Power BI. Simply select Local File from the previous menu,
then navigate to where you have your Excel workbooks saved.

Once selected, choose to Upload your file into Power BI.

Once your workbook is uploaded, you get a notification that the workbook is ready.

Once the workbook is ready, you can find it in the Repor ts section of Power BI.
Publish from Excel 2016 to your Power BI site
Using the Publish to Power BI feature in Excel 2016 is effectively the same as using Get Data in Power BI to
import or connect to your file. We won't go into the details here, but you can see Publish to Power BI from Excel
2016 to learn more.

Troubleshooting
Workbook file too big? Check out Reduce the size of an Excel workbook to view it in Power BI.
Currently, when you choose Import, Power BI only imports data that is part of a named table or a data model. As a
result, if the workbook contains no named tables, Power View sheets, or Excel data models, you might see this
error: "We couldn't find any data in your Excel workbook" . This article explains how to fix your workbook
and re-import it.

Next steps
Explore your data - Once you get data and reports from your file into Power BI, it's time to explore. Just right-
click the new dataset and then click Explore. If you chose to connect to a workbook file on OneDrive in step 4, your
workbook will appear in Reports. When you click on it, it will open in Power BI, just as it would if it were in Excel
Online.
Schedule refresh - If your Excel workbook file connects to external data sources, or you imported from a local
drive, you can setup scheduled refresh to make sure your dataset or report is always up-to-date. In most cases,
setting up scheduled refresh is quite easy to do, but going into the details is outside the scope of this article. See
Data refresh in Power BI to learn more.
Publish to Power BI from Excel 2016
Data refresh in Power BI
 Get data from Power BI Desktop files
9/9/2020 • 3 minutes to read • Edit Online

Power BI Desktop makes business intelligence and reporting easy. Whether you're connecting to a many
different data sources, querying and transforming data, modeling your data, and creating powerful and dynamic
reports, Power BI Desktop makes business intelligence tasks intuitive and fast. If you're not familiar with Power
BI Desktop , check out Getting started with Power BI Desktop.
Once you bring data into Power BI Desktop and create a few reports, it’s time to get your saved file into the
Power BI ser vice .

Where your file is saved makes a difference

Local - If you save your file to a local drive on your computer or another location in your organization, you can
import your file or you can publish from Power BI Desktop to get its data and reports into Power BI. Your file will
actually remain on your local drive, so the whole file isn’t really moved into Power BI. What really happens is a new
dataset is created in Power BI and data and the data model from the Power BI Desktop file are loaded into the
dataset. If your file has any reports, those will appear in your Power BI site under Reports.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your work in Power BI Desktop and your dataset,
reports, and dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI
connects to your file on OneDrive about every hour. If any changes are found, your dataset, reports, and
dashboards are automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing in with your OneDrive with your
Microsoft account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to your
file about every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team-Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder. You can also set up a Sync folder that points to the SharePoint folder;
files there will sync with the master copy on SharePoint.

Import or connect to a Power BI Desktop file from Power BI

IMPORTANT
The maximum file size you can import into Power BI is 1 gigabyte.

1. In Power BI, in the navigator pane, click ** Get Data**.

2. In Files , click Get .

3. Find your file. Power BI Desktop files have a .PBIX extension.

Publish a file from Power BI Desktop to your Power BI site

Using Publish from Power BI Desktop is similar using Get Data in Power BI, in terms of initially importing your file
data from a local drive or connecting to it on OneDrive. However, there are differences: if you upload from a local
drive, you'll want to refresh that data frequently to ensure the online and local copies of the data are current with
each other.
Here’s the quick how to, but you can see Publish from Power BI Desktop to learn more.
1. In Power BI Desktop, click File > Publish > Publish to Power BI , or click Publish on the ribbon.

2. Sign in to Power BI. You'll only need to do this the first time.
When complete, you'll get a link to open your report in your Power BI site.

Next steps
Explore your data - Once you get data and reports from your file into Power BI, it's time to explore. If your file
already has reports in it, they'll appear in the navigator pane in Repor ts . If your file just had data, you can create
new reports; just right-click the new dataset and then click Explore .
Refresh external data sources - If your Power BI Desktop file connects to external data sources, you can setup
scheduled refresh to make sure your dataset is always up-to-date. In most cases, setting up scheduled refresh is
quite easy to do, but going into the details is outside the scope of this article. See Data refresh in Power BI to learn
more.
 Edit parameter settings in the Power BI service
9/9/2020 • 2 minutes to read • Edit Online

Report creators add query parameters to reports in Power BI Desktop. Parameters allow them to make parts of
reports depend on one or more parameter values. For example, a report creator may create a parameter that
restricts the data to a single country/region, or a parameter that defines acceptable formats for fields like dates,
time, and text.

Review and edit parameters in Power BI service

As a report creator, you define parameters in Power BI Desktop. When you publish that report to Power BI service,
the parameter settings and selections travel with it. You can review and edit parameter settings in the Power BI
service, but not create them.

1. In the Power BI service, select the cog icon to open Settings .

2. Select the tab for Datasets and highlight a dataset in the list.

3. Expand Parameters . If the selected dataset has no parameters, you see a message with a link to Learn more
about query parameters. If the dataset does have parameters, expand the Parameters heading to reveal
those parameters.
 Review the parameter settings and make changes if needed. Grayed-out fields aren't editable.

Next steps
An ad-hoc way to add simple parameters is by modifying the URL.
 Get data from Comma Separated Value (.CSV) files
9/9/2020 • 2 minutes to read • Edit Online

Comma separated value files, often known as a .CSV, are simple text files with rows of data where each value is
separated by a comma. These types of files can contain very large amounts of data within a relatively small file size,
making them an ideal data source for Power BI. You can download a sample .CSV file here.
If you have a .CSV, it’s time to get it into your Power BI site as a dataset where you can begin exploring your data,
create some dashboards, and share your insights with others.

TIP
Many organizations output a .CSV with updated data each day. To make sure your dataset in Power BI stays in-sync with
your updated file, be sure the file is saved to OneDrive with the same name.

Where your file is saved makes a difference

Local - If you save your .CSV file to a local drive on your computer or another location in your organization, from
Power BI you can import your file into Power BI. Your file will actually remain on your local drive, so the whole file
isn’t really imported into Power BI. What really happens is a new dataset is created in Power BI and data from the
.CSV file is loaded into the dataset.
OneDrive - Business – If you have OneDrive for Business and you sign into it with the same account you sign
into Power BI with, this is by-far the most effective way to keep your .CSV file and your dataset, reports, and
dashboards in Power BI in-sync. Because both Power BI and OneDrive are in the cloud, Power BI connects to your
file on OneDrive about every hour. If any changes are found, your dataset, reports, and dashboards are
automatically updated in Power BI.
OneDrive - Personal – If you save your files to your own OneDrive account, you’ll get many of the same benefits
as you would with OneDrive for Business. The biggest difference is when you first connect to your file (using Get
Data > Files > OneDrive – Personal) you’ll need to sign in to your OneDrive with your Microsoft account, which is
usually different from what you use to sign in to Power BI. When signing into your OneDrive with your Microsoft
account, be sure to select the Keep me signed in option. This way, Power BI will be able to connect to your file about
every hour and make sure your dataset in Power BI is in-sync.
SharePoint Team-Sites – Saving your Power BI Desktop files to SharePoint – Team Sites is much the same as
saving to OneDrive for Business. The biggest difference is how you connect to the file from Power BI. You can
specify a URL or connect to the root folder.

Import or connect to a .CSV file

IMPORTANT
The maximum file size you can import into Power BI is 1 gigabyte.

1. In Power BI, in the navigator pane, click Get Data .

2. In Files , click Get .

3. Find your file.

Next steps
Explore your data - Once you get data from your file into Power BI, it's time to explore. Just right-click the new
dataset and then click Explore .
Schedule refresh - If your file is saved to a local drive, you can setup scheduled refresh so your dataset and
reports in Power BI stay up-to-date. To learn more, see Data refresh in Power BI. If your file is saved to OneDrive,
Power BI will automatically synchronize with it about every hour.
 Real-time streaming in Power BI
9/9/2020 • 14 minutes to read • Edit Online

Power BI with real-time streaming lets you stream data and update dashboards in real time. Any visual or
dashboard created in Power BI can display and update real-time data and visuals. The devices and sources of
streaming data can be factory sensors, social media sources, service usage metrics, or many other time-sensitive
data collectors or transmitters.

This article shows you how to set up real-time streaming dataset in Power BI. First, it's important to understand the
types of real-time datasets that are designed to display in tiles (and dashboards), and how those datasets differ.

Types of real-time datasets

There are three types of real-time datasets, which are designed for display on real-time dashboards:
Push dataset
Streaming dataset
PubNub streaming dataset
First let's understand how these datasets differ from one another (this section), then we discuss how to push data
into those each of these datasets.
Push dataset
With a push dataset , data is pushed into the Power BI service. When the dataset is created, the Power BI service
automatically creates a new database in the service to store the data. Since there is an underlying database that
continues to store the data as it comes in, reports can be created with the data. These reports and their visuals are
just like any other report visuals, which means you can use all of Power BI's report building features to create
visuals, including Power BI visuals, data alerts, pinned dashboard tiles, and more.
Once a report is created using the push dataset, any of its visuals can be pinned to a dashboard. On that dashboard,
visuals update in real-time whenever the data is updated. Within the service, the dashboard is triggering a tile
refresh every time new data is received.
There are two considerations to note about pinned tiles from a push dataset:
Pinning an entire report using the pin live page option will not result in the data automatically being updated.
Once a visual is pinned to a dashboard, you can use Q&A to ask questions of the push dataset in natural
language. Once you make a Q&A query, you can pin the resulting visual back to the dashboard, and that
dashboard will also update in real-time.
Streaming dataset
With a streaming dataset , data is also pushed into the Power BI service, with an important difference: Power BI
only stores the data into a temporary cache, which quickly expires. The temporary cache is only used to display
visuals, which have some transient sense of history, such as a line chart that has a time window of one hour.
With a streaming dataset , there is no underlying database, so you cannot build report visuals using the data that
flows in from the stream. As such, you cannot make use of report functionality such as filtering, Power BI visuals,
and other report functions.
The only way to visualize a streaming dataset is to add a tile and use the streaming dataset as a custom
streaming data source. The custom streaming tiles that are based on a streaming dataset are optimized for
quickly displaying real-time data. There is little latency between when the data is pushed into the Power BI service
and when the visual is updated, since there's no need for the data to be entered into or read from a database.
In practice, streaming datasets and their accompanying streaming visuals are best used in situations when it is
critical to minimize the latency between when data is pushed and when it is visualized. In addition, it's best practice
to have the data pushed in a format that can be visualized as-is, without any additional aggregations. Examples of
data that's ready as-is include temperatures, and pre-calculated averages.
PubNub streaming dataset
With a PubNub streaming dataset, the Power BI web client uses the PubNub SDK to read an existing PubNub data
stream. No data is stored by the Power BI service. Because this call is made from the web client directly, you would
have to list traffic to PubNub as allowed, if you only allowed whitelisted outbound traffic from your network. Refer
to the instructions in the support article about whitelisting outbound traffic for PubNub.
As with the streaming dataset , with the PubNub streaming dataset there is no underlying database in Power
BI, so you cannot build report visuals against the data that flows in, and cannot take advantage of report
functionality such as filtering, Power BI visuals, and so on. As such, the PubNub streaming dataset can also only
be visualized by adding a tile to the dashboard, and configuring a PubNub data stream as the source.
Tiles based on a PubNub streaming dataset are optimized for quickly displaying real-time data. Since Power BI
is directly connected to the PubNub data stream, there is little latency between when the data is pushed into the
Power BI service and when the visual is updated.
Streaming dataset matrix
The following table (or matrix, if you like) describes the three types of datasets for real-time streaming, and lists
capabilities and limitations of each.
 NOTE
See this article for information on Push limits on how much data can be pushed in.

Pushing data to datasets

The previous section described the three primary types of real-time datasets you can use in real-time streaming,
and how they differ. This section describes how to create and push data into those datasets.
There are three primary ways you can push data into a dataset:
Using the Power BI REST APIs
Using the Streaming Dataset UI
Using Azure Stream Analytics
Let's take a look at each of those approaches in turn.
Using Power BI REST APIs to push data
Power BI REST APIs can be used to create and send data to push datasets and to streaming datasets. When you
create a dataset using Power BI REST APIs, the defaultMode flag specifies whether the dataset is push or streaming.
If no defaultMode flag is set, the dataset defaults to a push dataset.
If the defaultMode value is set to pushStreaming, the dataset is both a push and streaming dataset, providing the
benefits of both dataset types.

NOTE
When using datasets with the defaultMode flag set to pushStreaming, if a request exceeds the 15Kb size restriction for a
streaming dataset, but is less than the 16MB size restriction of a push dataset, the request will succeed and the data will be
updated in the push dataset. However, any streaming tiles will temporarily fail.

Once a dataset is created, use the REST APIs to push data using the PostRows API.
All requests to REST APIs are secured using Azure AD OAuth .
Using the Streaming Dataset UI to push data
In the Power BI service, you can create a dataset by selecting the API approach as shown in the following image.

When creating the new streaming dataset, you can select to enable Historic data analysis as shown below, which
has a significant impact.
When Historic data analysis is disabled, and it is by default, you create a streaming dataset as described
earlier in this article. When Historic data analysis is enabled, the dataset created becomes both a streaming
dataset and a push dataset . This is equivalent to using the Power BI REST APIs to create a dataset with its
defaultMode set to pushStreaming, as described earlier in this article.

NOTE
For streaming datasets created using the Power BI service UI, as described in the previous paragraph, Azure AD
authentication is not required. In such datasets, the dataset owner receives a URL with a rowkey, which authorizes the
requestor to push data into the dataset with out using an Azure AD OAuth bearer token. Take now, however, that the Azure
AD (AAD) approach still works to push data into the dataset.

Using Azure Stream Analytics to push data

You can add Power BI as an output within Azure Stream Analytics (ASA), and then visualize those data streams in
the Power BI service in real time. This section describes technical details about how that process occurs.
Azure Stream Analytics uses the Power BI REST APIs to create its output data stream to Power BI, with defaultMode
set to pushStreaming, resulting in a dataset that can take advantage of both push and streaming . When the
dataset is created, Azure Stream Analytics sets the retentionPolicy flag to basicFIFO. With that setting, the
database supporting its push dataset stores 200,000 rows, and which rows are dropped in a first-in first-out (FIFO)
fashion.
Cau t i on

If your Azure Stream Analytics query results in very rapid output to Power BI (for example, once or twice per
second), Azure Stream Analytics will begin batching those outputs into a single request. This may cause the request
size to exceed the streaming tile limit. In that case, as mentioned in previous sections, streaming tiles will fail to
render. In such cases, the best practice is to slow the rate of data output to Power BI; for example, instead of a
maximum value every second, set it to a maximum over 10 seconds.

Set up your real-time streaming dataset in Power BI

Now that we've covered the three primary types of datasets for real-time streaming, and the three primary ways
you can push data into a dataset, let's get your real-time streaming dataset working in Power BI.
To get started with real-time streaming, you need to choose one of the two ways that streaming data can be
consumed in Power BI:
tiles with visuals from streaming data
datasets created from streaming data that persist in Power BI
With either option, you'll need to set up Streaming data in Power BI. To do this, in your dashboard (either an
existing dashboard, or a new one) select Add a tile and then select Custom streaming data .

If you don't have streaming data set up yet, don't worry - you can select manage data to get started.
On this page, you can input the endpoint of your streaming dataset if you already have one created (into the text
box). If you don't have a streaming dataset yet, select the plus icon ( + ) in the upper right corner to see the
available options to create a streaming dataset.

When you click on the + icon, you see two options:

The next section describes these options, and goes into more detail about how to create a streaming tile or how to
create a dataset from the streaming data source, which you can then use later to build reports.

Create your streaming dataset with the option you like best
There are two ways to create a real-time streaming data feed that can be consumed and visualized by Power BI:
Power BI REST API using a real-time streaming endpoint
PubNub
The next sections look at each option in turn.
Using the POWER BI REST API
Power BI REST API - Recent improvements to the Power BI REST API are designed to make real-time streaming
easier for developers. When you select API from the New streaming dataset window, you're presented with
entries to provide that enable Power BI to connect to and use your endpoint:

If you want Power BI to store the data that's sent through this data stream, enable Historic data analysis and you'll
be able to do reporting and analysis on the collected data stream. You can also learn more about the API.
Once you successfully create your data stream, you're provided with a REST API URL endpoint, which your
application can call using POST requests to push your data to Power BI streaming data dataset you created.
When making POST requests, you should ensure the request body matches the sample JSON provided by the
Power BI user interface. For example, wrap your JSON objects in an array.
Using PubNub
With the integration of PubNub streaming with Power BI, you can use your low-latency PubNub data streams (or
create new ones) and use them in Power BI. When you select PubNub and then select Next , you see the following
window:
 WARNING
PubNub channels can be secured by using a PubNub Access Manager (PAM) authentication key. This key will be shared with
all users who have access to the dashboard. You can learn more about PubNub access control.

PubNub data streams are often high volume, and are not always suitable in their original form for storage and
historical analysis. To use Power BI for historical analysis of PubNub data, you'll have to aggregate the raw PubNub
stream and send it to Power BI. One way to do that is with Azure Stream Analytics.

Example of using real time streaming in Power BI

Here's a quick example of how real time streaming in Power BI works. You can follow along with this sample to see
for yourself the value of real time streaming.
In this sample, we use a publicly available stream from PubNub . Here are the steps:
1. In the Power BI ser vice , select a dashboard (or create a new one) and select Add tile > Custom
Streaming Data and then select the Next button.
2. If you don't have and streaming data sources yet, select the manage data link ( just above the Next button),
then select + Add streaming data from the link in the upper right of the window. Select PubNub and then
select Next .
3. Create a name for your dataset, then paste in the following values into the window that appears, then select
Next :
Subscribe key:

sub-c-5f1b7c8e-fbee-11e3-aa40-02ee2ddab7fe

Channel:

pubnub-sensor-network
4. In the following window, just select the defaults (which are automatically populated), then select Create .
5. Back in your Power BI workspace, create a new dashboard and then add a tile (see above for steps, if you
need them). This time when you create a tile and select Custom Streaming Data , you have a streaming
data set to work with. Go ahead and play around with it. Adding the number fields to line charts, and then
adding other tiles, you can get a real time dashboard that looks like the following:
Give it a try, and play around with the sample dataset. Then go create your own datasets, and stream live data to
Power BI.

Questions and answers

Here are some common questions about real-time streaming in Power BI, and answers.
Can I use filters on push dataset? How about streaming dataset?
Unfortunately, streaming datasets do not support filtering. For push datasets, you can create a report, filter the
report, and then pin the filtered visuals to a dashboard. However, there is no way to change the filter on the visual
once it's on the dashboard.
Separately, you can pin the live report tile to the dashboard, in which case you can change the filters. However, live
report tiles will not update in real-time as data is pushed in – you'll have to manually update the visual by using the
refresh dashboard tiles option in the More menu.
When applying filters to push datasets with DateTime fields with millisecond precision, equivalence operators are
not supported. However, operators such as greater than (>) or less than (<) do operate properly.
How do I see the latest value on a push dataset? How about streaming dataset?
Streaming datasets are designed for displaying the latest data. You can use the Card streaming visual to easily see
latest numeric values. Unfortunately, the card does not support data of type DateTime or Text.
For push datasets, when you have a timestamp in the schema you can try creating a report visual with the last N
filter.
Can I connect to push or streaming datasets in Power BI Desktop?
Push and hybrid datasets can be live connected in Power BI Desktop. Other streaming datasets cannot be connected
in Power BI Desktop.
Given the previous question, how can I do any modeling on real-time datasets?
Modeling is not possible on a streaming dataset, since the data is not stored permanently. For a push dataset, you
can use create dataset REST API to create a dataset with relationship and measures and/or use the update table
REST APIs to add measures to an existing table.
How can I clear all the values on a push dataset? How about streaming dataset?
On a push dataset, you can use the delete rows REST API call. There is currently no way to clear data from a
streaming dataset, though the data will clear itself after an hour.
I set up an Azure Stream Analytics output to Power BI, but I don't see it appearing in Power BI – what's wrong?
Here's a checklist you can use to troubleshoot the issue:
1. Restart the Azure Stream Analytics job ( jobs created before the streaming GA release will require a restart)
2. Try reauthorizing your Power BI connection in Azure Stream Analytics
3. Which workspace did you specify in the Azure Stream Analytics output? In the Power BI service, are you
checking in that (same) workspace?
4. Does the Azure Stream Analytics query explicitly output to the Power BI output? (using the INTO keyword)
5. Does the Azure Stream Analytics job have data flowing through it? The dataset is only created when data is
being transmitted.
6. Can you look into the Azure Stream Analytics logs to see if there are any warnings or errors?

Automatic page refresh

Automatic page refresh works at a report page level, and allows you to set a refresh interval for visuals that's only
active when the page is being consumed. Automatic page refresh is only available for DirectQuery data sources.
The minimum refresh interval depends on which type of workspace where the report is published, and capacity
admin settings for Premium workspaces.
Learn more about automatic page refresh in the automatic page refresh article.

Next steps
Here are a few links you might find useful when working with real-time streaming in Power BI:
Overview of the Power BI REST API with real-time data
Azure Stream Analytics
 Publish to Power BI from Microsoft Excel
9/9/2020 • 4 minutes to read • Edit Online

With Microsoft Excel 2016 and later, you can publish your Excel workbooks directly to your Power BI workspace,
where you can create highly interactive reports and dashboards based on your workbook’s data. You can then
share your insights with others in your organization.

When publishing a workbook to Power BI, there are few things to consider:
The account you use to sign in to Office, OneDrive for Business (if using workbooks saved there), and Power BI
must be the same account.
You cannot publish an empty workbook, or a workbook that doesn’t have any Power BI supported content.
You cannot publish encrypted or password protected workbooks, or workbooks with Information Protection
Management.
Publishing to Power BI requires modern authentication be enabled (default). If disabled, the Publish option is
not available from the File menu.

Publish your Excel workbook

To publish your Excel workbook, in Excel, select File > Publish and select either Upload or Expor t .
If you Upload your workbook to Power BI, you can interact with the workbook just as you would interact using
Excel Online. You can also pin selections from your workbook onto Power BI dashboards, and share your
workbook, or selected elements, through Power BI.
If you select Expor t , you can export table data and its data model into a Power BI dataset, which you can then use
to create Power BI reports and dashboards.
Local file publishing
Excel supports publishing of local Excel files. They do not need to be saved to OneDrive for Business or SharePoint
Online.

IMPORTANT
You can only publish local files if you're using Excel 2016 (or later) with a Microsoft 365 subscription. Excel 2016 standalone
installations can Publish to Power BI, but only when the workbook is saved to OneDrive for Business or SharePoint Online.

When you select Publish , you can select the workspace to which you want to publish. If your Excel file resides on
OneDrive for Business, you can only publish to your My Workspace. If your Excel file resides on a local drive, you
can publish to My Workspace or a shared workspace to which you have access.

Two options on how to get your workbook into Power BI.

Once published, the workbook content you publish is imported into Power BI, separate from the local file. If you
want to update the file in Power BI, you must publish the updated version again, or you can refresh the data by
configuring a scheduled refresh, on the workbook, or on the dataset in Power BI.
Publishing from a standalone Excel installation
When publishing from a standalone Excel installation, the workbook must be saved to OneDrive for Business.
Select Save to Cloud and choose a location in OneDrive for Business.
Once your workbook is saved to OneDrive for Business, when you select Publish , you have two options to get
your workbook into Power BI, Upload or Expor t :

Upload your workbook to Power BI

When you choose the Upload option, your workbook will appear in Power BI just like it would in Excel Online. But,
unlike Excel Online, you’ll have some options that enable you to help you pin elements from your worksheets to
dashboards.
You can’t edit your workbook in Power BI. If you need to make some changes to the data, you can select Edit then
choose to edit your workbook in Excel Online or open it in Excel on your computer. Any changes you make are
saved to the workbook on OneDrive for Business.
When you Upload , no dataset is created in Power BI. Your workbook will appear in Reports, in your workspace
nav pane. Workbooks uploaded to Power BI have a special Excel icon, identifying them as Excel workbooks that
have been uploaded.
Choose the Upload option if you only have data in worksheets, or you have PivotTables and Charts you want to
see in Power BI.
Using Upload from Publish to Power BI in Excel is a similar experience to Get Data > File > OneDrive for
Business > Connect, Manage and View Excel in Power BI from Power BI in your browser.
Export workbook data to Power BI
When you choose the Expor t option, any supported data in tables and/or a data model are exported into a new
dataset in Power BI. Any Power View sheets in the workbook are re-created in Power BI as reports.
You can continue editing your workbook. When your changes are saved, they are synchronized with the dataset in
Power BI, usually within about an hour. If you need more immediate updates, you can select Publish again from
Excel, and your changes are exported immediately. Any visualizations in reports and dashboards are updated, too.
Choose the Publish option if you’ve used the Get & Transform data or Power Pivot features to load data into a
data model, or if your workbook has Power View sheets with visualizations that you want to see in Power BI.
Using Expor t is very similar to using Get Data > File > OneDrive for Business > Expor t Excel data into
Power BI from Power BI in your browser.

Publishing
When you choose either option, Excel signs in to Power BI with your current account, then publishes your
workbook to your Power BI workspace. You can monitor the status bar in Excel to see how the publish process is
progressing.

When complete, you can go to Power BI directly from Excel.

Next steps
Excel data in Power BI
More questions? Try the Power BI Community
 Reduce the size of an Excel workbook to view it in
Power BI
9/9/2020 • 2 minutes to read • Edit Online

You can upload any Excel workbook smaller than 1 GB to Power BI. An Excel workbook can have two parts: a Data
Model, and the rest of the report—the core worksheet contents. If the report meets the following size limits, you
can save it to OneDrive for Business , connect to it from Power BI, and view it in Excel Online:
The workbook as a whole can be up to 1 GB.
The core worksheet contents can be up to 30 MB.

What makes core worksheet contents larger than 30 MB

Here are some elements that can make the core worksheet contents larger than 30 MB:
Images.
Shaded cells. Remove a cell shading format.
Colored worksheets. Remove a sheet background.
Text boxes.
Clip art.
Consider removing these elements, if possible.
If the report has a Data Model, you have some other options:
Remove data from Excel worksheets, and store it in the Data Model instead. See “Remove data from
worksheets” below for details.
Create a memory-efficient Data Model to reduce the overall size of the report.
To make any of these changes, you need to edit the workbook in Excel.
Read more about file size limits for Excel workbooks in SharePoint Online.

Remove data from worksheets

If you import data into Excel from the Power Query tab or the Excel Data tab, the workbook might have the same
data in an Excel table and in the Data Model. Large tables in Excel worksheets may make the core worksheet
contents more than 30 MB. Removing the table in Excel and keeping the data in the Data Model can greatly reduce
the core worksheet contents of the report.
When you import data into Excel, follow these tips:
In Power Quer y : Clear the Load to worksheet box.
The data is imported only into the Data Model, with no data in Excel worksheets.
From the Excel Data tab , if you previously checked Table in the import wizard: Go to Existing
Connections > click the connection > Only create connection . Delete the original table or tables created
during the initial import.
From the Excel Data tab : don’t check Table in the Impor t Data box.
Workbook Size Optimizer
If your workbook contains a data model, you can run the workbook size optimizer to reduce the size of your
workbook. Download Workbook Size Optimizer.

Related info
Create a memory-efficient Data Model
Use OneDrive for Business links in Power BI Desktop
 Intro to datasets across workspaces
9/9/2020 • 4 minutes to read • Edit Online

Business intelligence is a collaborative activity. It's important to establish standardized datasets that can be the
'one source of truth.' Then discovering and reusing those standardized datasets is key. When expert data modelers
in your organization create and share optimized datasets, report creators can start with those datasets to build
accurate reports. Then your organization has consistent data for making decisions, and a healthy data culture.

In Power BI, dataset creators can control who has access to their data by using the Build permission. Dataset
creators can also certify or promote datasets so others can discover them. That way, report authors know which
datasets are high quality and official, and they can use those datasets wherever they author in Power BI. Tenant
administrators have a new tenant setting to govern the use of datasets across workspaces.

Dataset sharing and the new workspace experience

Building reports based on datasets in different workspaces, and copying reports to different workspaces, are
tightly coupled with the new workspace experience:
In the service, when you open the dataset catalog from a new workspace experience, the dataset catalog shows
datasets that are in your My Workspace and in other new workspace experience workspaces.
When you open the dataset catalog from a classic workspace, you only see the datasets in that workspace, not
the ones in other workspaces.
In Power BI Desktop, you can publish Live Connect reports to different workspaces, as long as their datasets are
in new experience workspaces.
When copying reports across workspaces, the target workspace needs to be a new experience workspace.

Discover datasets
When building a report on top of an existing dataset, the first step is to connect to the dataset, either in the Power
BI service or Power BI Desktop. Read about discovering datasets from different workspaces
Copy a report
When you find a report you like, in a workspace or an app, you can make a copy of it, and then modify it to fit your
needs. You don't have to worry about creating the data model. That's already created for you. And it's much easier
to modify an existing report than it is to start from scratch. Read more about copying reports.

Build permission for datasets

With Build permission type, if you're a dataset creator you can determine who in your organization can build new
content on your datasets. People with Build permission can also build new content on the dataset outside Power BI,
such as Excel sheets via Analyze in Excel, XMLA, and export. Read more about the Build permission.

Promotion and certification

If you create datasets, when you create one that others can benefit from, you can make it easier for them to
discover it by promoting your dataset. You can also request that experts in your organization certify your dataset.

Licensing
The specific features and experiences built on shared dataset capabilities are licensed according to their existing
scenarios. For example:
In general, discovering and connecting to shared datasets is available to anyone – it is not a feature restricted to
Premium.
Users without a Pro license can only use datasets across workspaces for report authoring if those datasets
reside in the users' personal My Workspace or in a Premium-backed workspace. The same licensing restriction
applies whether they author reports in Power BI Desktop or in the Power BI service.
Copying reports between workspaces requires a Pro license.
Copying reports from an app requires a Pro license, as was required for organizational content packs.
Promoting and certifying datasets requires a Pro license.

Considerations and limitations

As an app publisher you have to make sure that your audience has access to datasets outside of the workspace.
Otherwise, users will encounter issues when interacting with your app: reports won’t open without dataset
access, and dashboard tiles will show as locked. Also, users won’t be able to open the app if the first item in its
navigation is a report without access to the dataset.
Building a report on top of a dataset in a different workspace requires the new workspace experience at both
ends: The report needs to be in a new workspace experience and the dataset needs to be in a new workspace
experience. You can only copy reports in a new workspace experience to another new workspace experience,
and not to classic workspaces or to My Workspace.
In a classic workspace, the dataset discovery experience only shows the datasets in that workspace.
By design, “Publish to web” doesn’t work for a report based on a shared dataset.
If two people are members of a workspace that is accessing a shared dataset, it's possible that only one of them
can see the related dataset in the workspace. Only people with at least Read access to the dataset can see the
shared dataset.

Next steps
Promote datasets
Certify datasets
Govern the use of datasets across workspaces
Questions? Try asking the Power BI Community
 Share a dataset
9/9/2020 • 2 minutes to read • Edit Online

As a creator of data models in Power BI Desktop, you're creating datasets that you can distribute in the Power BI
service. Then other report creators can use your datasets as a basis for their own reports. In this article, you learn
how to share your datasets. To learn how to give and remove access to your shared datasets, read about the Build
permission.

Steps to sharing your dataset

1. You start by creating a .pbix file with a data model in Power BI Desktop. If you're planning to offer this
dataset for others to build reports, you may not even design a report in the .pbix file.
A best practice is to save the .pbix file to a Microsoft 365 group.
2. Publish the .pbix file to a new workspace experience in the Power BI service.
Already, other members of this workspace can create reports in other workspaces based on this dataset. Use
the Manage Permissions option on the dataset in the workspace content list give additional users access to
the dataset.
3. You can also publish an app from this workspace. When you do, on the Permissions page, you specify who
has permissions and what they can do.

NOTE
If you select Entire organization , then no one in the organization will have Build permission. This issue is already
known. Instead, specify email addresses in Specific individuals or groups . If you want your entire organization to
have Build permission, specify an email alias for the entire organization.

4. Select Publish app , or Update app if it's already published.

Track your dataset usage
When you have a shared dataset in your workspace, you may need to know what reports in other workspaces are
based on it.
1. In the Datasets list view, select View related .

2. The Related content dialog box shows all related items. In this list, you see the related items in this
workspace and in Other workspaces .

Limitations and considerations

Things to keep in mind about sharing datasets:
When you share a dataset by managing permissions, by sharing reports or dashboards, or by publishing an
app, you're granting access to the entire dataset unless row-level security (RLS) limits their access. Report
authors may use capabilities that customize user experiences when viewing or interacting with reports, for
example hiding columns, limiting the actions on visuals, and others. These customized user experience do not
restrict what data users can access in the dataset. Use row-level security (RLS) in the dataset so that each
 person's credentials determine which data they can access.

Next steps
Use datasets across workspaces
Questions? Try asking the Power BI Community
 Build permission for shared datasets
9/9/2020 • 3 minutes to read • Edit Online

When you create a report in Power BI Desktop, the data in that report is stored in a data model. When you publish
your reports to the Power BI service, you're also publishing the data as a dataset. You can give others Build
permission for that report, so they can discover and reuse the dataset you've shared. This article explains how you
control access to the data by using the Build permission.
Build permission applies to datasets. When you give users Build permission, they can build new content on your
dataset, such as reports, dashboards, pinned tiles from Q&A, and Insights Discovery.
Users also need Build permissions to work with the data outside Power BI:
To export the underlying data.
To build new content on the dataset such as with Analyze in Excel.
To access the data via the XMLA endpoint.

Ways to give Build permission

You give Build permission for a dataset in a few different ways:
Members of a workspace with at least a Contributor role automatically have Build permission for datasets
in that workspace, and permission to copy a report.
Members of the workspace where the dataset resides can assign the permission to specific users or
security groups in the Permission center. If you're a member of the workspace, select More options (...)
next to a dataset > Manage Permissions .

That opens the Permission center for that dataset, where you can set and change permissions.
 An admin or member of the workspace where the dataset resides can decide during app publishing that
users with permission for the app also get Build permission for the underlying datasets. See Share a
dataset for details.
Say you have Reshare and Build permission on a dataset. When you share a report or dashboard built on
that dataset, you can specify that the recipients also get Build permission for the underlying dataset.

You can remove a person's Build permission for a dataset. If you do, they can still see the report built on the
shared dataset, but they can no longer edit it. See the next section for details.

Remove Build permission for a dataset

At some point, you may need to remove Build permission for some users of a shared dataset.
1. In a workspace, go to the Datasets list page.
2. Select More options (...) next to the dataset > Manage permission .
3. Select More options (...) next to a name > Remove build .

They can still see the report built on the shared dataset, but they can no longer edit it.
Remove Build permission for a dataset in an app
Say you've distributed an app from a workspace to a group of people. Later, you decide to remove access to the
app for some people. Removing their access to the app doesn't automatically remove their build and reshare
permissions. That's an extra step.
1. In a workspace list page, select Update app .
2. On the Permissions tab, select the X to delete the person or group.

3. Select Update app .

You see a message explaining that you need to go to Manage permissions to remove Build permission
for users with existing access.
4. Select Update .
5. In the workspace, go to the Datasets list page.
6. Select More options (...) next to the dataset > Manage permission .

7. Select More options (...) next to their name > Remove build .

They can still see the report built on the shared dataset, but they can no longer edit it.

More granular permissions

Power BI introduced Build permission in June 2019 as a complement to the existing permissions, Read and
Reshare. All users who already had Read permission for datasets via app permissions, sharing, or workspace
access at that time also got Build permission for those same datasets. They got Build permission automatically
because Read permission already granted them the right to build new content on top of the dataset, by using
Analyze in Excel or Export.
With this more granular Build permission, you can choose who can only view the content in the existing report or
dashboard and who can create content connected to the underlying datasets.
If your dataset is being used by a report outside the dataset workspace, you can't delete that dataset. Instead, you
see an error message.
You can remove Build permission. If you do, the people whose permissions you have revoked can still see the
report, but can no longer edit the report or export underlying data. Users with only read permission can still
export summarized data.

Next steps
Use datasets across workspaces
Questions? Try asking the Power BI Community
 Create reports based on datasets from different
workspaces
9/9/2020 • 2 minutes to read • Edit Online

Learn how you can create reports in your own workspaces based on datasets in other workspaces. To build a
report on top of an existing dataset, you can start from Power BI Desktop or from the Power BI service, in your My
Workspace or in a new workspace experience.
In the Power BI service: Get data > Published datasets .
In Power BI Desktop: Get data > Power BI datasets .

In both cases, the dataset discovery experience starts in this dialog box, Select a dataset to create a repor t . You
see all the datasets you have access to, regardless of where they are:

You notice the first one is labeled Promoted . We'll get to that in Find an endorsed dataset, later in this article.
The datasets you see in this list meet at least one of the following conditions:
The dataset is in one of the new workspace experience workspaces, and you're a member of that workspace. See
Considerations and limitations.
You have Build permission for the dataset, which is in a new workspace experience workspace.
The dataset is in your My Workspace.
 NOTE
If you're a free user, you only see datasets in your My Workspace, or datasets for which you have Build permission that are in
Premium-capacity workspaces.

When you click Create , you create a live connection to the dataset, and the report creation experience opens with
the full dataset available. You haven't made a copy of the dataset. The dataset still resides in its original location. You
can use all tables and measures in the dataset to build your own reports. Row-level security (RLS) restrictions on
the dataset are in effect, so you only see data you have permissions to see based on your RLS role.
You can save the report to the current workspace in the Power BI service, or publish the report to a workspace from
Power BI Desktop. Power BI automatically creates an entry in the list of datasets if the report is based on a dataset
outside of the workspace. The icon for this dataset is different from the icon for datasets in the workspace:
That way, members of the workspace can tell which reports and dashboards use datasets that are outside the
workspace. The entry shows information about the dataset, and a few select actions.

Find an endorsed dataset

THere are two different kinds of endorsed datasets. Dataset owners can promote a dataset that they recommend to
you. Also, the Power BI tenant admin can designate experts in your organization who can certify datasets for
everyone to use. Promoted and certified datasets both display badges that you see both when looking for a
dataset, and in the list of datasets in a workspace. The name of the person who certified a dataset is displayed in a
tooltip during the dataset discovery experience; hover over the Cer tified label and you see it.
In the Power BI service: Get data > Published datasets .
In Power BI Desktop: Get data > Power BI datasets .
In the Select a dataset dialog box, endorsed datasets top the list by default.

Next steps
Use datasets across workspaces
Questions? Try asking the Power BI Community
 Copy reports from other workspaces
9/9/2020 • 3 minutes to read • Edit Online

When you find a report you like in a workspace or an app, you can make a copy of it and save it to a different
workspace. Then you can modify your copy of the report, adding or deleting visuals and other elements. You don't
have to worry about creating the data model. It's already created for you. And it's much easier to modify an existing
report than it is to start from scratch. However, when you make an app from your workspace, sometimes you can't
publish your copy of the report in the app. See Considerations and limitations in the article "Use datasets across
workspaces" for details.

NOTE
To make a copy, you need a Pro license, even if the original report is in a workspace in a Premium capacity.

Save a copy of a report in a workspace

1. In a workspace, go to the Reports list view.

2. Under Actions , select Save a copy .

You only see the Save a copy icon if the report is in a new experience workspace, and you have Build
permission. Even if you have access to the workspace, you have to have Build permission for the dataset.
3. In Save a copy of this repor t , give the report a name and select the destination workspace.
 You can save the report to the current workspace or a different one in the Power BI service. You only see
workspaces that are new experience workspaces, in which you're a member.
4. Select Save .
Power BI automatically creates a copy of the report, and an entry in the list of datasets if the report is based
on a dataset outside of the workspace. The icon for this dataset is different from the icon for datasets in the
workspace:
That way, members of the workspace can tell which reports and dashboards use datasets that are outside
the workspace. The entry shows information about the dataset, and a few select actions.

See Your copy of the report in this article for more about the report and related dataset.

Copy a report in an app

1. In an app, open the report you want to copy.
2. In the menu bar, select More options (...) > Save a copy .
 You only see the Save a copy option if the report is in a new experience workspace, and you have Build
permission.
3. Give your report a name > Save .

Your copy is automatically saved to your My Workspace.

4. Select Go to repor t to open your copy.

Your copy of the report

When you save a copy of the report, you create a live connection to the dataset, and you can open the report
creation experience with the full dataset available.
You haven't made a copy of the dataset. The dataset still resides in its original location. You can use all tables and
measures in the dataset in your own report. Row-level security (RLS) restrictions on the dataset are in effect, so you
only see data you have permissions to see based on your RLS role.

View related datasets

When you have a report in one workspace based on a dataset in another workspace, you may need to know more
about the dataset it's based on.
1. In the Reports list view, select View related .

2. The Related content dialog box shows all related items. In this list, the dataset looks like any other. You
can't tell it resides in a different workspace. This issue is known.

Delete a report and its shared dataset

You may decide you no longer want the report and its associated shared dataset in workspace.
1. Delete the report. In the list of reports in the workspace, select the Delete icon.

2. In the list of datasets, you see the shared datasets don't have Delete icons. Refresh the page, or go to a
different page and return. The dataset will be gone. If not, check View related . It may be related to another
table in your workspace.
 NOTE
Deleting the shared dataset in this workspace doesn't delete the dataset. It just deletes the reference to it.

Next steps
Use datasets across workspaces
Questions? Try asking the Power BI Community
 Control the use of datasets across workspaces
9/9/2020 • 2 minutes to read • Edit Online

Using datasets across workspaces is a powerful way to drive data culture and data democratization within an
organization. Still, if you're a Power BI admin, sometimes you want to restrict the flow of information within your
Power BI tenant. With the tenant setting Use datasets across workspaces , you can restrict dataset reuse either
completely or partially per security groups.

If you turn off this setting, here are the effects on report creators:
The button to copy reports across workspaces isn't available.
In a report based on a shared dataset, the Edit repor t button isn't available.
In the Power BI service, the discovery experience only shows datasets in the current workspace.
In Power BI Desktop, the discovery experience only shows datasets from workspaces where you're a member.
In Power BI Desktop, if users open a .pbix file with a live connection to a dataset outside any workspaces they
are a member of, they see an error message asking them to connect to a different dataset.

Provide a link for the certification process

As a tenant admin, you can provide a URL for the Learn more link on the Endorsement setting page. This link
can go to documentation about your certification process. If you don't provide a destination for the Learn more
link, by default it points to the dataset certification article.
Next steps
Use datasets across workspaces
Questions? Try asking the Power BI Community
 Promote your dataset - Power BI
9/9/2020 • 2 minutes to read • Edit Online

Your Power BI report creators may now have access to many different datasets, so enterprises need to guide them
to the reliable, high-quality datasets. Power BI provides two ways to endorse datasets:
Promotion : As a dataset owner, you can promote your own datasets when they're ready for wide-spread
usage. Any workspace member with Write permissions can promote a dataset. There are no restrictions on who
can promote a dataset. Promotion supports the collaborative spread of datasets within organizations. This
article is about promoting your dataset.
Cer tification : You can request certification for a promoted dataset. A select group of users defined in the
Dataset Cer tification tenant admin setting decides which datasets to certify. See Certify datasets for details.

Promote a dataset
Your dataset needs to be in a new workspace experience workspace in the Power BI service when you're ready to
promote it.
1. Go to the list of datasets in the workspace.
2. Select More options (...), then select Settings .

3. Expand Endorsement > select Promoted .

4. Select Apply .

Request dataset certification

Your tenant admin has identified people in your organization who can certify datasets. You can ask that they certify
your dataset.
1. Give the certifier member permissions for the workspace where the dataset resides.
2. In the Endorsement section of Settings , Cer tified is grayed out.
3. Select the Learn more link.
Your Power BI tenant admin can configure the Learn more link to go to a specified location with details
about the certification process in your tenant. If they haven't customized the Learn more link, by default it
points to the dataset certification article.

Next steps
Read about Using datasets across workspaces
Questions? Try asking the Power BI Community
 Certify datasets - Power BI
9/9/2020 • 2 minutes to read • Edit Online

Your organization can certify datasets that are the authoritative source for critical information. These datasets are
featured prominently when report designers start creating a report and looking for reliable data. Certification can
be a highly selective process, with only the most valuable datasets getting certified. Power BI tenant admins have a
new setting, so they can tightly control who can certify datasets. Thus, admins can ensure that dataset certification
results in truly reliable and authoritative datasets designed for use across the organization.
Power BI users may now have access to many different datasets, so enterprises need to guide them to the reliable,
high-quality datasets. Power BI provides two ways to endorse datasets:
Promotion : Dataset owners and others in a workspace can promote their datasets when they're ready for
wide-spread usage. See Promote your dataset for details.
Cer tification : Dataset owners can request certification of a promoted dataset. A select group of users defined
in the Dataset Cer tification tenant admin setting decides which datasets to certify. The name of the person
who certified a dataset is displayed in a tooltip during the dataset discovery experience; hover over the
Cer tified label and you see it.

Certify a dataset
Your tenant admin can provide a URL for the Learn more link on the Endorsement setting page. They can link
to documentation about your certification process. If they don't provide a destination for the Learn more link, by
default it points to this article.

Being named someone who can certify datasets is clearly a big responsibility. When a dataset creator contacts you
about certifying a dataset, that's the beginning of your vetting process. When you're satisfied that a dataset merits
certification, here are your last steps.
1. The dataset owner needs to give you member permissions for the workspace where the dataset resides.
2. If your tenant admin has named you as someone who can certify datasets, the Cer tified option in the
Endorsement section of Settings for the dataset is available. Select Cer tified .
3. Select Apply .
Read more about how tenant admins control the use of datasets across workspaces.

Next steps
Read about Using datasets across workspaces
Questions? Try asking the Power BI Community
 Azure and Power BI
9/9/2020 • 3 minutes to read • Edit Online

With Azure services and Power BI , you can turn your data processing efforts into analytics and reports that
provide real-time insights into your business. Whether your data processing is cloud-based or on-premises,
straightforward, or complex, single-sourced or massively scaled, warehoused, or real-time, Azure and Power BI
have the built-in connectivity and integration to bring your business intelligence efforts to life.

Power BI has a multitude of Azure connections available, and the business intelligence solutions you can create
with those services are as unique as your business. You can connect as few as one Azure data source, or a handful,
then shape and refine your data to build customized reports.

Azure SQL Database and Power BI

You can start with a straightforward connection to an Azure SQL Database, and create reports to monitor the
progress of your business. Using the Power BI Desktop, you can create reports that identify trends and key
performance indicators that move your business forward.

There's plenty more information for you to learn about Azure SQL Database.

Transform, shape, and merge your cloud data

Do you have more complex data, and all sorts of sources? No problem. With Power BI Desktop and Azure
services, connections are just a tap of the Get Data dialog away. Within the same Query you can connect to your
Azure SQL Database , your Azure HDInsight data source, and your Azure Blob Storage (or Azure Table
Storage ), then select only the subsets within each that you need, and refine it from there.
You can create different reports for different audiences too, using the same data connections and even the same
Query. Just build a new report page, refine your visualizations for each audience, and watch it keep the business in
the know.

For more information, take a look at the following resources:

Azure SQL Database
Azure HDInsight
Azure Storage (Blob storage and Table storage)

Get complex (and ahead) using Azure Services and Power BI

You can expand as much as you need with Azure and Power BI. Harness multi-source data processing, make use of
massive real-time systems, use Stream Analyticsand Event Hubs, and coalesce your varied SaaS services into
business intelligence reports that give your business an edge.
Context insights with Power BI Embedded analytics
Embed stunning, interactive data visualizations in applications, websites, portals, and more, to take advantage of
your business data. With Power BI Embedded as a resource in Azure, you can easily embed interactive reports and
dashboards, so your users can enjoy consistent, high-fidelity experiences across devices. Power BI used with
embedding analytics is to help you through your journey from Data -> Knowledge -> Insights -> Actions.
Furthermore, you can extend the value of Power BI and Azure also by embedding analytics in your organization's
internal applications and portals.
There's lots of information about Power BI APIs in the Power BI Developer Portal.
For more information, see What is Power BI Embedded in Azure?.

Embed your Power BI data within your app

Embed stunning, interactive data visualizations in applications, websites, portals, and more, to showcase your
business data in context. Using Power BI Embedded in Azure, you can easily embed interactive reports and
dashboards, so your users can enjoy consistent, high-fidelity experiences across devices.

What could you do with Azure and Power BI?

There are all sorts of scenarios where Azure and Power BI can be combined - the possibilities and opportunities
are as unique as your business. For more information about Azure ser vices , check out this overview page, which
describes Data Analytics Scenarios using Azure , and learn how to transform your data sources into
intelligence that drives your business ahead.
 Power BI and Azure egress
9/9/2020 • 2 minutes to read • Edit Online

When using Power BI with Azure data sources, you can avoid Azure egress charges by making sure your Power BI
tenant is in the same region as your Azure data sources.
When your Power BI tenant is deployed in the same Azure region as you deploy your data sources, you do not incur
egress charges for scheduled refresh and DirectQuery interactions.

Determining where your Power BI tenant is located

To find out where your Power BI tenant is located, see the where is my Power BI tenant located article.
For Power BI Premium Multi-Geo customers, if your Power BI tenant is not in the optimal location for some of your
Azure-based data sources, you can deploy Power BI Premium Multi-Geo in the desired Azure region and benefit
from having your Power BI tenant and Azure data sources in the same Azure region.

Next steps
For more information about Power BI Premium or Multi-Geo, take a look at the following resources:
What is Microsoft Power BI Premium?
How to purchase Power BI Premium
Multi-Geo support for Power BI Premium (Preview)
Where is my Power BI tenant located?
Power BI Premium FAQ
 Azure SQL Data Warehouse with DirectQuery
9/9/2020 • 3 minutes to read • Edit Online

Azure SQL Data Warehouse with DirectQuery allows you to create dynamic reports based on data and metrics you
already have in Azure SQL Data Warehouse. With DirectQuery, queries are sent back to your Azure SQL Data
Warehouse in real time as you explore the data. Real-time queries, combined with the scale of SQL Data Warehouse
enables users to create dynamic reports in minutes against terabytes of data. In addition, the Build dashboards +
repor ts link allows users to create Power BI reports using their SQL Data Warehouse.
When using the SQL Data Warehouse connector:
Specify the fully qualified server name when connecting (see below for details)
Ensure firewall rules for the server are configured to "Allow access to Azure services"
Every action such as selecting a column or adding a filter will directly query the data warehouse
Tiles are set to refresh approximately every 15 minutes and refresh does not need to be scheduled. Refresh can
be adjusted in the Advanced settings when you connect.
Q&A isn't available for DirectQuery datasets
Schema changes aren't picked up automatically
These restrictions and notes may change as we continue to improve the experience. The steps to connect are
detailed below.

Build dashboards and reports in Power BI

IMPORTANT
We have been improving our connectivity to Azure SQL Data Warehouse. For the best experience to connect to your Azure
SQL Data Warehouse data source, use Power BI Desktop. Once you've built your model and report, you can publish it to the
Power BI service. The previously available direct connector for Azure SQL Data Warehouse in the Power BI service is no longer
available.

The easiest way to move between your SQL Data Warehouse and Power BI is to create reports in Power BI Desktop.
You can use the Build dashboards + repor ts button within the Azure portal.
1. To get started, download and install Power BI Desktop. See the get Power BI Desktop article for information
about downloading and installing, or go directly to the next step.
2. You can also click the Build dashboards + repor ts link to download Power BI Desktop.
Connecting through Power BI Desktop
You can connect to a SQL Data Warehouse using the Get Data button in Power BI Desktop.
1. Select the Get Data button from the Home menu.

2. Select More... to see all available data sources. From the window that appears, select Azure from the left
pane, then select Azure SQL Data Warehouse from the list of available connectors in the right pane.
3. In the window that appears, input your Server and optionally state the Database to which you want to
connect. You can also select your data connectivity mode: Import or DirectQuery. For real-time access to
information in your Azure SQL Data Warehouse, use DirectQuery.

4. For advanced options for the Azure SQL Data Warehouse connection, select the down arrow beside
Advanced options to display additional options for your connection.
The next section describes how to find parameter values for your connection.

Finding Parameter Values

Your fully qualified server name and database name can be found in the Azure portal. Note that SQL Data
Warehouse only has a presence in the Azure portal at this time.

NOTE
If your Power BI tenant is in the same region as the Azure SQL Data Warehouse there will be no egress charges. You can find
where your Power BI tenant is located using these instructions.

Single sign-on
After you publish an Azure SQL DirectQuery dataset to the service, you can enable single sign-on (SSO) using
Azure Active Directory (Azure AD) OAuth2 for your end users.
To enable SSO, go to settings for the dataset, open the Data Sources tab, and check the SSO box.
When the SSO option is enabled and your users access reports built atop the data source, Power BI sends their
authenticated Azure AD credentials in the queries to the Azure SQL database or data warehouse. This option
enables Power BI to respect the security settings that are configured at the data source level.
The SSO option takes affect across all datasets that use this data source. It does not affect the authentication
method used for import scenarios.

Next steps
About using DirectQuery in Power BI
What is Power BI?
Get Data for Power BI
Azure SQL Data Warehouse
More questions? Try the Power BI Community
 Azure SQL Database with DirectQuery
9/9/2020 • 2 minutes to read • Edit Online

Learn how you can connect directly to Azure SQL Database and create reports that use live data. You can keep your
data at the source and not in Power BI.
With DirectQuery, queries are sent back to your Azure SQL Database as you explore the data in the report view.
This experience is suggested for users who are familiar with the databases and entities they connect to.

IMPORTANT
This description assumes that Azure SQL database is not behind a VNET or has private link endpoint enabled.

Notes:
Specify the fully qualified server name when connecting (see below for more details).
Ensure firewall rules for the database are configured to "Allow access to Azure services."
Every action such as selecting a column or adding a filter will send a query back to the database.
Tiles are refreshed every hour (refresh does not need to be scheduled). You can adjust how often to refresh in
the Advanced settings when you connect.
Q&A is not available for DirectQuery datasets.
Schema changes are not picked up automatically.
These restrictions and notes may change as we continue to improve the experiences. The steps to connect are
detailed below.

IMPORTANT
We have been improving our connectivity to Azure SQL Database. For the best experience to connect to your Azure SQL
Database data source, use Power BI Desktop. Once you've built your model and report, you can publish it to the Power BI
service. The direct connector for Azure SQL Database in the Power BI service is now deprecated.

Power BI Desktop and DirectQuery

To connect to Azure SQL Database using DirectQuery, you must use Power BI Desktop. This approach provides
additional flexibility and capabilities. Reports created using Power BI Desktop can then be published to the Power BI
service. You can learn more about how to connect to Azure SQL Database using DirectQuery within Power BI
Desktop.

Find parameter values

You can find your fully qualified server name and database name in the Azure portal.
Single sign-on
After you publish an Azure SQL DirectQuery dataset to the service, you can enable single sign-on (SSO) using
Azure Active Directory (Azure AD) OAuth2 for your end users.
To enable SSO, go to settings for the dataset, open the Data Sources tab, and check the SSO box.

When the SSO option is enabled and your users access reports built atop the data source, Power BI sends their
authenticated Azure AD credentials in the queries to the Azure SQL database or data warehouse. This option
enables Power BI to respect the security settings that are configured at the data source level.
The SSO option takes affect across all datasets that use this data source. It does not affect the authentication
method used for import scenarios.
Next steps
Use DirectQuery in Power BI Desktop
What is Power BI?
Get data for Power BI
More questions? Try the Power BI community
 SQL Server Analysis Services live data in Power BI
9/9/2020 • 2 minutes to read • Edit Online

In Power BI, there are two ways you can connect to a live SQL Server Analysis Services server. In Get data , you can
connect to a SQL Server Analysis Services server, or you can connect to a Power BI Desktop file, or Excel workbook,
that already connects to an Analysis Services server. As a best practice, Microsoft strongly recommends using
Power BI Desktop because of the richness of the toolset and the ability to maintain a backup copy of the Power BI
Desktop file locally.

IMPORTANT
In order to connect to a live Analysis Services server, an On-premises data gateway must be installed and configured by
an administrator. For more information, see On-premises data gateway.
When you use the gateway, your data remains on-premises. The reports you create based on that data are saved in the
Power BI service.
Q&A natural language querying is in preview for Analysis Services live connections.

To connect to a model from Get data

1. In My Workspace , select Get data . You can also change to a group workspace, if one is available.

2. Select Databases & More .

3. Select SQL Ser ver Analysis Ser vices > Connect .

4. Select a server. If you don't see any servers listed here, it means either a gateway, and data source, are not
configured, or your account is not listed in the Users tab of the data source, in the gateway. Check with your
administrator.
5. Select the model you want to connect to. This could be either Tabular or Multidimensional.
After you connect to the model, it will appear in your Power BI site in My Workspace/Datasets . If you were
switched to a group workspace, then the dataset will appear within the group.

Dashboard tiles
If you pin visuals from a report to the dashboard, the pinned tiles are automatically refreshed every 10 minutes. If
the data in your on-premises Analysis Services server is updated, the tiles will get auto-updated after 10 minutes.

Common Issues
Cannot load the model schema error - This error occurs when the user connecting to SSAS does not have
access to the SSAS database, cube and model.

Next steps
On-premises data gateway
Manage Analysis Services data sources
Troubleshooting the On-premises data gateway
More questions? Try the Power BI Community
 Data refresh in Power BI
9/9/2020 • 26 minutes to read • Edit Online

Power BI enables you to go from data to insight to action quickly, yet you must make sure the data in your
Power BI reports and dashboards is recent. Knowing how to refresh the data is often critical in delivering
accurate results.
This article describes the data refresh features of Power BI and their dependencies at a conceptual level. It also
provides best practices and tips to avoid common refresh issues. The content lays a foundation to help you
understand how data refresh works. For targeted step-by-step instructions to configure data refresh, refer to the
tutorials and how-to guides listed in the Next steps section at the end of this article.

Understanding data refresh

Whenever you refresh data, Power BI must query the underlying data sources, possibly load the source data into
a dataset, and then update any visualizations in your reports or dashboards that rely on the updated dataset. The
entire process consists of multiple phases, depending on the storage modes of your datasets, as explained in the
following sections.
To understand how Power BI refreshes your datasets, reports, and dashboards, you must be aware of the
following concepts:
Storage modes and dataset types : The storage modes and dataset types that Power BI supports have
different refresh requirements. You can choose between re-importing data into Power BI to see any changes
that occurred or querying the data directly at the source.
Power BI refresh types : Regardless of dataset specifics, knowing the various refresh types can help you
understand where Power BI might spend its time during a refresh operation. And combining these details
with storage mode specifics helps to understand what exactly Power BI performs when you select Refresh
Now for a dataset.
Storage modes and dataset types
A Power BI dataset can operate in one of the following modes to access data from a variety of data sources. For
more information, see Storage mode in Power BI Desktop.
Import mode
DirectQuery mode
LiveConnect mode
Push mode
The following diagram illustrates the different data flows, based on storage mode. The most significant point is
that only Import mode datasets require a source data refresh. They require refresh because only this type of
dataset imports data from its data sources, and the imported data might be updated on a regular or ad-hoc
basis. DirectQuery datasets and datasets in LiveConnect mode to Analysis Services don't import data; they
query the underlying data source with every user interaction. Datasets in push mode don't access any data
sources directly but expect you to push the data into Power BI. Dataset refresh requirements vary depending on
the storage mode/dataset type.
Datasets in Import mode
Power BI imports the data from the original data sources into the dataset. Power BI report and dashboard
queries submitted to the dataset return results from the imported tables and columns. You might consider such
a dataset a point-in-time copy. Because Power BI copies the data, you must refresh the dataset to fetch changes
from the underlying data sources.
Because Power BI caches the data, Import mode dataset sizes can be substantial. Refer to the following table for
maximum dataset sizes per capacity. Stay well below the maximum dataset sizes to avoid refresh issues that
might occur if your datasets require more than the maximum available resources during a refresh operation.

C A PA C IT Y T Y P E M A XIM UM DATA SET SIZ E

Shared, A1, A2, or A3 1 GB

A4 or P1 3 GB

A5 or P2 6 GB

A6 or P3 10 GB

Datasets in DirectQuery/LiveConnect mode

Power BI does not import data over connections that operate in DirectQuery/LiveConnect mode. Instead, the
dataset returns results from the underlying data source whenever a report or dashboard queries the dataset.
Power BI transforms and forwards the queries to the data source.
Although DirectQuery mode and LiveConnect mode are similar in that Power BI forwards the queries to the
source, it is important to note that Power BI does not have to transform queries in LiveConnect mode. The
queries go directly to the Analysis Services instance hosting the database without consuming resources on
shared capacity or a Premium capacity.
Because Power BI does not import the data, you don't need to run a data refresh. However, Power BI still
performs tile refreshes and possibly report refreshes, as the next section on refresh types explains. A tile is a
report visual pinned to a dashboard, and dashboard tile refreshes happen about every hour so that the tiles
show recent results. You can change the schedule in the dataset settings, as in the screenshot below, or force a
dashboard update manually by using the Refresh Now option.

NOTE
The Scheduled cache refresh section of the Datasets tab is not available for datasets in import mode. These datasets
don't require a separate tile refresh because Power BI refreshes the tiles automatically during each scheduled or on-
demand data refresh.

Push datasets
Push datasets don't contain a formal definition of a data source, so they don't require you to perform a data
refresh in Power BI. You refresh them by pushing your data into the dataset through an external service or
process, such as Azure Stream Analytics. This is a common approach for real-time analytics with Power BI. Power
BI still performs cache refreshes for any tiles used on top of a push dataset. For a detailed walkthrough, see
Tutorial: Stream Analytics and Power BI: A real-time analytics dashboard for streaming data.

NOTE
Push Mode has several limitations as documented in Power BI REST API limitations.

Power BI refresh types

A Power BI refresh operation can consist of multiple refresh types, including data refresh, OneDrive refresh,
refresh of query caches, tile refresh, and refresh of report visuals. While Power BI determines the required
refresh steps for a given dataset automatically, you should know how they contribute to the complexity and
duration of a refresh operation. For a quick reference, refer to the following table.

O N EDRIVE
STO RA GE M O DE DATA REF RESH REF RESH Q UERY C A C H ES T IL E REF RESH REP O RT VISUA L S

Import Scheduled and Yes, for If enabled on Automatically No

on-demand connected Premium and on-demand
datasets capacity

DirectQuery Not applicable Yes, for If enabled on Automatically No

connected Premium and on-demand
datasets capacity
 O N EDRIVE
STO RA GE M O DE DATA REF RESH REF RESH Q UERY C A C H ES T IL E REF RESH REP O RT VISUA L S

LiveConnect Not applicable Yes, for If enabled on Automatically Yes

connected Premium and on-demand
datasets capacity

Push Not applicable Not applicable Not practical Automatically No

and on-demand

Data refresh
For Power BI users, refreshing data typically means importing data from the original data sources into a dataset,
either based on a refresh schedule or on-demand. You can perform multiple dataset refreshes daily, which might
be necessary if the underlying source data changes frequently. Power BI limits datasets on shared capacity to
eight daily refreshes. If the dataset resides on a Premium capacity, you can schedule up to 48 refreshes per day
in the dataset settings. For more information, see Configure scheduled refresh later in this article. Datasets on a
Premium capacity with the XMLA endpoint enabled for read-write support unlimited refresh operations when
configured programmatically with TMSL or PowerShell.
It is also important to call out that the shared-capacity limitation for daily refreshes applies to both scheduled
refreshes and API refreshes combined. You can also trigger an on-demand refresh by selecting Refresh Now in
the dataset menu, as the following screenshot depicts. On-demand refreshes are not included in the refresh
limitation. Also note that datasets on a Premium capacity don't impose limitations for API refreshes. If you are
interested in building your own refresh solution by using the Power BI REST API, see Datasets - Refresh Dataset.

NOTE
Data refreshes must complete in less than 2 hours on shared capacity. If your datasets require longer refresh operations,
consider moving the dataset onto a Premium capacity. On Premium, the maximum refresh duration is 5 hours.

OneDrive refresh
If you created your datasets and reports based on a Power BI Desktop file, Excel workbook, or comma separated
value (.csv) file on OneDrive or SharePoint Online, Power BI performs another type of refresh, known as
OneDrive refresh. For more information, see Get data from files for Power BI.
Unlike a dataset refresh during which Power BI imports data from a data source into a dataset, OneDrive refresh
synchronizes datasets and reports with their source files. By default, Power BI checks about every hour if a
dataset connected to a file on OneDrive or SharePoint Online requires synchronization.
Power BI performs refresh based on an item ID in OneDrive, so be thoughtful when considering updates versus
replacement. When you set a OneDrive file as the data source, Power BI references the item ID of the file when it
performs the refresh. Consider the following scenario: you have a master file A and a production copy of that file
B, and you configure OneDrive refresh for file B. If you then copy file A over file B, the copy operation deletes the
old file B and creates a new file B with a different item ID, which breaks OneDrive refresh. To avoid that situation,
you can instead upload and replace file B, which keeps its same item ID.
You can move the file to another location (using drag and drop, for example) and refresh will continue to work
because Power BI still knows the file ID. However, if you copy that file to another location, a new instance of the
file and a new fileID is created. Therefore, your Power BI file reference is no longer valid and refresh will fail.

NOTE
It can take Power BI up to 60 minutes to refresh a dataset, even once the sync has completed on your local machine and
after you've used Refresh now in the Power BI service.

To review past synchronization cycles, check the OneDrive tab in the refresh history. The following screenshot
shows a completed synchronization cycle for a sample dataset.

As the above screenshot shows, Power BI identified this OneDrive refresh as a Scheduled refresh, but it is not
possible to configure the refresh interval. You can only deactivate OneDrive refresh in the dataset's settings.
Deactivating refresh is useful if you don't want your datasets and reports in Power BI to pick up any changes
from the source files automatically.
Note that the dataset settings page only shows the OneDrive Credentials and OneDrive refresh sections if
the dataset is connected to a file in OneDrive or SharePoint Online, as in the following screenshot. Datasets that
are not connected to sources file in OneDrive or SharePoint Online don't show these sections.
If you disable OneDrive refresh for a dataset, you can still synchronize your dataset on-demand by selecting
Refresh Now in the dataset menu. As part of the on-demand refresh, Power BI checks if the source file on
OneDrive or SharePoint Online is newer than the dataset in Power BI and synchronizes the dataset if this is the
case. The Refresh histor y lists these activities as on-demand refreshes on the OneDrive tab.
Keep in mind that OneDrive refresh does not pull data from the original data sources. OneDrive refresh simply
updates the resources in Power BI with the metadata and data from the .pbix, .xlsx, or .csv file, as the following
diagram illustrates. To ensure that the dataset has the most recent data from the data sources, Power BI also
triggers a data refresh as part of an on-demand refresh. You can verify this in the Refresh histor y if you switch
to the Scheduled tab.

If you keep OneDrive refresh enabled for a OneDrive or SharePoint Online-connected dataset and you want to
perform data refresh on a scheduled basis, make sure you configure the schedule so that Power BI performs the
data refresh after the OneDrive refresh. For example, if you created your own service or process to update the
source file in OneDrive or SharePoint Online every night at 1 am, you could configure scheduled refresh for 2:30
am to give Power BI enough time to complete the OneDrive refresh before starting the data refresh.
Refresh of query caches
If your dataset resides on a Premium capacity, you might be able to improve the performance of any associated
reports and dashboards by enabling query caching, as in the following screenshot. Query caching instructs the
Premium capacity to use its local caching service to maintain query results, avoiding having the underlying data
source compute those results. For more information, see Query caching in Power BI Premium.

Following a data refresh, however, previously cached query results are no longer valid. Power BI discards these
cached results and must rebuild them. For this reason, query caching might not be as beneficial for reports and
dashboards associated with datasets that you refresh very often, such as 48 times per day.
Tile refresh
Power BI maintains a cache for every tile visual on your dashboards and proactively updates the tile caches
when data changes. In other words, tile refresh happens automatically following a data refresh. This is true for
both, scheduled and on-demand refresh operations. You can also force a tile refresh by selecting More options
(...) in the upper right of a dashboard and selecting Refresh dashboard tiles .

Because it happens automatically, you can consider tile refresh an intrinsic part of data refresh. Among other
things, you might notice that the refresh duration increases with the number of tiles. The tile refresh overhead
can be significant.
By default, Power BI maintains a single cache for every tile, but if you use dynamic security to restrict data access
based on user roles, as covered in the article row-level security (RLS) with Power BI, then Power BI must
maintain a cache for every role and every tile. The number of tile caches multiplies by the number of roles.
The situation can get even more involved if your dataset uses a live connection to an Analysis Services data
model with RLS, as highlighted in the tutorial Dynamic row level security with Analysis services tabular model.
In this situation, Power BI must maintain and refresh a cache for every tile and every user who ever viewed the
dashboard. It is not uncommon that the tile refresh portion of such a data refresh operation far exceeds the time
it takes to fetch the data from the source. For more details around tile refresh, see Troubleshooting tile errors.
Refresh of report visuals
This refresh process is less important because it is only relevant for live connections to Analysis Services. For
these connections, Power BI caches the last state of the report visuals so that when you view the report again,
Power BI does not have to query the Analysis Services tabular model. When you interact with the report, such as
by changing a report filter, Power BI queries the tabular model and updates the report visuals automatically. If
you suspect that a report is showing stale data, you can also select the Refresh button of the report to trigger a
refresh of all report visuals, as the following screenshot illustrates.

Review data infrastructure dependencies

Regardless of storage modes, no data refresh can succeed unless the underlying data sources are accessible.
There are three main data access scenarios:
A dataset uses data sources that reside on-premises
A dataset uses data sources in the cloud
A dataset uses data from both, on-premises and cloud sources
Connecting to on-premises data sources
If your dataset uses a data source that Power BI can't access over a direct network connection, you must
configure a gateway connection for this dataset before you can enable a refresh schedule or perform an on-
demand data refresh. For more information about data gateways and how they work, see What are on-premises
data gateways?
You have the following options:
Choose an enterprise data gateway with the required data source definition
Deploy a personal data gateway

NOTE
You can find a list of data source types that require a data gateway in the article Manage your data source -
Import/Scheduled Refresh.

Using an enterprise data gateway

Microsoft recommends using an enterprise data gateway instead of a personal gateway to connect a dataset to
an on-premises data source. Make sure the gateway is properly configured, which means the gateway must
have the latest updates and all required data source definitions. A data source definition provides Power BI with
the connection information for a given source, including connection endpoints, authentication mode, and
credentials. For more information about managing data sources on a gateway, see Manage your data source -
import/scheduled refresh.
Connecting a dataset to an enterprise gateway is relatively straightforward if you are a gateway administrator.
With admin permissions, you can promptly update the gateway and add missing data sources, if necessary. In
fact, you can add a missing data source to your gateway straight from the dataset settings page. Expand the
toggle button to view the data sources and select the Add to gateway link, as in the following screenshot. If
you are not a gateway administrator, on the other hand, you must contact a gateway admin to add the required
data source definition.

NOTE
Only gateway admins can add data sources to a gateway. Also make sure your gateway admin adds your user account to
the list of users with permissions to use the data source. The dataset settings page only lets you select an enterprise
gateway with a matching data source that you have permission to use.

Make sure you map the correct data source definition to your data source. As the above screenshot illustrates,
gateway admins can create multiple definitions on a single gateway connecting to the same data source, each
with different credentials. In the example shown, a dataset owner in the Sales department would choose the
AdventureWorksProducts-Sales data source definition while a dataset owner in the Support department would
map the dataset to the AdventureWorksProducts-Support data source definition. If the names of the data source
definition aren't intuitive, contact your gateway admin to clarify which definition to pick.

NOTE
A dataset can only use a single gateway connection. In other words, it is not possible to access on-premises data sources
across multiple gateway connections. Accordingly, you must add all required data source definitions to the same gateway.
Deploying a personal data gateway
If you have no access to an enterprise data gateway and you're the only person who manages datasets so you
don't need to share data sources with others, you can deploy a data gateway in personal mode. In the Gateway
connection section, under You have no personal gateways installed , select Install now . The personal
data gateway has several limitations as documented in On-premises data gateway (personal mode).
Unlike for an enterprise data gateway, you don't need to add data source definitions to a personal gateway.
Instead, you manage the data source configuration by using the Data source credentials section in the
dataset settings, as the following screenshot illustrates.

Accessing cloud data sources

Datasets that use cloud data sources, such as Azure SQL DB, don't require a data gateway if Power BI can
establish a direct network connection to the source. Accordingly, you can manage the configuration of these data
sources by using the Data source credentials section in the dataset settings. As the following screenshot
shows, you don't need to configure a gateway connection.
 NOTE
Each user can only have one set of credentials per data source, across all of the data sets they own, regardless of the
workspaces where the datasets reside.

Accessing on-premises and cloud sources in the same source query

A dataset can get data from multiple sources, and these sources can reside on-premises or in the cloud.
However, a dataset can only use a single gateway connection, as mentioned earlier. While cloud data sources
don't necessarily require a gateway, a gateway is required if a dataset connects to both on-premises and cloud
sources in a single mashup query. In this scenario, Power BI must use a gateway for the cloud data sources as
well. The following diagram illustrates how such a dataset accesses its data sources.
 NOTE
If a dataset uses separate mashup queries to connect to on-premises and cloud sources, Power BI uses a gateway
connection to reach the on-premises sources and a direct network connection to the cloud sources. If a mashup query
merges or appends data from on-premises and cloud sources, Power BI switches to the gateway connection even for the
cloud sources.

Power BI datasets rely on Power Query to access and retrieve source data. The following mashup listing shows a
basic example of a query that merges data from an on-premises source and a cloud source.

Let

OnPremSource = Sql.Database("on-premises-db", "AdventureWorks"),

CloudSource = Sql.Databases("cloudsql.database.windows.net", "AdventureWorks"),

TableData1 = OnPremSource{[Schema="Sales",Item="Customer"]}[Data],

TableData2 = CloudSource {[Schema="Sales",Item="Customer"]}[Data],

MergedData = Table.NestedJoin(TableData1, {"BusinessEntityID"}, TableData2, {"BusinessEntityID"},

"MergedData", JoinKind.Inner)

in

MergedData

There are two options to configure a data gateway to support merging or appending data from on-premises
and cloud sources:
Add a data source definition for the cloud source to the data gateway in addition to the on-premises data
sources.
Enable the checkbox Allow user's cloud data sources to refresh through this gateway cluster .

If you enable the checkbox Allow user's cloud data sources to refresh through this gateway cluster in
the gateway configuration , as in the screenshot above, Power BI can use the configuration that the user
defined for the cloud source under Data source credentials in the dataset settings. This can help to lower the
gateway configuration overhead. On the other hand, if you want to have greater control over the connections
that your gateway establishes, you should not enable this checkbox. In this case, you must add an explicit data
source definition for every cloud source that you want to support to your gateway. It is also possible to enable
the checkbox and add explicit data source definitions for your cloud sources to a gateway. In this case, the
gateway uses the data source definitions for all matching sources.
Configuring query parameters
The mashup or M queries you create by using Power Query can vary in complexity from trivial steps to
parameterized constructs. The following listing shows a small sample mashup query that uses two parameters
called SchemaName and TableName to access a given table in an AdventureWorks database.

let

Source = Sql.Database("SqlServer01", "AdventureWorks"),

TableData = Source{[Schema=SchemaName,Item=TableName]}[Data]

in

TableData

NOTE
Query parameters are only supported for Import mode datasets. DirectQuery/LiveConnect mode does not support
query parameter definitions.

To ensure that a parameterized dataset accesses the correct data, you must configure the mashup query
parameters in the dataset settings. You can also update the parameters programmatically by using the Power BI
REST API. The following screenshot shows the user interface to configure the query parameters for a dataset
that uses the above mashup query.

Refresh and dynamic data sources

A dynamic data source is a data source in which some or all of the information required to connect cannot be
determined until Power Query runs its query, because the data is generated in code or returned from another
data source. Examples include: the instance name and database of a SQL Server database; the path of a CSV file;
or the URL of a web service.
In most cases, Power BI datasets that use dynamic data sources cannot be refreshed in the Power BI service.
There are a few exceptions in which dynamic data sources can be refreshed in the Power BI service, such as
when using the RelativePath and Query options with the Web.Contents M function. Queries that reference Power
Query parameters can also be refreshed.
To determine whether your dynamic data source can be refreshed, open the Data Source Settings dialog in
Power Quer y Editor , and then select Data Sources In Current File . In the window that appears, look for the
following warning message, as shown in the following image:

Some data sources may not be listed because of hand-authored queries.

If that warning is present in the Data Source Settings dialog that appears, then a dynamic data source that
cannot be refreshed in the Power BI service is present.

Configure scheduled refresh

Establishing connectivity between Power BI and your data sources is by far the most challenging task in
configuring a data refresh. The remaining steps are relatively straightforward and include setting the refresh
schedule and enabling refresh failure notifications. For step-by-step instructions, see the how-to guide
Configuring scheduled refresh.
Setting a refresh schedule
The Scheduled refresh section is where you define the frequency and time slots to refresh a dataset. As
mentioned earlier, you can configure up to eight daily time slots if your dataset is on shared capacity, or 48 time
slots on Power BI Premium. The following screenshot shows a refresh schedule on a twelve-hour interval.
Having configured a refresh schedule, the dataset settings page informs you about the next refresh time, as in
the screenshot above. If you want to refresh the data sooner, such as to test your gateway and data source
configuration, perform an on-demand refresh by using the Refresh Now option in the dataset menu in the nav
pane. On-demand refreshes don't affect the next scheduled refresh time.
Note also that the configured refresh time might not be the exact time when Power BI starts the next scheduled
process. Power BI starts scheduled refreshes on a best effort basis. The target is to initiate the refresh within 15
minutes of the scheduled time slot, but a delay of up to one hour can occur if the service can't allocate the
required resources sooner.

NOTE
Power BI deactivates your refresh schedule after four consecutive failures or when the service detects an unrecoverable
error that requires a configuration update, such as invalid or expired credentials. It is not possible to change the
consecutive failures threshold.

Getting refresh failure notifications

By default, Power BI sends refresh failure notifications through email to the dataset owner so that the owner can
act in a timely manner should refresh issues occur. Power BI also sends you a notification when the service
disables your schedule due to consecutive failures. Microsoft recommends that you leave the checkbox Send
refresh failure notification emails to me enabled.
It is also a good idea to specify additional recipients by using the Email these users when the refresh fails
textbox. The specified recipients receive refresh failure notifications in addition to the dataset owner. This might
be a colleague taking care of your datasets while you are on vacation. It could also be the email alias of your
support team taking care of refresh issues for your department or organization. Sending refresh failure
notifications to others in addition to the dataset owner is helpful to ensure issues get noticed and addressed in a
timely manner.
Note that Power BI not only sends notifications on refresh failures but also when the service pauses a scheduled
refresh due to inactivity. After two months, when no user has visited any dashboard or report built on the
dataset, Power BI considers the dataset inactive. In this situation, Power BI sends an email message to the dataset
owner indicating that the service paused the refresh schedule for the dataset. See the following screenshot for
an example of such a notification.

To resume scheduled refresh, visit a report or dashboard built using this dataset or manually refresh the dataset
using the Refresh Now option.
Checking refresh status and history
In addition to failure notifications, it is a good idea to check your datasets periodically for refresh errors. A quick
way is to view the list of datasets in a workspace. Datasets with errors show a small warning icon. Select the
warning icon to obtain additional information, as in the following screenshot. For more information about
troubleshooting specific refresh errors, see Troubleshooting refresh scenarios.
The warning icon helps to indicate current dataset issues, but it is also a good idea to check the refresh history
occasionally. As the name implies, the refresh history enables you to review the success or failure status of past
synchronization cycles. For example, a gateway administrator might have updated an expired set of database
credentials. As you can see in the following screenshot, the refresh history shows when an affected refresh
started working again.
 NOTE
You can find a link to display the refresh history in the dataset settings. You can also retrieve the refresh history
programmatically by using the Power BI REST API. By using a custom solution, you can monitor the refresh history of
multiple datasets in a centralized way.

Automatic page refresh

Automatic page refresh works at a report page level, and allows report authors to set a refresh interval for
visuals in a page that is only active when the page is being consumed. Automatic page refresh is only available
for DirectQuery data sources. The minimum refresh interval depends on which type of workspace the report is
published in, and the capacity admin settings for Premium workspaces and embedded workspaces.
Learn more about automatic page refresh in the automatic page refresh article.

Best practices
Checking the refresh history of your datasets regularly is one of the most important best practices you can
adopt to ensure that your reports and dashboards use current data. If you discover issues, address them
promptly and follow up with data source owners and gateway administrators if necessary.
In addition, consider the following recommendations to establish and maintain reliable data refresh processes
for your datasets:
Schedule your refreshes for less busy times, especially if your datasets are on Power BI Premium. If you
distribute the refresh cycles for your datasets across a broader time window, you can help to avoid peaks that
might otherwise overtax available resources. Delays starting a refresh cycle are an indicator of resource
overload. If a Premium capacity is completely exhausted, Power BI might even skip a refresh cycle.
Keep refresh limits in mind. If the source data changes frequently or the data volume is substantial, consider
using DirectQuery/LiveConnect mode instead of Import mode if the increased load at the source and the
impact on query performance are acceptable. Avoid constantly refreshing an Import mode dataset. However,
DirectQuery/LiveConnect mode has several limitations, such as a one-million-row limit for returning data
and a 225 seconds response time limit for running queries, as documented in Use DirectQuery in Power BI
Desktop. These limitations might require you to use Import mode nonetheless. For very large data volumes,
consider the use of aggregations in Power BI.
Verify that your dataset refresh time does not exceed the maximum refresh duration. Use Power BI Desktop
to check the refresh duration. If it takes more than 2 hours, consider moving your dataset to Power BI
Premium. Your dataset might not be refreshable on shared capacity. Also consider using incremental refresh
in Power BI Premium for datasets that are larger than 1GB or take several hours to refresh.
Optimize your datasets to include only those tables and columns that your reports and dashboards use.
Optimize your mashup queries and, if possible, avoid dynamic data source definitions and expensive DAX
calculations. Specifically avoid DAX functions that test every row in a table because of the high memory
consumption and processing overhead.
Apply the same privacy settings as in Power BI Desktop to ensure that Power BI can generate efficient source
queries. Keep in mind that Power BI Desktop does not publish privacy settings. You must manually reapply
the settings in the data source definitions after publishing your dataset.
Limit the number of visuals on your dashboards, especially if you use row-level security (RLS). As explained
earlier in this article, an excessive number of dashboard tiles can significantly increase the refresh duration.
Use a reliable enterprise data gateway deployment to connect your datasets to on-premises data sources. If
you notice gateway-related refresh failures, such as gateway unavailable or overloaded, follow up with
gateway administrators to either add additional gateways to an existing cluster or deploy a new cluster (scale
up versus scale out).
 Use separate data gateways for Import datasets and DirectQuery/LiveConnect datasets so that the data
imports during scheduled refresh don't impact the performance of reports and dashboards on top of
DirectQuery/LiveConnect datasets, which query the data sources with each user interaction.
Ensure that Power BI can send refresh failure notifications to your mailbox. Spam filters might block the email
messages or move them into a separate folder where you might not notice them immediately.

Next steps
Configuring scheduled refresh
Tools for troubleshooting refresh issues
Troubleshooting refresh scenarios
More questions? Try asking the Power BI Community
 Configure scheduled refresh
9/9/2020 • 4 minutes to read • Edit Online

NOTE
After two months of inactivity, scheduled refresh on your dataset is paused. For more information, see Scheduled refresh
later in this article.

This article describes the options available for scheduled refresh for the On-premises data gateway (personal
mode) and the On-premises data gateway. You specify refresh options in the following areas of the Power BI
service: Gateway connection , Data source credentials , and Scheduled refresh . We'll look at each in turn.
For more information about data refresh, including limitations on refresh schedules, see Data refresh.
To get to the Scheduled refresh screen:
1. In the navigation pane, under Datasets , select More options (...) next to a dataset listed .
2. Select Schedule Refresh .
Gateway connection
You see different options here depending on whether you have a personal, or enterprise, gateway online and
available.
If no gateway is available, you see Gateway connection disabled. You also see a message indicating how to
install the personal gateway.

If you have a personal gateway configured and it's online, it's available to select. It shows offline if it's not
available.

You can also select the enterprise gateway if one is available for you. You only see an enterprise gateway
available if your account is listed in the Users tab of the data source configured for a given gateway.

Data source credentials

Power BI Gateway - Personal
If you are using the personal gateway to refresh data, you must supply the credentials to connect to the back-
end data source. If you connected to a content pack from an online service, the credentials you entered to
connect are carried over for scheduled refresh.

You're only required to sign in to a data source the first time you use refresh on that dataset. Once entered, those
credentials are retained with the dataset.
 NOTE
For some authentication methods, if the password you use to sign into a data source expires or is changed, you need to
change it for the data source in Data source credentials too.

When things go wrong, the problem usually has something to do with either the gateway being offline because
it couldn't sign in to Windows and start the service, or Power BI couldn't sign in to the data sources to query for
updated data. If refresh fails, check the dataset settings. If the gateway service is offline, Status is where you see
the error. If Power BI can't sign into the data sources, you see an error in Data Source Credentials.
On-premises data gateway
If you are using the On-premises data gateway to refresh data, you do not need to supply credentials, as they
are defined for the data source by the gateway administrator.

NOTE
When connecting to on-premises SharePoint for data refresh, Power BI supports only Anonymous, Basic, and Windows
(NTLM/Kerberos) authentication mechanisms. Power BI does not support ADFS or any Forms-Based Authentication
mechanisms for data refresh of on-premises SharePoint data sources.

Scheduled refresh
The Scheduled refresh section is where you define the frequency and time slots to refresh the dataset. Some
data sources do not require a gateway to be configurable for refresh; other data sources require a gateway.
Set the Keep your data up to date slider to On to configure the settings.

NOTE
The target is to initiate the refresh within 15 minutes of the scheduled time slot, but a delay of up to one hour can occur if
the service can't allocate the required resources sooner.
 NOTE
After two months of inactivity, scheduled refresh on your dataset is paused. A dataset is considered inactive when no user
has visited any dashboard or report built on the dataset. At that time, the dataset owner is sent an email indicating the
scheduled refresh is paused. The refresh schedule for the dataset is then displayed as disabled . To resume scheduled
refresh, simply revisit any dashboard or report built on the dataset.

What's supported?
NOTE
Scheduled refresh will also get disabled automatically after four consecutive errors.

Certain datasets are supported against different gateways for scheduled refresh. Here is a reference to
understand what is available.
Power BI Gateway - Personal
Power BI Desktop
All online data sources shown in Power BI Desktop's Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop's Get Data and Query Editor except for Hadoop file
(HDFS) and Microsoft Exchange.
Excel
All online data sources shown in Power Query.
All on-premises data sources shown in Power Query except for Hadoop file (HDFS) and Microsoft Exchange.
All online data sources shown in Power Pivot.
All on-premises data sources shown in Power Pivot except for Hadoop file (HDFS) and Microsoft Exchange.
 NOTE
In Excel 2016 and later, Power Query is listed on the Data section of the ribbon, under Get & Transform Data .

Power BI Gateway
For information about supported data sources, see Power BI data sources.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway.
Take a look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal

Next steps
Data refresh in Power BI
Power BI Gateway - Personal
On-premises data gateway (personal mode)
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Refresh summaries for Power BI
9/9/2020 • 4 minutes to read • Edit Online

The Power BI refresh summaries page, found in the Power BI Admin portal, provides control and insight into your
refresh schedules, capacities, and potential refresh schedule overlaps. You can use the refresh summaries page to
determine whether you should adjust refresh schedules, learn error codes associated with refresh issues, and
properly manage your data refresh scheduling.
The refresh summaries page has two views:
Histor y - displays the refresh summary history for Power BI Premium capacities for which you are an
administrator.
Schedule - shows the schedule view for scheduled refresh, which also can uncover issues with time slots
that are oversubscribed.
You can also export information about a refresh event to a .CSV file, which can provide significant information and
insight into refresh events or errors that can be impacting the performance or completion of scheduled refresh
events.
The following sections look at each of these views in turn.

Refresh history
You can select the Histor y view by clicking on Histor y in the refresh summaries page.

The History provides an overview of the outcomes of recently scheduled refreshes on the capacities for which you
have admin privilege. You can sort the view by any column by clicking the column. You can choose to sort the view
by the column selected by ascending order, descending, or by using text filters.
In history view, the data associated with a given refresh is based on up 60 most recent records for each scheduled
refresh.
You can also export information for any scheduled refresh to a .CSV file, which includes detailed information
including error messages for each refresh event. Exporting to a .CSV file lets you sort the file based on any of the
columns, search for words, sort based on error codes or owners, and so on. The following image shows an example
exported .CSV file.

With the information in the exported file, you can review the capacity, duration, and any error messages recorded
for the instance of refresh.

Refresh schedule
You can select the Schedule view by clicking on Schedule in refresh summaries. The Schedule view displays
scheduling information for the week, broken down into 30-minute time slots.
The Schedule view is very useful in determining whether the refresh events scheduled are properly spaced,
allowing for all refreshes to complete without overlap, or whether you have scheduled refresh events that are
taking too long and creating resource contention. If you find such resource contention, you should adjust your
refresh schedules to avoid the conflicts or overlap, so your scheduled refreshes can complete successfully.
The Refresh time booked (minutes) column is a calculation of the average of up to 60 records for each associated
dataset. The numeric value for each 30-minute time slot is the sum of minutes calculated for all scheduled refreshes
scheduled to start on the time slot and any scheduled refreshes set to start on the previous time slot, but whose
average duration overflows into the time slot that's selected.
The Refresh time available (minutes) column is a calculation of the minutes available for refresh in each time slot,
minus whatever refresh is already scheduled for that timeslot. For example, if your P2 subscription provides 12
concurrently running refreshes, you have 12 30-minute slots, so 12 refreshes x 30 minutes each = 360 minutes
available for refresh in that time slot. If you have one refresh booked in that slot that takes 20 minutes, your Refresh
time available (minutes) in that slot is 340 minutes (360 total minutes available, minus 20 minutes already booked
= 340 minutes still available).
You can select a time slot and then select the associated details button to see which scheduled refresh events
contribute to the refresh time booked, their owners, and how long they take to complete.
Let's look at an example, to see how this works. The following dialog is displayed when we select the 8:30 PM time
slot for Sunday, and click details .
There are three scheduled refresh events occurring in this time slot.
Scheduled refresh #1 and #3 are both scheduled for this 8:30 PM time slot, which we can determine by looking at
the value in the Scheduled time slot column. Their average durations are 4:39 and six seconds (0:06) respectively.
All is good there.
However, scheduled refresh #2 is scheduled for the 8:00 PM time slot, but because it takes an average of over 48
minutes to complete (seen in the Average duration column), that refresh event overflows into the next 30-minute
time slot.
That's not good. The admin in this case should contact the owners of that scheduled refresh instance and suggest
they find a different time slot for that scheduled refresh, or reschedule the other refreshes so there's no overlap, or
find some other solution to prevent such overlap.

Next steps
Data refresh in Power BI
Power BI Gateway - Personal
On-premises data gateway (personal mode)
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Incremental refresh in Power BI
9/9/2020 • 13 minutes to read • Edit Online

Incremental refresh enables very large datasets in Power BI with the following benefits:
Refreshes are faster - Only data that has changed needs to be refreshed. For example, refresh only the last
five days of a ten-year dataset.
Refreshes are more reliable - It's no longer necessary to maintain long-running connections to volatile
source systems.
Resource consumption is reduced - Less data to refresh reduces overall consumption of memory and other
resources.

NOTE
Incremental refresh is now available for Power BI Pro, Premium, and shared subscriptions and datasets.

Configure incremental refresh

Incremental refresh policies are defined in Power BI Desktop and applied when published to the Power BI service.
Filter large datasets in Power BI Desktop
Large datasets with potentially billions of rows may not fit into a Power BI Desktop model because the PBIX file is
limited by the memory resources available on the desktop computer. Such datasets are therefore commonly
filtered upon import. This type of filtering applies whether using incremental refresh or not. For incremental
refresh, you filter by using Power Query date/time parameters.
RangeStart and RangeEnd parameters
For incremental refresh, datasets are filtered by using Power Query date/time parameters with the reserved, case-
sensitive names RangeStar t and RangeEnd . These parameters are used to filter the data imported into Power BI
Desktop, and also to dynamically partition the data into ranges once published to the Power BI service. The
parameter values are substituted by the service to filter for each partition. There's no need to set them in dataset
settings in the service. Once published, the parameter values are overridden automatically by the Power BI service.
To define the parameters with default values, in the Power Query Editor, select Manage Parameters .
With the parameters defined, you can then apply the filter by selecting the Custom Filter menu option for a
column.
Ensure rows are filtered where the column value is after or equal to RangeStar t and before RangeEnd . Other
filter combinations may result in double counting of rows.

IMPORTANT
Verify queries have an equal to (=) on either RangeStar t or RangeEnd , but not both. If the equal to (=) exists on both
parameters, a row could satisfy the conditions for two partitions, which could lead to duplicate data in the model. For
example,
#"Filtered Rows" = Table.SelectRows(dbo_Fact, each [OrderDate] >= RangeStar t and [OrderDate] <= RangeEnd ) could
result in duplicate data.

TIP
While the data type of the parameters must be date/time, it's possible to convert them to match the requirements of the
datasource. For example, the following Power Query function converts a date/time value to resemble an integer surrogate
key of the form yyyymmdd, which is common for data warehouses. The function can be called by the filter step.
(x as datetime) => Date.Year(x)*10000 + Date.Month(x)*100 + Date.Day(x)

Select Close and Apply from the Power Query Editor. You should have a subset of the dataset in Power BI
Desktop.
Filter date column updates
The filter on the date column is used to dynamically partition the data into ranges in the Power BI service.
Incremental refresh isn't designed to support cases where the filtered date column is updated in the source system.
An update is interpreted as an insertion and a deletion, not an actual update. If the deletion occurs in the historical
range and not the incremental range, it won't get picked up. This can cause data refresh failures due to partition-
key conflicts.
Query folding
It's important the partition filters are pushed to the source system when queries are submitted for refresh
operations. To push filtering down means the datasource should support query folding. Most data sources that
support SQL queries support query folding. However, data sources like flat files, blobs, and web feeds typically do
not. In cases where the filter is not supported by the datasource back-end, it cannot be pushed down. In such cases,
the mashup engine compensates and applies the filter locally, which may require retrieving the full dataset from
the data source. This can cause incremental refresh to be very slow, and the process can run out of resources either
in the Power BI service or in the on-premises data gateway if used.
Given the various levels of query folding support for each datasource, it's recommended that verification is
performed to ensure the filter logic is included in the source queries. To make this easier, Power BI Desktop
attempts to perform this verification for you. If unable to verify, a warning is displayed in the incremental refresh
dialog when defining the incremental refresh policy. SQL based data sources such as SQL, Oracle, and Teradata can
rely on this warning. Other data sources may be unable to verify without tracing queries. If Power BI Desktop is
unable to confirm, the following warning is displayed. If you see this warning and want to check that the necessary
query folding is occurring, you can use the Query Diagnostics feature, or trace queries received by the source
database.

Define the refresh policy

Incremental refresh is available on the context menu for tables, except for Live Connection models.
Incremental refresh dialog
The incremental refresh dialog is displayed. Use the toggle to enable the dialog.
 NOTE
If the Power Query expression for the table doesn't refer to the parameters with reserved names, the toggle is disabled.

The header text explains the following:

Refresh policies are defined in Power BI Desktop, and they are applied by refresh operations in the service.
If you're able to download the PBIX file containing an incremental-refresh policy from the Power BI service, it
cannot be opened in Power BI Desktop. While this may be supported in the future, keep in mind these
datasets can grow to be so large that they are impractical to download and open on a typical desktop
computer.
Refresh ranges
The following example defines a refresh policy to store data for five full calendar years plus data for the current
year up to the current date, and incrementally refresh ten full days of data. The first refresh operation loads
historical data. Subsequent refreshes are incremental, and (if scheduled to run daily) perform the following
operations:
Add a new day of data.
Refresh ten full days up to the current date.
Remove calendar years that are older than five years prior to the current date. For example, if the current
 date is January 1 2019, the year 2013 is removed.
The first refresh in the Power BI service may take longer to import all five full calendar years. Subsequent refreshes
may be finished in a fraction of the time.

Current date
The current date is based on the system date at the time of refresh. If scheduled refresh is enabled for the dataset in
the Power BI service, the specified time zone will be taken into account when determining the current date. Both
manually invoked and scheduled refreshes through the Power BI service observe the time zone if available. For
example, a refresh that occurs at 8 PM Pacific Time (US and Canada) with time zone specified will determine the
current date based on Pacific Time, not GMT (which would otherwise be the next day). Refresh operations not
invoked through the Power BI service, such as the TMSL refresh command, will not consider the scheduled refresh
time zone
 NOTE
Definition of these ranges might be all you need, in which case you can go straight to the publishing step below. The
additional dropdowns are for advanced features.

Advanced policy options

Detect data changes
Incremental refresh of ten days is more efficient than full refresh of five years. However, it's possible to do even
better. If you select the Detect data changes checkbox, you can select a date/time column used to identify and
refresh only the days where the data has changed. This assumes such a column exists in the source system, which
is typically for auditing purposes. This should not be the same column used to par tition the data with the
RangeStar t/RangeEnd parameters. The maximum value of this column is evaluated for each of the periods in
the incremental range. If it has not changed since the last refresh, there is no need to refresh the period. In the
example, this could further reduce the days incrementally refreshed from ten to around two.
 TIP
The current design requires that the column to detect data changes is persisted and cached into memory. You may want to
consider one of the following techniques to reduce cardinality and memory consumption.
Persist only the maximum value of this column at time of refresh, perhaps using a Power Query function.
Reduce the precision to a level that is acceptable given your refresh-frequency requirements.
Define a custom query for detecting data changes using the XMLA endpoint and avoid persisting the column value
altogether. See custom queries for detect data changes below for more information.

Only refresh complete periods

Let's say your refresh is scheduled to run at 4:00 AM every morning. If data appears in the source system during
those 4 hours, you may not want to account for it. Some business metrics such as barrels per day in the oil and gas
industry make no sense with partial days.
Another example is refreshing data from a financial system where data for the previous month is approved on the
12th calendar day of the month. You could set the incremental range to 1 month and schedule the refresh to run on
the 12th day of the month. With this option checked, it would for example refresh January data on February 12th.
 NOTE
Refresh operations in the service run under UTC time. This can determine the effective date and affect complete periods. We
plan to add the ability to override the effective date for a refresh operation.

Publish to the service

You can now refresh the model. The first refresh may take longer to import the historical data. Subsequent
refreshes can be much quicker because they use incremental refresh.

Query timeouts
The troubleshooting refresh article explains that refresh operations in the Power BI service are subject to timeouts.
Queries can also be limited by the default timeout for the data source. Most relational sources allow overriding
timeouts in the M expression. For example, the expression below uses the SQL Server data-access function to set it
to 2 hours. Each period defined by the policy ranges submits a query observing the command timeout setting.
 let
Source = Sql.Database("myserver.database.windows.net", "AdventureWorks", [CommandTimeout=#duration(0, 2,
0, 0)]),
dbo_Fact = Source{[Schema="dbo",Item="FactInternetSales"]}[Data],
#"Filtered Rows" = Table.SelectRows(dbo_Fact, each [OrderDate] >= RangeStart and [OrderDate] < RangeEnd)
in
#"Filtered Rows"

XMLA endpoint benefits for incremental refresh

The XMLA endpoint for datasets in a Premium capacity can be enabled for read-write operations, which can
provide considerable benefits for incremental refresh. Refresh operations through the XMLA endpoint are not
limited to 48 refreshes per day, and the scheduled refresh timeout is not imposed, which can be useful in
incremental refresh scenarios.
Refresh management with SQL Server Management Studio (SSMS )
With XMLA endpoint read-write enabled, SSMS can be used to view and manage partitions generated by the
application of incremental refresh policies. This allows, for example, to refresh a specific historical partition not in
the incremental range to perform a back-dated update without having to refresh all historical data. You can also use
SSMS to load historical data for very large datasets by incrementally adding/refreshing historical partitions in
batches.

Override incremental refresh behavior

With SSMS, you also have more control over how to invoke incremental refreshes from using the Tabular Model
Scripting Language (TMSL) and the Tabular Object Model (TOM). For example, in SSMS, in Object Explorer, right-
click a table and then select the Process Table menu option. Then click the Script button to generate a TMSL
refresh command.
The following parameters can be inserted into the TMSL refresh command to override the default incremental
refresh behavior.
applyRefreshPolicy – If a table has an incremental refresh policy defined, applyRefreshPolicy will
determine if the policy is applied or not. If the policy is not applied, a process full operation will leave
partition definitions unchanged and all partitions in the table will be fully refreshed. Default value is true.
effectiveDate – If an incremental refresh policy is being applied, it needs to know the current date to
determine rolling window ranges for the historical range and the incremental range. The effectiveDate
parameter allows you to override the current date. This is useful for testing, demos, and business scenarios
where data is incrementally refreshed up to a date in the past or the future (for example, budgets in the
future). The default value is the current date.

{
"refresh": {
"type": "full",

"applyRefreshPolicy": true,
"effectiveDate": "12/31/2013",

"objects": [
{
"database": "IR_AdventureWorks",
"table": "FactInternetSales"
}
]
}
}

To learn more about overriding default incremental refresh behavior with TMSL, see Refresh command.
Custom queries for detect data changes
You can use TMSL and/or TOM to override the detected data changes behavior. Not only can this be used to avoid
persisting the last-update column in the in-memory cache, it can enable scenarios where a
configuration/instruction table is prepared by ETL processes for the purpose of flagging only the partitions that
need to be refreshed. This can create a more efficient incremental refresh process where only the required periods
are refreshed, no matter how long ago data updates took place.
The pollingExpression is intended to be a lightweight M expression or name of another M query. It must return a
scalar value and will be executed for each partition. If the value returned is different to what it was the last time an
incremental refresh occurred, the partition is flagged for full processing.
The following example covers all 120 months in the historical range for backdated changes. Specifying 120 months
instead of 10 years means data compression may not be quite as efficient, but avoids having to refresh a whole
historical year, which would be more expensive when a month would suffice for a backdated change.

"refreshPolicy": {
"policyType": "basic",
"rollingWindowGranularity": "month",
"rollingWindowPeriods": 120,
"incrementalGranularity": "month",
"incrementalPeriods": 120,
"pollingExpression": "<M expression or name of custom polling query>",
"sourceExpression": [
"let ..."
]
}

Metadata-only deployment
When publishing a new version of a PBIX file from Power BI Desktop to a workspace in Power BI Premium, if a
dataset with the same name already exists, you are prompted to replace the existing dataset.

In some cases you may not want to replace the dataset, especially with incremental refresh. The dataset in Power BI
Desktop could be much smaller than the one in the service. If the dataset in the service has an incremental refresh
policy applied, it may have several years of historical data that will be lost if the dataset is replaced. Refreshing all
the historical data could take hours and result in system downtime for users.
Instead, it's better to perform a metadata-only deployment. This allows deployment of new objects without losing
the historical data. For example, if you have added a few measures, you can deploy only the new measures without
needing to refresh the data, saving a lot of time.
When configured for read-write, the XMLA endpoint provides compatibility with tools that make this happen. For
example, the ALM Toolkit is a schema diff tool for Power BI datasets and can be used to perform deployment of
metadata only.
Download and install the latest version of the ALM Toolkit from the Analysis Services Git repo. Documentation links
and information on supportability are available via the Help ribbon. To perform a metadata only deployment,
perform a comparison and select the running Power BI Desktop instance as the source, and the existing dataset in
the service as the target. Consider the differences displayed and skip the update of the table with incremental
refresh partitions, or use the Options dialog to retain partitions for table updates. Validate the selection to ensure
the integrity of the target model and then update.
See also
Dataset connectivity with the XMLA endpoint
Troubleshooting refresh scenarios
 Refresh a dataset created from a Power BI Desktop
file on a local drive
9/9/2020 • 2 minutes to read • Edit Online

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Power BI Desktop files
imported from a local drive where Get Data/Query Editor is used to connect to and load data from any of the
following data sources:
Power BI Gateway - Personal
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS) and Microsoft Exchange.
On-premises data gateway
Data source
Analysis Services Tabular
Analysis Services Multidimensional
SQL Server
SAP HANA
Oracle
Teradata
File
Folder
SharePoint list (on-premises)
Web
OData
IBM DB2
MySQL
Sybase
SAP BW
IBM Informix Database
ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

You can perform a one-time, manual refresh in Power BI Desktop by selecting Refresh on the Home ribbon. When
you select Refresh here, the data in the file’s model is refreshed with updated data from the original data source.
This kind of refresh, entirely from within the Power BI Desktop application itself, is different from manual or
scheduled refresh in Power BI, and it’s important to understand the distinction.
When you import your Power BI Desktop file from a local drive, data, along with other information about the
model, is loaded into a dataset in the Power BI service. In the Power BI service, not Power BI Desktop, you want to
refresh data in the dataset because that is what your reports, in the Power BI service, are based on. Because the data
sources are external, you can manually refresh the dataset by using Refresh now or you can set up a refresh
schedule by using Schedule Refresh .
When you refresh the dataset, Power BI does not connect to the file on the local drive to query for updated data. It
uses information in the dataset to connect directly to the data sources to query for updated data it then loads into
the dataset.

NOTE
Refreshed data in the dataset is not synchronized back to the file on the local drive.

How do I schedule refresh?

When you set up a refresh schedule, Power BI connects directly to the data sources using connection information
and credentials in the dataset to query for updated data, then loads the updated data into the dataset. Any
visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to set up scheduled refresh, see Configure scheduled refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this is an issue connected with a gateway. Take a look
at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Refresh a dataset stored on OneDrive or SharePoint
Online
9/9/2020 • 4 minutes to read • Edit Online

Importing files from OneDrive or SharePoint Online into the Power BI service is a great way to make sure your
work in Power BI Desktop stays in sync with the Power BI service.

Advantages of storing a Power BI Desktop file on OneDrive or

SharePoint Online
When you store a Power BI Desktop file on OneDrive or SharePoint Online, any data you’ve loaded into your file’s
model is imported into the dataset. Any reports you’ve created in the file are loaded into Repor ts in the Power BI
service. Let's say you make changes to your file on OneDrive or SharePoint Online. These changes can include
adding new measures, changing column names, or editing visualizations. Once you save the file, Power BI service
syncs with those changes too, usually within about an hour.
You can do a one-time, manual refresh right in Power BI Desktop by selecting Refresh on the Home ribbon. When
you select Refresh , you refresh the file’s model with updated data from the original data source. This kind of
refresh happens entirely from within the Power BI Desktop application itself. It's different from a manual or
scheduled refresh in Power BI, and it’s important to understand the distinction.

When you import your Power BI Desktop file from OneDrive or SharePoint Online, you load data and model
information into a dataset in Power BI. You'll want to refresh the dataset in the Power BI service because that's what
your reports are based on. Because the data sources are external, you can manually refresh the dataset by using
Refresh now or you can set up a refresh schedule by using Schedule Refresh .
When you refresh the dataset, Power BI doesn't connect to the file on OneDrive or SharePoint Online to query for
updated data. It uses information in the dataset to connect directly to the data sources and query for updated data.
Then, it loads that data into the dataset. This refreshed data in the dataset isn't synchronized back to the file on
OneDrive or SharePoint Online.

What’s supported?
Power BI supports Refresh and Schedule Refresh for datasets created from Power PI Desktop files imported
from a local drive where you use Get Data or Quer y Editor to connect to and load data from the following data
sources.

NOTE
Onedrive refresh for live connection datasets is supported. However, changing the live connection dataset, from one dataset
to another in an already published report, is not supported in the OneDrive refresh scenario.

Power BI Gateway - Personal

All online data sources shown in Power BI Desktop’s Get Data and Quer y Editor .
All on-premises data sources shown in Power BI Desktop’s Get Data and Quer y Editor except for Hadoop File
(HDFS) and Microsoft Exchange.
On-premises data gateway
Data source
Analysis Services Tabular
Analysis Services Multidimensional
SQL Server
 SAP HANA
Oracle
Teradata
File
Folder
SharePoint list (on-premises)
Web
OData
IBM DB2
MySQL
Sybase
SAP BW
IBM Informix Database
ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, you should keep any files you want to import into
Power BI in OneDrive for Business. Here’s why: You likely use two different accounts to sign into them.
When you connect to OneDrive for Business in Power BI, connection is easy because your Power BI account is often
the same account as your OneDrive for Business account. With personal OneDrive, you usually sign in with a
different Microsoft account.
When you sign in with your Microsoft account, be sure to select Keep me signed in . Power BI can then
synchronize any updates you make in the file in Power BI Desktop with datasets in Power BI.

If you've changed your Microsoft credentials, you can't synchronize changes between your file on OneDrive and the
dataset in Power BI. You need to connect to and import your file again from OneDrive.

How do I schedule refresh?

When you set up a refresh schedule, Power BI connects directly to the data sources. Power BI uses connection
information and credentials in the dataset to query for updated data. Then Power BI loads the updated data into the
dataset. It then updates any report visualizations and dashboards based on that dataset in the Power BI service.
For details on how to set up schedule refresh, see Configure scheduled refresh.
When things go wrong
When things go wrong, it’s usually because Power BI can’t sign into data sources. Things may also go wrong if the
dataset tries to connect to an on-premises data source but the gateway is offline. To avoid these issues, make sure
Power BI can sign into data sources. Try signing into your data sources in Data Source Credentials . Sometimes
the password you use to sign into a data source changes or Power BI gets signed out from a data source.
When you save your changes to the Power BI Desktop file on OneDrive and you don't see those changes in Power
BI within an hour or so, it could be because Power BI can't connect to your OneDrive. Try connecting to the file on
OneDrive again. If you’re prompted to sign in, make sure you select Keep me signed in. Because Power BI wasn't
able to connect to your OneDrive to synchronize with the file, you’ll need to import your file again.
Be sure to leave the Send refresh failure notification email to me checked. You’ll want to know right away if a
scheduled refresh fails.

Troubleshooting
Sometimes refreshing data may not go as expected. You'll typically run into data refresh issues when you're
connected with a gateway. Take a look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community.
 Refresh a dataset created from an Excel workbook on
a local drive
9/9/2020 • 3 minutes to read • Edit Online

What’s supported?
In Power BI, Refresh Now and Schedule Refresh is supported for datasets created from Excel workbooks imported
from a local drive where Power Query (Get & Transform data in Excel 2016) or Power Pivot is used to connect to
any of the following data sources and load data into the Excel data model:
Power BI Gateway - Personal
All online data sources shown in Power Query.
All on-premises data sources shown in Power Query except for Hadoop file (HDFS) and Microsoft Exchange.
All online data sources shown in Power Pivot.*
All on-premises data sources shown in Power Pivot except for Hadoop file (HDFS) and Microsoft Exchange.
On-premises data gateway
Data source
Analysis Services Tabular
Analysis Services Multidimensional
SQL Server
SAP HANA
Oracle
Teradata
File
Folder
SharePoint list (on-premises)
Web
OData
IBM DB2
MySQL
Sybase
SAP BW
IBM Informix Database
ODBC

Notes:
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and
refresh the dataset.
When using Excel 2013, make sure you’ve updated Power Query to the latest version.
Refresh is not supported for Excel workbooks imported from a local drive where data exists only in
worksheets or linked tables. Refresh is supported for worksheet data if it is stored and imported from
OneDrive. To learn more, see Refresh a dataset created from an Excel workbook on OneDrive, or SharePoint
Online.
When you refresh a dataset created from an Excel workbook imported from a local drive, only the data
 queried from data sources is refreshed. If you change the structure of the data model in Excel or Power Pivot;
for example, create a new measure or change the name of a column, those changes will not be copied to the
dataset. If you make such changes, you’ll need to re-upload or re-publish the workbook. If you expect to
make regular changes to the structure of your workbook and you want those to be reflected in the dataset in
Power BI without having to re-upload, consider putting your workbook on OneDrive. Power BI automatically
refreshes both the structure and worksheet data from workbooks stored and imported from OneDrive.

How do I make sure data is loaded to the Excel data model?

When you use Power Query (Get & Transform data in Excel 2016) to connect to a data source, you have several
options where to load the data. To make sure you load data into the data model, you must select the Add this data
to the Data Model option in the Load To dialog box.

NOTE
The images here show Excel 2016.

In Navigator , click Load To…

Or, If you click Edit in Navigator, you’ll open the Query Editor. There you can click Close & Load To….

Then in Load To , make sure you select Add this data to the Data Model .

What if I use Get External Data in Power Pivot?

No problem. Whenever you use Power Pivot to connect to and query data from an on-premises or online data
source, the data is automatically loaded to the data model.
How do I schedule refresh?
When you setup a refresh schedule, Power BI will connect directly to the data sources using connection information
and credentials in the dataset to query for updated data, then load the updated data into the dataset. Any
visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to setup schedule refresh, see Configure Schedule Refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked . You’ll want to know right away if
a scheduled refresh fails.

IMPORTANT
Refresh is not supported for OData feeds connected to and queried from Power Pivot. When using an OData feed as a data
source, use Power Query.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this will be an issue connected with a gateway. Take a
look at the gateway troubleshooting articles for tools and known issues.
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal

Next steps
More questions? Try the Power BI Community
 Refresh a dataset created from an Excel workbook on
OneDrive, or SharePoint Online
9/9/2020 • 6 minutes to read • Edit Online

You can import Excel workbooks that are stored on your local machine, or in cloud storage such as OneDrive for
Business or SharePoint Online. We will look at the advantages of using cloud storage for your Excel files. For more
information on how to import Excel files into Power BI, see Get data from Excel workbook files.

What are the advantages?

Importing files from OneDrive, or SharePoint Online, is a great way to make sure the work you’re doing in Excel
stays in-sync with the Power BI service. Any data you’ve loaded into your file’s model is imported into the dataset,
and any reports you’ve created in the file are loaded into Reports in Power BI. If you make changes to your file on
OneDrive, or SharePoint Online, like add new measures, change column names, or edit visualizations, once you
save, those changes are updated in Power BI too, usually within about an hour.
When you import an Excel workbook from your personal OneDrive, any data in the workbook, like tables in
worksheets and/or data that are loaded into the Excel data model and the structure of the data model, are imported
into a new dataset in Power BI. Any Power View visualizations are re-created in Reports. Power BI automatically
connects to the workbook on OneDrive, or SharePoint Online, about every hour to check for updates. If the
workbook has changed, Power BI will refresh the dataset and reports in the Power BI service.
You can refresh the dataset in the Power BI service. When you manually refresh, or schedule refresh, on the dataset,
Power BI connects directly to the external data sources to query for updated data it then loads into the dataset.
Refreshing a dataset from within Power BI does not refresh the data in the workbook on OneDrive, or SharePoint
Online.

What’s supported?
In Power BI, Refresh Now and Schedule Refresh are supported for datasets created from Power BI Desktop files
imported from a local drive where Get Data/Query Editor is used to connect to and load data from any of the
following data sources:
Power BI Gateway - Personal
All online data sources shown in Power BI Desktop’s Get Data and Query Editor.
All on-premises data sources shown in Power BI Desktop’s Get Data and Query Editor except for Hadoop file
(HDFS) and Microsoft Exchange.
On-premises data gateway
Data source
Analysis Services Tabular
Analysis Services Multidimensional
SQL Server
SAP HANA
Oracle
Teradata
File
Folder
 SharePoint list (on-premises)
Web
OData
IBM DB2
MySQL
Sybase
SAP BW
IBM Informix Database
ODBC

NOTE
A gateway must be installed and running in order for Power BI to connect to on-premises data sources and refresh the
dataset.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, it’s recommended you keep any files you want to
import into Power BI in OneDrive for Business. Here’s why: You likely use two different accounts to sign into them.
Connecting to OneDrive for Business in Power BI is typically seamless because the same account you use to sign
into Power BI is often the same account used to sign into OneDrive for Business. But, with personal OneDrive, you
likely sign in with a different Microsoft account.
When you sign in with your Microsoft account, be sure to select Keep me signed in . Power BI can then
synchronize any updates you make in the file in Power BI Desktop with datasets in Power BI.

If you make changes to your file on OneDrive that cannot be synchronized with the dataset or reports in Power BI,
because your Microsoft account credentials might have changed, you’ll need to connect to and import your file
again from your personal OneDrive.

Options for connecting to Excel file

When you connect to an Excel workbook in OneDrive for Business, or SharePoint Online, you’ll have two options
on how to get what’s in your workbook into Power BI.
Impor t Excel data into Power BI – When you import an Excel workbook from your OneDrive for Business, or
SharePoint Online, it works as described above.
Connect, Manage, and View Excel in Power BI – When using this option, you create a connection from Power
BI right to your workbook on OneDrive for Business, or SharePoint Online.
When you connect to an Excel workbook this way, a dataset is not created in Power BI. However, the workbook will
appear in the Power BI service under Reports with an Excel icon next to the name. Unlike with Excel Online, when
you connect to your workbook from Power BI, if your workbook has connections to external data sources that load
data into the Excel data model, you can set up a refresh schedule.
When you set up a refresh schedule this way, the only difference is refreshed data goes into the workbook’s data
model on OneDrive, or SharePoint Online, rather than a dataset in Power BI.

How do I make sure data is loaded to the Excel data model?

When you use Power Query (Get & Transform in Excel 2016) to connect to a data source, you have several
options where to load the data. To make sure you load data into the data model, you must select the Add this data
to the Data Model option in the Load To dialog box.

NOTE
The images here show Excel 2016.

In Navigator , click Load To…

Or, If you click Edit in Navigator , you’ll open the Query Editor. There you can click Close & Load To….

Then in Load To , make sure you select Add this data to the Data Model .

What if I use Get External Data in Power Pivot?

No problem. Whenever you use Power Pivot to connect to and query data from an on-premises or online data
source, the data is automatically loaded to the data model.
How do I schedule refresh?
When you set up a refresh schedule, Power BI connects directly to the data sources using connection information
and credentials in the dataset to query for updated data, then loads the updated data into the dataset. Any
visualizations in reports and dashboards based on that dataset in the Power BI service are also updated.
For details on how to set up scheduled refresh, see Configure scheduled refresh.

When things go wrong

When things go wrong, it’s usually because Power BI can’t sign into data sources, or if the dataset connects to an
on-premises data source, the gateway is offline. Make sure Power BI can sign into data sources. If a password you
use to sign into a data source changes, or Power BI gets signed out from a data source, be sure to try signing into
your data sources again in Data Source Credentials.
Be sure to leave the Send refresh failure notification email to me checked . You’ll want to know right away if
a scheduled refresh fails.

Important notes
Refresh is not supported for OData feeds connected to and queried from Power Pivot. When using an OData feed
as a data source, use Power Query.

Troubleshooting
Sometimes refreshing data may not go as expected. Typically this is an issue connected with a gateway. Take a look
at the gateway troubleshooting articles for tools and known issues:
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try the Power BI Community
 Refresh a dataset created from a .CSV file on
OneDrive or SharePoint Online
9/9/2020 • 2 minutes to read • Edit Online

What are the advantages?

When you connect to a .csv file on OneDrive or SharePoint Online, a dataset is created in Power BI. Data from the
.csv file is then imported into the dataset in Power BI. Power BI then automatically connects to the file and refreshes
any changes with the dataset in Power BI. If you edit the .csv file in OneDrive, or SharePoint Online, once you save,
those changes will appear in Power BI, usually within about an hour. Any visualizations in Power BI based on the
dataset are automatically updated too.
If your files are in a shared folder on OneDrive for Business, or SharePoint Online, other users can work on the
same file. Once saved, any changes made are automatically updated in Power BI, usually within an hour.
Many organizations run processes that automatically query databases for data that is then saved to a .csv file each
day. If the file is stored on OneDrive, or SharePoint Online, and the same file is overwritten each day, as opposed to
a new file with a different name being created each day, you can connect to that file in Power BI. Your dataset that
connects to the file will be synchronized soon after the file on OneDrive, or SharePoint Online, is updated. Any
visualizations based on the dataset are automatically updated too.

What’s supported?
Comma separated value files are simple text files, so connections to external data sources and reports are not
supported. You cannot schedule refresh on a dataset created from a comma delimited file. However, when the file is
on OneDrive, or SharePoint Online, Power BI will synchronize any changes to the file with the dataset automatically
about every hour.

OneDrive or OneDrive for Business. What’s the difference?

If you have both a personal OneDrive and OneDrive for Business, it’s recommended you keep any files you want to
connect to in Power BI on OneDrive for Business. Here’s why: You likely use two different accounts to sign into
them.
Connecting to OneDrive for Business in Power BI is typically seamless because the same account you use to sign
into Power BI with is often the same account used to sign into OneDrive for Business. But, with personal OneDrive,
you likely sign in with a different Microsoft account.
When you sign into your Microsoft account, be sure to select Keep me signed in. Power BI can then synchronize any
updates with datasets in Power BI
If you make changes to your .csv file on OneDrive that cannot be synchronized with the dataset in Power BI because
your Microsoft account credentials might have changed, you’ll need to connect to the file and import it again from
your personal OneDrive.

When things go wrong

If data in the .csv file on OneDrive is changing and those changes aren’t being reflected in Power BI, it’s most likely
because Power BI cannot connect to your OneDrive. Try connecting to the file and importing it again. If you’re
prompted to sign in, make sure you select Keep me signed in .

Next steps
Tools for troubleshooting refresh issues Troubleshooting refresh scenarios
More questions? Try asking the Power BI Community
 Query caching in Power BI Premium/Embedded
9/9/2020 • 2 minutes to read • Edit Online

Organizations with Power BI Premium or Power BI Embedded can take advantage of query caching to speed up
reports associated with a dataset. Query caching instructs the Premium/Embedded capacity to use its local caching
service to maintain query results, avoiding having the underlying data source compute those results.

IMPORTANT
Query caching is only available on Power BI Premium or Power BI Embedded. It is not applicable to LiveConnect datasets
leveraging Azure Analysis Services or SQL Server Analysis Services.

Cached query results are specific to user and dataset context and always respect security rules. At present the
service only does query caching for the initial page that you land on. In other words, queries aren't cached when
you interact with the report. The query cache respects personal bookmarks and persistent filters, so queries
generated by a personalized report will be cached. Dashboard tiles that are powered by the same queries also
benefit once the query is cached. Performance especially benefits when a dataset is accessed frequently and doesn't
need to be refreshed often. Query caching can also reduce load on your Premium/Embedded capacity by reducing
the overall number of queries.
You control query caching behavior on the Settings page for the dataset in the Power BI service. It has three
possible settings:
Capacity default : Query caching Off
Off : Don't use query caching for this dataset.
On : Use query caching for this dataset.

Considerations and limitations

When you change caching settings from On to Off , all previously saved query results for the dataset are
removed from the capacity cache. You can turn off caching either explicitly or by reverting to capacity default
setting that an administrator has set to Off . Turning it off can introduce a small delay the next time any report
runs queries against this dataset. The delay is caused by those report queries running on demand and not
leveraging saved results. Also, the required dataset may need to be loaded into memory before it can service
queries.
When the query cache is refreshed, Power BI must run queries against the underlying data models to get the
latest results. If a large number of datasets have query caching enabled and the Premium/Embedded capacity is
under heavy load, some performance degradation may occur during cache refresh. Degradation results from
the increased volume of queries being executed.
Next steps
What is Power BI Premium?
What is Power BI Embedded in Azure?
 What are Power BI template apps?
9/9/2020 • 4 minutes to read • Edit Online

The new Power BI template apps enable Power BI partners to build Power BI apps with little or no coding, and
deploy them to any Power BI customer. This article is an overview of the Power BI template app program.
As a Power BI partner, you create a set of out-of-the-box content for your customers and publish it yourself.
You build template apps that allow your customers to connect and instantiate within their own accounts. As
domain experts, they can unlock the data in a way that's easy for their business users to consume.
You submit a template apps to the Partner center. The apps then become publicly available in the Power BI Apps
marketplace and on Microsoft AppSource. Here's a high-level look at the public template app creation experience.

Power BI Apps marketplace

Power BI Template Apps allow Power BI Pro or Power BI Premium users to gain immediate insights through
prepackaged dashboards and reports that can be connected to live data sources. Many Power BI Apps are already
available in the Power BI Apps marketplace.

Process
The general process to develop and submit a template app involves several stages. Some stages can include more
than one activity at the same time.

P O W ER B I P O W ER B I PA RT N ER
STA GE DESK TO P SERVIC E C EN T ER

One Build a data Create a Register as a

model and workspace. partner
report in a .pbix Import .pbix file.
file Create a
complementary
dashboard

Two Create a test

package and run
internal
validation

Three Promote the test With your

package to preproduction
preproduction for package, create a
validation outside Power BI
your Power BI template app
tenant, and offer and start
submit it to the validation
AppSource process

Four Promote the Go live

preproduction
package to
production

Before you begin

To create the template app, you need permissions to create one. See the Power BI admin portal, Template app
settings for details.
To publish a template app to the Power BI service and AppSource, you must meet the requirements for becoming
a Partner Center publisher.

High-level steps
Here are the high-level steps.
1. Review the requirements to make sure you meet them.
2. Build a report in Power BI Desktop. Use parameters so you can save it as a file other people can use.
3. Create a workspace for your template app in your tenant on the Power BI service (app.powerbi.com).
4. Import your .pbix file and add content such as a dashboard to your app.
5. Create a test package to test the template app yourself within your organization.
6. Promote the test app to pre-production to submit the app for validation in AppSource, and to test outside
your own tenant.
7. Submitthe content to Partner center for publishing.
8. Make your offer go 'Live' in AppSource, and move your app to production in Power BI.
9. Now you can start developing the next version in the same workspace, in preproduction.

Requirements
To create the template app, you need permissions to create one. See the Power BI admin portal, Template app
settings for details.
To publish a template app to the Power BI service and AppSource, you must meet the requirements for becoming
a Partner Center publisher.

NOTE
Template apps submissions are managed in Partner Center. Use the same Microsoft Developer Center registration account
to sign in. You should have only one Microsoft account for your AppSource offerings. Accounts shouldn't be specific to
individual services or offers.

Tips
Make sure your app includes sample data to get everyone started in a click.
Carefully examine your application by installing it in your tenant and in a secondary tenant. Make sure
customers only see what you want them to see.
Use AppSource as your online store to host your application. This way everyone using Power BI can find your
app.
Consider offering more than one template app for separate unique scenarios.
Enable data customization; for example, support custom connection and parameters configuration by the
installer.
See Tips for authoring template apps in Power BI for more suggestions.

Known limitations
F EAT URE K N O W N L IM ITAT IO N

Contents: Datasets Exactly one dataset should be present. Only datasets built in
Power BI Desktop (.pbix files) are allowed.
Not supported: Datasets from other template apps, cross-
workspace datasets, paginated reports (.rdl files), Excel
workbooks

Contents: Dashboards Real-time tiles aren't allowed (in other words, no support for
push or streaming datasets)

Contents: Dataflows Not supported: Dataflows

Contents from files Only PBIX files are allowed.

Not supported: .rdl files (paginated reports), Excel workbooks
 F EAT URE K N O W N L IM ITAT IO N

Data sources Data sources supported for cloud Scheduled Data refresh are
allowed.
Not supported:
DirectQuery
Live connections (no Azure AS)
On-premises data sources (personal and enterprise
gateways aren't supported)
Real time (no support for push dataset)
Composite models

Dataset: cross-workspace No cross-workspace datasets are allowed

Query parameters Not supported: Parameters of type "Any" or "Binary" type

block refresh operation for dataset

Power BI visuals Only publicly available Power BI visuals are supported.

Organizational Power BI visuals not supported

Sovereign clouds Template apps are not available in sovereign clouds

Support
For support during development, use https://powerbi.microsoft.com/support. We actively monitor and manage
this site. Customer incidents quickly find their way to the appropriate team.

Next steps
Create a template app
 Create a template app in Power BI
9/9/2020 • 6 minutes to read • Edit Online

The new Power BI template apps enable Power BI partners to build Power BI apps with little or no coding, and
deploy them to any Power BI customer. This article contains step-by-step instructions to create a Power BI template
app.
If you can create Power BI reports and dashboards, you can become a template app builder and builds and
packages analytical content into an app. You may deploy your app to other Power BI tenants through any available
platform, such as AppSource, or by using it in your own web service. As a builder you have the possibility to create
a protected analytics package for distribution.
Power BI tenant admins govern and control who in their organization can create template apps, and who can
install them. Those users who are authorized can install your template app, then modify it and distribute it to the
Power BI consumers in their organization.

Prerequisites
Here are the requirements for building a template app:
A Power BI pro license
An installation of Power BI Desktop (optional)
Familiarity with the basic concepts of Power BI
Permissions to share a template app publicly (for more information, see Power BI admin portal, Template app
settings

Create the template workspace

To create a template app you can distribute to other Power BI tenants, you need to create it in one of the new
workspaces.
1. In the Power BI service, select Workspaces > Create workspace .

2. In Create a workspace , select Upgrade to new .

3. Enter a name, description (optional), and logo image (optional) for your workspace.
4. Expand the Advanced section and select Develop a template app .
5. Select Save .

NOTE
You need permissions from your Power BI admin to promote template apps.

Create the content in your template app

As with a regular Power BI workspace, your next step is to create the contents in the workspace.
Create your Power BI content in your workspace.
If you're using parameters in Power Query, make sure they have well-defined type (for example, Text). The types
Any and Binary aren't supported.
Tips for authoring template apps in Power BI has suggestions to consider when creating reports and dashboards
for your template app.

Create the test template app

Now that you have content in your workspace, you're ready to package it in a template app. The first step is to
create a test template app, accessible only from within your organization on your tenant.
1. In the template workspace, select Create app .
Here, you fill in additional building options for your template app, in five categories:
Branding

App name
Description
Support site (link is presented under app info after redistributing template app as org app)
App logo (45K file size limit, 1:1 aspect ratio, .png .jpg .jpeg formats)
App theme color
Navigation
Activate the New navigation builder where you can define the nav pane of the app (See Design the
navigation experience in this article for details).
App landing page: If you decide to opt out of the navigation builder, you have the option to select the app
landing page. Define a report or dashboard to be the landing page of your app. Use a landing page that
gives the right impression.
Control
Set limits and restrictions that your application users will have with the content of your application. You can
use this control to protect intellectual property in your app.

NOTE
Exporting to .pbix format is always blocked for users installing the app.
 Parameters
Use this category to manage parameter behavior when connecting to data sources. Learn more about
creating query parameters.

Value : default parameter value.

Required : use this to require the installer to input a user-specific parameter.
Lock : Locking prevents the installer from updating a parameter.
Access In the test phase, decide which others in your organization can install and test your app. Don't
worry, you can always come back and change these settings later. The setting doesn't affect access of the
distributed Template app.
2. Select Create app .
You see a message that the test app is ready, with a link to copy and share with your app testers.

You've also done the first step of the release management process, which follows.

Manage the template app release

Before you release this template app publicly, you want to make sure it's ready to go. Power BI has created the
release management pane, where you can follow and inspect the full app release path. You can also trigger the
transition from stage to stage. The common stages are:
 Generate test app: for testing only in your organization.
Promote the test package to pre-production stage: test outside of your organization.
Promote pre-production package to Production: production version.
Delete any package or start over from previous stage.
The URL doesn't change as you move between release stages. Promotion doesn't affect the URL itself.
Let's go through the stages:
1. In the template workspace, select Release Management .

2. Select Create app .

If you created the test app in Create the test template app above, the yellow dot next to Testing is
already filled and you don't need to select Create app here. If you do select it, you go back into the
template app creation process.
3. Select Get link .
4. To test the app installation experience, copy the link in the notification window and paste it in a new browser
window.
From here, you're following the same procedure your customers will follow. See Install and distribute
template apps in your organization for their version.
5. In the dialog box, select Install .
When installation succeeds, you see a notification that the new app is ready.
6. Select Go to app .
7. In Get star ted with your new app , you see your app as your customers will see it.
 8. Select Explore App to verify the test app with the sample data.
9. To make any changes, go back to the app in the original workspace. Update the test app until you're
satisfied.
10. When you're ready to promote your app to pre-production for further testing outside your tenant, go back
to the Release Management pane and select Promote app .

NOTE
When the app is promoted it becomes publicly available outside your organization.

If you don't see that option, contact your Power BI admin to grant you permissions for template app
development in the admin portal.
11. Select Promote to confirm your choice.
12. Copy this new URL to share outside your tenant for testing. This link is also the one you submit to begin the
process of distributing your app on AppSource by creating a new Partner center offer. Submit only pre-
production links to the Partner center. Only after the app is approved and you get notification that it is
published in AppSource, then you can promote this package to production in Power BI.
13. When your app is ready for production or sharing via AppSource, go back to the Release Management
pane and select Promote app next to Pre-production .
14. Select Promote to confirm your choice.
Now your app is in production, and ready for distribution.
To make your app widely available to thousands of Power BI users in the world, we encourage you to submit it to
AppSource. See the Power BI Application offer for details.

Next steps
See how your customers interact with your template app in Install, customize, and distribute template apps in your
organization.
See the Power BI Application offer for details on distributing your app.
 Tips for authoring template apps in Power BI
9/9/2020 • 6 minutes to read • Edit Online

When you're authoring your template app in Power BI, part of it is the logistics of creating the workspace, testing it,
and production. But the other important part is obviously authoring the report and the dashboard. We can break
down the authoring process into four main components. Working on these components helps you create the best
possible template app:
With queries , you connect and transform the data, and define parameters.
In the data model , you create relationships, measures, and Q&A improvements.
Repor t pages include visuals and filters to provide insights into your data.
Dashboards and tiles offer an overview of the insights included.
Sample data makes your app discoverable immediately after installation.
You may be familiar with each piece as existing Power BI features. When building a template app, there are
additional things to consider for each piece. See each section below for more details.

Queries
For template apps, queries developed in Power BI Desktop are used to connect to your data source and import
data. These queries are required to return a consistent schema and are supported for Scheduled Data refresh
(DirectQuery isn't supported).
Connect to your API
To get started, you need to connect to your API from Power BI Desktop to start building your queries.
You can use the Data Connectors that are available in Power BI Desktop to connect to your API. You can use the
Web Data Connector (Get Data -> Web) to connect to your Rest API or the OData connector (Get Data -> OData
feed) to connect to your OData feed.

NOTE
Currently template apps do not support custom connectors, it is recommended to explore using Odatafeed Auth 2.0 as a
mitigation for some of the connection use-cases or to submit your connector for certification. For details on how to develop
a connector and certify it check the Data Connectors documentation.

Consider the source

The queries define the data that's included in the data model. Depending on the size of your system, these queries
should also include filters to ensure your customers are dealing with a manageable size that fits your business
scenario.
Power BI template apps can execute multiple queries in parallel and for multiple users concurrently. Plan ahead
your throttling and concurrency strategy and ask us how to make your template app fault tolerant.
Schema enforcement
Ensure your queries are resilient to changes in your system, changes in schema on refresh can break the model. If
the source could return null or missing schema result for some queries, consider returning an empty table or a
meaningful custom error message.
Parameters
Parameters in Power BI Desktop allow your users to provide input values that customize the data retrieved by the
user. Think of the parameters up front to avoid rework after investing time to build detailed queries or reports.

NOTE
Template apps support all parameters except Any and Binary.

Additional query tips

Ensure all columns are typed appropriately.
Columns have informative names (see Q&A).
For shared logic, consider using functions or queries.
Privacy levels are currently not supported in the service. If you get a prompt about privacy levels, you may need
to rewrite the query to use relative paths.

Data models
A well-defined data model ensures your customers can easily and intuitively interact with the template app. Create
the data model in Power BI Desktop.

NOTE
You should do much of the basic modeling (typing, column names) in the queries.

Q&A
The modeling also affects how well Q&A can provide results for your customers. Ensure you add synonyms to
commonly used columns and you've properly named your columns in the queries.
Additional data model tips
Make sure you've:
Applied formatting to all value columns. Apply types in the query.
Applied formatting to all measures.
Set default summarization. Especially "Do Not Summarize", when applicable (for unique values, for example).
Set data category, when applicable.
Set relationships, as necessary.

Reports
The report pages offer additional insight into the data included in your template app. Use the pages of the reports
to answer the key business questions your template app is trying to address. Create the report using Power BI
Desktop.
Additional report tips
Use more than one visual per page for cross-filtering.
Align the visuals carefully (no overlapping).
Page is set to "4:3" or "16:9" mode for layout.
All of the aggregations presented make numeric sense (averages, unique values).
Slicing produces rational results.
Logo is present on at least the top report.
Elements are in the client's color scheme to the extent possible.
Dashboards
The dashboard is the main point of interaction with your template app for your customers. It should include an
overview of the content included, especially the important metrics for your business scenario.
To create a dashboard for your template app, just upload your PBIX through Get Data > Files or publish directly
from Power BI Desktop.
Additional dashboard tips
Maintain the same theme when pinning so that the tiles on your dashboard are consistent.
Pin a logo to the theme so consumers know where the pack is from.
Suggested layout to work with most screen resolutions is 5-6 small tiles wide.
All dashboard tiles should have appropriate titles/subtitles.
Consider groupings in the dashboard for different scenarios, either vertically or horizontally.

Sample data
Template apps, as part of the app creation stage, wraps the cache data in the workspace as part of the app:
Allows the installer to understand the functionality and purpose of the app before connecting data.
Creates an experience that drives the installer to further explore app capabilities, which leads to connecting the
app dataset.
We recommend having quality sample data before creating the app. ensure the app report and dashboards are
populated with data.

Publishing on AppSource
Template apps can be published on AppSource, follow these guidelines before submitting your app to AppSource:
Make sure you create a template app with engaging sample data that can help the installer understand what the
app can do (empty report & dashboard aren't approved). Template apps support sample data only apps, make
sure to check the static app checkbox. Learn more
Have instruction for the validation team to follow which includes credentials and parameters that are required
to connect to data.
Application must include an App icon in Power BI and on your CPP offer. Learn more
Landing page configured. Learn more
Make sure to follow the documentation on Partner center -> Power BI App offer.
In case a dashboard is part of your app, make sure it's not empty.
Install the app using the app link before submitting it, make sure you can connect the dataset and the app
experience is as you planned.
Before uploading pbix into the template workspace, make sure to unload any unnecessary connections.
Follow Power BI Best design practices for reports and visuals to achieve maximum impact on your users and
getting approved for distribution.

Create a download link for the app

After publishing the template app on AppSource, consider creating a download link from your website to either:
AppSource download page - can be viewed by publicly, get the link from your AppSource page.
Power BI - Can be viewed by a Power BI user.
In order to redirect a user to the app's download link in Power BI see the following code example: GitHub repo.
Next steps
What are Power BI template apps?
 Install and distribute template apps in your
organization
9/9/2020 • 5 minutes to read • Edit Online

Are you a Power BI analyst? If so, this article explains how you can install template apps to connect to many of the
services you use to run your business, such as Salesforce, Microsoft Dynamics, and Google Analytics. You can then
modify the template app's pre-built dashboard and reports to suit the needs of your organization, and distribute
them to your colleagues as apps.

If you're interested in creating template apps yourself for distribution outside your organization, see Create a
template app in Power BI. With little or no coding, Power BI partners can build Power BI apps and make them
available to Power BI customers.

Prerequisites
To install, customize, and distribute a template app, you need:
A Power BI pro license.
Permissions to install template apps on your tenant.
A valid installation link for the app, which you get either from AppSource or from the app creator.
A good familiarity with the basic concepts of Power BI .

Install a template app

1. In the nav pane in the Power BI service, select Apps > Get apps .
2. In the Power BI apps marketplace that appears, select Template apps . All the template apps available in
AppSource will be shown. Browse to find the template app you're looking for, or get a filtered selection by
using the search box. Typing part of the name of the template app, or of a category such as finance,
analytics, marketing, etc., will make it easier to find the item you're looking for.

3. When you find the template app you're looking for, click it. The template app offer will display. Click GET IT
NOW .
4. In the dialog box that appears, select Install .

The app is installed, along with a workspace of the same name that has all the artifacts needed for further
customization.

NOTE
If you use an installation link for an app that isn't listed on AppSource, a validation dialog box will ask you to confirm
your choice.
To be able to install a template app that is not listed on AppSource, you need to request the relevant permissions
from your admin. See the Template app settings in Power BI admin portal for details.

When the installation finishes successfully, a notification tells you that your new app is ready.
Connect to data
1. Select Go to app .
2. On the Get star ted with your new app window, select Explore .

The app opens, showing sample data.

3. Select the Connect your data link on the banner at the top of the page.
 This opens a dialog or series of dialogs where you change the data source from the sample data to your
own data source. This generally means redefining dataset parameters and data source credentials. See
Known limitations.
In the example below, connecting to data involves two dialogs.

Once you've finished filling out the connection dialogs, the connection process starts. A banner informs you
that the data is being refreshed, and that in the meantime you are viewing sample data.

Your report data will automatically refresh once a day, unless you disabled this during the sign-in process.
You can also set up your own refresh schedule to keep the report data up to date if you so desire.

Customize and share the app

After you've connected to your data and data refresh is complete, you can customize any of the reports and
dashboards the apps includes, as well as share the app with your colleagues. Remember, however that any
changes you make will be overwritten when you update the app with a new version, unless you save the items
you changed under different names. See details about overwriting.
To customize and share your app, select the pencil icon at the top right corner of the page.
For information about editing artifacts in the workspace, see
Tour the report editor in Power BI
Basic concepts for designers in the Power BI service
Once you are done making any changes you wish to the artifacts in the workspace, you are ready to publish and
share the app. See Publish your app to learn how to do this.

Update a template app

From time to time, template app creators release new improved versions of their template apps, via either
AppSource, direct link, or both.
If you originally downloaded the app from AppSource, when a new version of the template app becomes
available, you get notified in two ways:
An update banner appears in the Power BI service informing you that a new app version is available.

You receive a notification in Power BI's notification pane.

 NOTE
If you originally got the app via direct link rather than through AppSource, the only way to know when a new version is
available is to contact the template app creator.

To install the update, either click Get it on the notification banner or in the notification center, or find the app
again in AppSource and choose Get it now . If you got a direct link for the update from the Template app creator,
simply click the link.
You will be asked whether you wish to overwrite the current version, or to install the new version in a new
workspace. By default, "overwrite" is selected.
 Over write an existing version: Overwrites the existing workspace with the updated version of the
template app. See details about overwriting.
Install to a new workspace: Installs a fresh version of the workspace and app that you need to
reconfigure (that is, connect to data, define navigation and permissions).
Overwrite behavior
Overwriting updates the reports, dashboards, and dataset inside the workspace, not the app. Overwriting
doesn't change app navigation, setup, and permissions.
After you update the workspace, you need to update the app to apply changes from the
workspace to the app .
Overwriting keeps configured parameters and authentication. After update, an automatic dataset refresh
starts. During this refresh, the app, repor ts, and dashboards present sample data .

Overwriting always presents sample data until the refresh is complete. If the template app author made
changes to the dataset or parameters, users of the workspace and app will not see the new data until the
refresh is complete. Rather, they will continue to see sample data during this time.
Overwriting never deletes new reports or dashboards you've added to the workspace. It only overwrites
the original reports and dashboards with changes from the original author.

IMPORTANT
Remember to update the app after overwriting to apply changes to the reports and dashboard for your organizational app
users.

Next steps
Create workspaces with your colleagues in Power BI
 Update, delete, and extract template app
9/9/2020 • 3 minutes to read • Edit Online

Now that your app is in production, you can start over in the test phase, without disrupting the app in production.

Update your app

If you made the changes in Power BI Desktop, start at step (1). If you did not make the changes in Power BI Desktop,
start at step (4).
1. Upload the updated dataset and overwrite the existing dataset. Make sure to use the exact same
dataset name . Using a different name will create a new dataset for users that are updating the app.

2. Import the pbix file from your computer.

3. Confirm the overwrite.

4. In the Release management pane, select Create app .
5. Go back through the app creation process.
6. After you've set Branding , Content , Control , and Access , select Create app again.
7. Select Close and go back to Release management .
You see you have two versions now: The version in production, plus a new version in testing.
8. When you're ready to promote your app to pre-production for further testing outside your tenant, go back
to the Release Management pane and select Promote app next to Testing .
You now have a version in production and a version in pre-production.
 Your link is now live. Note that the Promote app button at the pre-production stage is greyed out .
This is to prevent accidentally overwriting the live production link to the current app version before the
Cloud Partner Portal has validated and approved the new app version.
9. Submit your link again to the Cloud Partner Portal (CPP) by following the steps at Power BI App offer update.
In the Cloud Partner Portal, you must publish your offer again and have it validated and approved.
When your offer is approved, the Promote app button will become active again.
10. Promote your app to the production stage.
Update behavior
1. Updating the app will allow the installer of the template app to Update a template app in the already installed
workspace without losing the connection configuration.
2. See installer overwrite behavior to learn how changes in the dataset affect the installed template app.
3. When updating (overwriting) a template app, it first reverts back to sample data and will automatically
 reconnect with user's configuration (parameters & authentication). Until refresh is complete, the reports,
dashboards, and org app will present the sample data banner.
4. If you added a new query parameter to the updated dataset that requires users input - you must check the
required check box. This will prompt the installer with the connection string after updating the app.

Extract workspace
Rolling back to the previous version of a template app is now easier than ever with the extract capability. The
following steps will extract a specific app version from various release stages into a new workspace:
1. In the release management pane, press more (...) and then Extract .
2. In dialog box, enter the name for extracted workspace. a new workspace will be added.
Your new workspace versioning resets and you can continue to develop and distribute the template app from the
newly extracted workspace.

Delete template app version

A template workspace is the source of an active distributed template app. To protect the template app users, it's not
possible to delete a workspace without first removing all the created app versions in the workspace. Deleting an
app version also deletes the app url that will no longer work.
1. In the release management pane, press select the ellipsis (...) and then Delete .
 NOTE
Make sure not to delete app version which are being used by customers or AppSource or they will no longer work.

Next steps
See how your customers interact with your template app in Install, customize, and distribute template apps in your
organization.
See the Power BI Application offer for details on distributing your app.
 Template apps samples
9/9/2020 • 2 minutes to read • Edit Online

The purpose of this document is sharing with Power BI users template apps samples. Use them for personal use or
for redistribution on AppSource. The Samples are in pbix file format and can be authored with Power BI desktop.

Connection, additional related accounts

The samples might require additional user accounts with the relevant service owner. The following templates are to
be used under the following License terms.

Downloadable Template apps samples

Template example for Template app creation
LinkedIn Sales Navigator Analytics Integration
Github
Mailchimp
QuickBooks Online
Google Analytics
Salesforce Sales Manager
Salesforce Sales Rep
Smartsheet
Zendesk
Marketo

Next steps
What are Power BI template apps?
 Troubleshooting refresh scenarios
9/9/2020 • 4 minutes to read • Edit Online

Here you can find information regarding different scenarios you may face when refreshing data within the Power
BI service.

NOTE
If you encounter a scenario that is not listed below, and it's causing you issues, you can ask for further assistance on the
community site, or you can create a support ticket.

You should always ensure that basic requirements for refresh are met and verified. These basic requirements
include:
Verify the gateway version is up to date
Verify the report has a gateway selected - if not, the datasource may have changed or might be missing
Once you've confirmed those requirements are met, take a look through the following sections for more
troubleshooting.

Email notifications
If you're coming to this article from an email notification, and you no longer want to receive emails about refresh
issues, contact your Power BI admin. Ask them to remove your email or an email list you're subscribed to from the
appropriate datasets in Power BI. They can do this from the following area in the Power BI admin portal.

Refresh using Web connector doesn't work properly

If you have a Web connector script that's using the Web.Page function, and you have updated your dataset or
report after November 18th, 2016, you must use a gateway for refresh to work properly.

Unsupported data source for refresh

When configuring a dataset, you may get an error indicating the dataset uses an unsupported data source for
refresh. For details, see Troubleshooting unsupported data source for refresh.

Dashboard doesn't reflect changes after refresh

Please wait about 10-15 minutes for a refresh to be reflected in the dashboard tiles. If it is still not showing up, re-
pin the visualization to the dashboard.

GatewayNotReachable when setting credentials

You may encounter GatewayNotReachable when trying to set credentials for a data source. This can be the result of
an outdated gateway. Install the latest gateway and try again.

Processing Error: The following system error occurred: Type Mismatch

This could be an issue with your M script within your Power BI Desktop file or Excel workbook. It can also be due
to an out-of-date Power BI Desktop version.

Tile refresh errors

For a list of errors you may encounter with dashboard tiles, and explanations, see Troubleshooting tile errors.

Refresh fails when updating data from sources that use AAD OAuth
The Azure Active Directory (AAD ) OAuth token, used by many different data sources, expires in approximately
one hour. You can run into situations where loading data takes longer than the token expiration (more than one
hour), since the Power BI service waits for up to two hours when loading data. In that situation, the data loading
process can fail with a credentials error.
Data sources that use AAD OAuth include Microsoft Dynamics CRM Online , SharePoint Online (SPO), and
others. If you’re connecting to such data sources, and get a credentials failure when loading data takes more than
an hour, this may be the reason.
Microsoft is investigating a solution that allows the data loading process to refresh the token and continue.
However, if your Dynamics CRM Online or SharePoint Online instance (or other AAD OAuth data source) is so
large that it can run into the two-hour data-load threshold, you may experience a data load timeout from the
Power BI service as well.
Also note that, for refresh to work properly, when connecting to a SharePoint Online data source using AAD
OAuth, you must use the same account that you use to sign in to the Power BI ser vice .

Uncompressed data limits for refresh

The maximum size for datasets imported into the Power BI ser vice is 1 GB. These datasets are heavily
compressed to ensure high performance. In addition, in shared capacity, the service places a limit on the amount
of uncompressed data that is processed during refresh to 10 GB. This limit accounts for the compression, and
therefore is much higher than 1 GB. Datasets in Power BI Premium are not subject to this limit. If refresh in the
Power BI service fails for this reason, please reduce the amount of data being imported to Power BI and try again.

Scheduled refresh timeout

Scheduled refresh for imported datasets timeout after two hours. This timeout is increased to five hours for
datasets in Premium workspaces. If you encounter this limit, consider reducing the size or complexity of your
dataset, or consider breaking the dataset into smaller pieces.

Scheduled refresh failures

If a scheduled refresh fails four times in a row, Power BI disables the refresh. Address the underlying problem, and
then re-enable the scheduled refresh.

Access to the resource is forbidden

This error can occur because of expired cached credentials. Clear your internet browser cache by going signing
into Power BI and going to https://app.powerbi.com?alwaysPromptForContentProviderCreds=true . This forces an
update of your credentials.

Data refresh failure because of password change or expired credentials

Data refresh can also fail due to expired cached credentials. Clear your internet browser cache by going signing
into Power BI and going to https://app.powerbi.com?alwaysPromptForContentProviderCreds=true . This forces an
update of your credentials.

Next steps
Data refresh in Power BI
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Microsoft Power BI Community
 Troubleshooting unsupported data source for refresh
9/9/2020 • 2 minutes to read • Edit Online

You may see an error when trying to configured a dataset for scheduled refresh.

You cannot schedule refresh for this dataset because it gets data from sources that currently don’t
support refresh.

This happens when the data source you used, within Power BI Desktop, isn’t supported for refresh. You will need to
find the data source that you are using and compare that against the list of supported data sources at Refresh data
in Power BI.

Find the data source

If you aren’t sure what data source was used, you can find that using the following steps within Power BI Desktop.
1. In Power BI Desktop, make sure you are on the Repor t pane.

2. Select Edit Queries from the ribbon bar.

3. Select Advanced Editor .

4. Make note of the provider listed for the source. In this example, the provider is ActiveDirectory.

5. Compare the provider with the list of supported data sources found in Power BI data sources.

NOTE
For refresh issues related to dynamic data sources, including data sources that include hand-authored queries, see refresh
and dynamic data sources.

Next steps
Data Refresh
Power BI Gateway - Personal
On-premises data gateway
Troubleshooting the On-premises data gateway
Troubleshooting the Power BI Gateway - Personal
More questions? Try asking the Power BI Community
 Troubleshooting scheduled refresh for Azure SQL
Databases in Power BI
9/9/2020 • 2 minutes to read • Edit Online

For detailed information about refresh, see Refresh data in Power BI and Configure scheduled refresh.
While setting up scheduled refresh for Azure SQL database, if you get an error with error code 400 when editing
the credentials, try the following to set up the appropriate firewall rule:
1. Sign in to the Azure portal.
2. Go to the Azure SQL database for which you're configuring refresh.
3. At the top of the Over view blade, select Set ser ver firewall .
4. On the Firewall settings blade, make sure that Allow access to Azure ser vices is set to ON .

More questions? Try the Power BI Community

 Troubleshooting Analyze in Excel
9/9/2020 • 4 minutes to read • Edit Online

There may be times when using Analyze in Excel that you get an unexpected result, or the feature doesn't work as
you expected. This page provides solutions for common issues when using Analyze in Excel.

NOTE
There's a separate page dedicated to describing and enabling Analyze in Excel.
If you encounter a scenario that is not listed below, and it is causing you issues, you can ask for further assistance on the
community site, or you can create a support ticket.

This article contains the following troubleshooting sections:

Update Excel libraries for the OLE DB provider
Determining whether you need to update your Excel libraries
Connection cannot be made error
Forbidden error
No data models
Token expired error
Unable to access on-premises Analysis services
Can't drag anything to the PivotTable Values area (no measures)

Update Excel libraries for the OLE DB provider

To use Analyze in Excel , your computer must have a current AS OLE DB provider installed. This community post is
a great source to verify your installation of the OLE DB provider, or to download a recent version.
The Excel libraries need to match your version of Windows in terms of its bit-level. If you have 64-bit Windows
installed, you need to install the 64-bit OLE DB provider.
To download the latest Excel libraries, visit Power BI and select the down arrow in the upper right corner of the
Power BI service, then select Analyze in Excel updates .

In the dialog that appears, select Download (preview) .

Determining whether you need to update your Excel libraries
You can download the most recent version of the Excel OLE DB provider libraries from the links in the previous
section. Once you download the appropriate OLD DB provider library and begin installation, checks are performed
against your current installed version.
If your Excel OLE DB provider client libraries are up to date, you'll be presented with a dialog that looks like the
following:

Alternatively, if the new version you are installing is newer than the version on your computer, the following dialog
appears:
If you see the dialog prompting you to upgrade, you should continue with the installation to get the most recent
version of the OLE DB provider installed in your computer.

Connection cannot be made error

The primary cause for a connection cannot be made error is that your computer's OLE DB provider client libraries
are not current. For information about how to determine the correct update, and for download links, see Update
Excel libraries for the OLE DB provider earlier in this article.

Forbidden error
Some users have more than one Power BI account, and when Excel attempts to connect to Power BI using existing
credentials, it may use credentials that do not have access to the dataset or report you want to access.
When this occurs, you may receive an error titled Forbidden , which means you may be signed into Power BI with
credentials that do not have permissions to the dataset. After encountering the forbidden error, when prompted to
enter your credentials, use the credentials that have permission to access the dataset you're trying to use.
If you still run into errors, log into Power BI with the account that has permission, and verify that you can view and
access the dataset in Power BI that you're attempting to access in Excel.

No data models
If you encounter an error that states Can't find OL AP cube model , then the dataset you're trying to access has
no data model, and therefore cannot be analyzed in Excel.

Token expired error

If you receive a token expired error, it means you haven't recently used the Analyze in Excel feature on the
computer you're using. Simply re-enter your credentials, or reopen the file, and the error should go away.

Unable to access on-premises Analysis Services

If you're trying to access a dataset that has connections to on-premises Analysis Services data, you may receive an
error message. Analyze in Excel does support connecting to datasets and reports on on-premises Analysis
Ser vices with a connection string, as long as your computer is on the same domain as the Analysis Ser vices
server, and your account has access to that Analysis Ser vices server.

Can't drag anything to the PivotTable Values area (no measures)

When Analyze in Excel connects to an external OLAP model (which is how Excel connects to Power BI), the
PivotTable requires measures to be defined in the external model, since all calculations are performed on the
server. This is different than when you work with a local data source (such as tables in Excel, or when you're
working with datasets in Power BI Desktop or the Power BI ser vice ), in which case the tabular model is
available locally, and you can use implicit measures, which are measures that are generated dynamically and are
not stored in the data model. In these cases, the behavior in Excel is different from the behavior in Power BI
Desktop or the Power BI ser vice : there may be columns in the data that can be treated as measures in Power BI,
but can't be used as values (measures) in Excel.
To address this issue, you have a few options:
1. Create measures in your data model in Power BI Desktop , then publish the data model to the Power BI
ser vice and access that published dataset from Excel.
2. Create measures in your data model from Excel PowerPivot.
3. If you imported data from an Excel workbook that had only tables (and no data model), then you can add the
tables to the data model, then follow the steps in option 2, directly above, to create measures in your data
model.
Once your measures are defined in the model in the Power BI service, you'll be able to use them in the Values area
in Excel PivotTables.

Next steps
Analyze in Excel
Tutorial: Create your own measures in Power BI Desktop
Measures in PowerPivot
Create a Measure in PowerPivot
Add worksheet data to a Data Model using a linked table
 Error: We couldn't find any data in your Excel
workbook
9/9/2020 • 2 minutes to read • Edit Online

NOTE
This article applies to Excel 2007 and later.

When you import an Excel workbook into Power BI, you may see the following error:
Error: We couldn't find any data formatted as a table. To import from Excel into the Power BI service, you need to
format the data as a table. Select all the data you want in the table and press Ctrl+T.

Quick solution
1. Edit your workbook in Excel.
2. Select the range of cells that contain your data. The first row should contain your column headers (the column
names).
3. Press Ctrl + T to create a table.
4. Save your workbook.
5. Return to Power BI and import your workbook again, or if you're working in Excel 2016 and you've saved your
workbook to OneDrive for Business, in Excel, click File > Publish.

Details
Cause
In Excel, you can create a table out of a range of cells, which makes it easier to sort, filter, and format data.
When you import an Excel workbook, Power BI looks for these tables and imports them into a dataset; if it doesn't
find any tables, you'll see this error message.
Solution
1. Open your workbook in Excel.

NOTE
The pictures here are of Excel 2013. If you're using a different version, things may look a little different, but the steps
are the same.
2. Select the range of cells that contain your data. The first row should contain your column headers (the
column names):

3. In the ribbon on the INSERT tab, click Table . (Or, as a shortcut, press Ctrl + T .)
4. You'll see the following dialog. Make sure My table has headers is checked, and select OK :

5. Now your data is formatted as a table:

6. Save your workbook.

7. Return to Power BI. Select Get Data at the bottom of the nav pane.
8. In the Files box, select Get .

9. Import your Excel workbook again. This time, the import should find the table and succeed.
If the import still fails, let us know by clicking **Community **in the help menu:
 How to refresh your Xero content pack credentials if
refresh failed
9/9/2020 • 2 minutes to read • Edit Online

If you use the Xero Power BI content pack, you may have experienced some problems with the content pack’s daily
refresh due to a recent Power BI service incident.
You can see if your content pack refreshed successfully by checking the last refresh status for your Xero dataset as
shown in the screenshot below.

If you do see that refresh failed as shown above, please follow these steps to renew your content pack credentials.
1. Click More options (...) next to your Xero dataset, then click Schedule refresh . This opens the settings
page for the Xero content pack.

2. In the Settings for Xero page, select Data source credentials > Edit credentials .
3. Enter your organization’s name > Next .

4. Sign in with your Xero account.

5. Now that your credentials are updated, let’s make sure the refresh schedule is set to run daily. Check that by
clicking More options (...) next to your Xero dataset, then clicking Schedule refresh again.

6. You can also choose to refresh the dataset immediately. Click More options (...) next to your Xero dataset,
then click Refresh now .

If you are still having refresh issues, please don’t hesitate to reach out to us at https://support.powerbi.com
To learn more about the Xero content pack for Power BI, please visit the Xero content pack help page.
Next steps
More questions? Try the Power BI Community
 Connect to the services you use with Power BI
9/9/2020 • 2 minutes to read • Edit Online

With Power BI, you can connect to many of the services you use to run your business, such as Salesforce, Microsoft
Dynamics, and Google Analytics. Power BI starts by using your credentials to connect to the service. It creates a
Power BI workspace with a dashboard and a set of Power BI reports that automatically show your data and provide
visual insights about your business.

IMPORTANT
Service content packs are being replaced by Template apps. As of September 25, 2019, a number of content packs have
already been deprecated. Any deprecated content pack that you have installed will remain in your account, but no
documentation or support will be provided for it, nor will it be possible to install it again.

Sign in to Power BI to view all of the services you can connect to.

After you install the app, you can view the dashboard and reports in the app and the workspace in the Power BI
service (https://app.powerbi.com). You can also view them in the Power BI mobile apps. In the workspace, you can
modify the dashboard and reports to meet the needs of your organization, and then distribute them to your
colleagues as an app.
Get started
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

Edit the dashboard and reports

When the import is complete, the new app appears on the Apps page.
1. Select Apps in the nav pane > select the app.

2. You can ask a question by typing in the Q&A box, or click a tile to open the underlying report.

Change the dashboard and report to fit the needs of your organization. Then distribute your app to your
colleagues

What's included
After connecting to a service, you see a newly created app and workspace with a dashboard, reports, and dataset.
The data from the service is focused on a specific scenario and may not include all the information from the
service. The data is scheduled to refresh automatically once per day. You can control the schedule by selecting the
dataset.
You can also connect to many services in Power BI Desktop, such as Google Analytics, and create your own
customized dashboards and reports.
For more details on connecting to specific services, refer to the individual help pages.

Troubleshooting
Empty tiles
While Power BI is first connecting to the service, you may see an empty set of tiles on your dashboard. If you still
see an empty dashboard after 2 hours, it's likely the connection failed. If you didn't see an error message with
information on correcting the issue, file a support ticket.
Select the question mark icon (? ) in the upper-right corner > Get help .

Missing information
The dashboard and reports include content from the service focused on a specific scenario. If you're looking for a
specific metric in the app and don't see it, add an idea on the Power BI Support page.

Suggesting services
Do you use a service you'd like to suggest for a Power BI app? Go to the Power BI Support page and let us know.
If you're interested in creating template apps to distribute yourself, see Create a template app in Power BI. Power BI
partners can build Power BI apps with little or no coding, and deploy them to Power BI customers.

Next steps
Distribute apps to your colleagues
Create the new workspaces in Power BI
Questions? Try asking the Power BI Community
 Connect to the COVID-19 US tracking report
9/9/2020 • 2 minutes to read • Edit Online

This article tells you how to install the template app for the COVID-19 tracking report, and how to connect to the
data sources.

For detailed information about the report itself, including disclaimers and information about the data, see COVID-
19 tracking sample for US state and local governments.
After you've installed the template app and connected to the data sources, you can customize the report as per your
needs. You can then distribute it as an app to colleagues in your organization.

Install the app

1. Click the following link to get to the app: COVID-19 US Tracking Report template app
2. Once you're on the App's Appsource page, click GET IT NOW .

3. When prompted , click Install . Once the app has installed, you will see it on your Apps page.
Connect to data sources
1. Click the icon on your Apps page to open the app.
2. On the splash screen that appears choose Connect .

3. Two sign-in dialogs will appear, one after another. On both, set the privacy level to Public.
 The report will connect to the data sources and be populated with up-to-date data. During this time the
activity monitor will turn.

Schedule report refresh

When the data refresh has completed, you will be in the workspace associated with the app. Set up a refresh
schedule to keep the report data up to date.

Customize and share

See Customize and share the app for details. Be sure to review the report disclaimers before publishing or
distributing the app.
Next steps
COVID-19 tracking sample for US state and local governments
Questions? Try asking the Power BI Community
What are Power BI template apps?
Install and distribute template apps in your organization
 Connect to the Crisis Communication Presence
Report
9/9/2020 • 2 minutes to read • Edit Online

This Power BI app is the report/dashboard artifact in the Microsoft Power Platform solution for Crisis
Communication. It tracks worker location for Crisis Communication app users. The solution combines capabilities
of Power Apps, Power Automate, Teams, SharePoint and Power BI. It can be used on the web, mobile or in Teams.

The dashboard shows emergency managers aggregate data across their health system to help them to make
timely, correct decisions.
This article tells you how to install the app and how to connect to the data sources. For more information about the
Crisis Communication app, see Set up and learn about the Crisis Communication sample template in Power Apps
After you've installed the template app and connected to the data sources, you can customize the report as per your
needs. You can then distribute it as an app to colleagues in your organization.

Prerequisites
Before installing this template app, you must first install and set up the Crisis Communication sample. Installing this
solution creates the datasource references necessary to populate the app with data.
When installing the Crisis Communication sample, take note of the SharePoint list folder path of "CI_Employee
Status" and list ID.

Install the app

1. Click the following link to get to the app: Crisis Communication Presence Report template app
2. On the AppSource page for the app, select GET IT NOW .
3. Read the information in One more thing , and select Continue .

4. Select Install .

Once the app has installed, you see it on your Apps page.
Connect to data sources
1. Select the icon on your Apps page to open the app.
2. On the splash screen, select Explore .

The app opens, showing sample data.

3. Select the Connect your data link on the banner at the top of the page.
4. In the dialog box:
a. In the SharePoint_Folder field, enter your "CI_Employee Status" SharePoint list path.
b. In the List_ID field, enter your list id that you got from list settings. When done, click Next .

5. In the next dialog that appears, set the authentication method to OAuth2 . You don't have to do anything to
the privacy level setting.
Select Sign in .

6. At the Microsoft sign-in screen, sign in to Power BI.

 After you've signed in, the report connects to the data sources and is populated with up-to-date data. During
this time, the activity monitor turns.

Schedule report refresh

When the data refresh has completed, set up a refresh schedule to keep the report data up to date.
1. In the top header bar, select Power BI .

2. In the left navigation pane, look for the Hospital Emergency Response Decision Support Dashboard
workspace under Workspaces , and follow the instruction described in the Configure scheduled refresh
article.

Customize and share

See Customize and share the app for details. Be sure to review the report disclaimers before publishing or
distributing the app.

Next steps
Set up and learn about the Crisis Communication sample template in Power Apps
Questions? Try asking the Power BI Community
What are Power BI template apps?
Install and distribute template apps in your organization
 Connect to GitHub with Power BI
9/9/2020 • 4 minutes to read • Edit Online

This article walks you through pulling your data from your GitHub account with a Power BI template app. The
template app generates a workspace with a dashboard, a set of reports, and a dataset to allow you to explore your
GitHub data. The GitHub app for Power BI shows you insights into your GitHub repository, also known as repo, with
data around contributions, issues, pull requests, and active users.

After you've installed the template app, you can change the dashboard and report. Then you can distribute it as an
app to colleagues in your organization.
Connect to the GitHub template app or read more about the GitHub integration with Power BI.
You can also try the GitHub tutorial. It installs real GitHub data about the public repo for the Power BI
documentation.

NOTE
This template app requires the GitHub account to have access to the repo. More details on requirements below.
This template app does not support GitHub Enterprise.

Install the app

1. Click the following link to get to the app: GitHub template app
2. On the AppSource page for the app, select GET IT NOW .
3. Select Install .

Once the app has installed, you see it on your Apps page.

Connect to data sources

1. Select the icon on your Apps page to open the app.
2. On the splash screen, select Explore app .

The app opens, showing sample data.

3. Select the Connect your data link on the banner at the top of the page.

4. In the dialog box that appears, enter the repository name and repository owner of the repo. See details on
finding these parameters below. When done, click Next .
5. In the next dialog that appears, make sure the authentication method is set to OAuth2 . You don't have to do
anything to the privacy setting. When you're ready, click Sign in .

6. Enter your GitHub credentials and follow the GitHub authentication process (this step might be skipped if
you're already signed in with your browser).
After you've signed in, the report connects to the data sources and is populated with up-to-date data. During this
time, the activity monitor turns.

Your report data will automatically refresh once a day, unless you disabled this during the sign-in process. You can
also set up your own refresh schedule to keep the report data up to date if you so desire.

Customize and share

To customize and share your app, select the pencil icon at the top right corner of the page.
For information about editing artifacts in the workspace, see
Tour the report editor in Power BI
Basic concepts for designers in the Power BI service
Once you are done making any changes you wish to the artifacts in the workspace, you are ready to publish and
share the app. See Publish your app to learn how to do this.

What's included in the app

The following data is available from GitHub in Power BI:

TA B L E N A M E DESC RIP T IO N

Contributions The contributions table gives the total additions, deletions,

and commits authored by the contributor aggregated per
week. The top 100 contributors are included.

Issues List all issues for the selected repo and it contains calculations
like total and average time to close an issue, Total open issues,
Total closed issues. This table will be empty when there are no
issues in the repo.

Pull requests This table contains all the Pull Requests for the repo and who
pulled the request. It also contains calculations around how
many open, closed, and total pull requests, how long it took to
pull the requests and how long the average pull request took.
This table will be empty when there are no pull requests in the
repo.

Users This table provides a list of GitHub users or contributors who

have made contributions, filed issues, or solved Pull requests
for the repo selected.

Milestones It has all the Milestones for the selected repo.

DateTable This table contains dates from today and for years in the past
that allow you to analyze your GitHub data by date.

ContributionPunchCard This table can be used as a contribution punch card for the
selected repo. It shows commits by day of week and hour of
day. This table is not connected to other tables in the model.
 TA B L E N A M E DESC RIP T IO N

RepoDetails This table provides details for the repo selected.

System requirements
The GitHub account that has access to the repo.
Permission granted to the Power BI for GitHub app during first login. See details below on revoking access.
Sufficient API calls available to pull and refresh the data.

NOTE
This template app does not support Github Enterprise.

De -authorize Power BI
To de-authorize Power BI from being connected to your GitHub repo, you can Revoke access in GitHub. See this
GitHub help topic for details.

Finding parameters
You can determine the owner and repository by looking at the repository in GitHub itself:

The first part "Azure" is the owner and the second part "azure-sdk-for-php" is the repository itself. You see these
same two items in the URL of the repository:

<https://github.com/Azure/azure-sdk-for-php> .

Troubleshooting
If necessary, you can verify your GitHub credentials.
1. In another browser window, go to the GitHub web site and sign in to GitHub. You can see you’re logged in, in the
upper-right corner of the GitHub site.
2. In GitHub, navigate to the URL of the repo you plan to access in Power BI. For example:
https://github.com/dotnet/corefx.
3. Back in Power BI, try connecting to GitHub. In the Configure GitHub dialog box, use the names of the repo and
repo owner for that same repo.

Next steps
Tutorial: Connect to a GitHub repo with Power BI
Create the new workspaces in Power BI
Install and use apps in Power BI
Connect to Power BI apps for external services
Questions? Try asking the Power BI Community
 Connect to the Hospital Emergency Response
Decision Support Dashboard
9/9/2020 • 2 minutes to read • Edit Online

The Hospital Emergency Response Decision Support Dashboard template app is the reporting component of the
Microsoft Power Platform solution for healthcare emergency response. The dashboard shows emergency managers
aggregate data across their health system to help them to make timely, correct decisions.

This article tells you how to install the app and how to connect to the data sources. To learn how to use the report
that you will see with this app, see the Hospital Emergency Response Decision Support Dashboard documentation.
After you've installed the template app and connected to the data sources, you can customize the report as per your
needs. You can then distribute it as an app to colleagues in your organization.

Prerequisites
Before installing this template app, you must first install and set up the Hospital Emergency Response Power
Platform solution. Installing this solution creates the datasource references necessary to populate the app with data.
When installing Hospital Emergency Response Power Platform solution, take note of the URL of your Common
Data Service environment instance. You will need it to connect the template app to the data.

Install the app

1. Click the following link to get to the app: Hospital Emergency Response Decision Support Dashboard
template app
2. On the AppSource page for the app, select GET IT NOW .
3. Read the information in One more thing , and select Continue .

4. Select Install .

Once the app has installed, you see it on your Apps page.
Connect to data sources
1. Select the icon on your Apps page to open the app.
2. On the splash screen, select Explore .

The app opens, showing sample data.

3. Select the Connect your data link on the banner at the top of the page.
4. In the dialog box:
a. In the organization name field, enter the name of your organization, for example, "Contoso Health
Systems". This field is optional. This name appears in the upper-left side of the dashboard.
b. In the CDS_base_solution field, Type the URL of your Common Data Service environment instance. For
example: https://[myenv].crm.dynamics.com. When done, click Next .

5. In the next dialog that appears, set the authentication method to OAuth2 . You don't have to do anything to
the privacy level setting.
Select Sign in .
6. At the Microsoft sign-in screen, sign in to Power BI.

After you've signed in, the report connects to the data sources and is populated with up-to-date data. During
this time, the activity monitor turns.
Schedule report refresh
When the data refresh has completed, set up a refresh schedule to keep the report data up to date.
1. In the top header bar, select Power BI .

2. In the left navigation pane, look for the Hospital Emergency Response Decision Support Dashboard
workspace under Workspaces , and follow the instructions described in the Configure scheduled refresh
article.

Customize and share

See Customize and share the app for details. Be sure to review the report disclaimers before publishing or
distributing the app.

Next steps
Understanding the Hospital Emergency Response report
Set up and learn about the Crisis Communication sample template in Power Apps
Questions? Try asking the Power BI Community
What are Power BI template apps?
Install and distribute template apps in your organization
 Connect the Microsoft Sustainability Calculator
9/9/2020 • 2 minutes to read • Edit Online

Gain insights into the carbon emissions of your IT infrastructure to make more sustainable computing decisions
The Microsoft Sustainability Calculator provides new insight into carbon emissions data associated with Azure
services. Those responsible for reporting on and driving sustainability within their organizations now have the
ability to quantify the carbon impact of each Azure subscription, as well as see estimated carbon savings from
running those workloads in Azure versus on-premises datacenters. This data may be used for greenhouse gas
reporting of scope 3 emissions. Access to the Microsoft Sustainability Calculator will require your tenant ID and
access key, typically available through your organization’s Azure administrator.
To use this app, you will need information from the Azure Enterprise Portal. Your enterprise’s system administrators
may be able to help you obtain this information. Please review these instructions and obtain the required
information prior to installing the App.
This connector version only supports enterprise enrollments from https://ea.azure.com. China enrollments aren't
currently supported.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.
1. Select Microsoft Sustainability Calculator > Get it now .
2. In Install this Power BI App? select Install .
3. In the Apps pane, select the Microsoft Sustainability Calculator tile.
4. In Get star ted with your new app , select Connect .

5. Enter the Company name, User enrollment number, and Number of months > Sign In. See details
on finding these parameters below.

6. For Authentication method , select Key , and for Privacy level , select Organizational .
7. For Key , enter your Access key > Sign In .
8. The import process begins automatically. When complete, a new dashboard, report, and model appear in the
Navigation Pane . Select the report to view your imported data.

Finding parameters
To find your company Enrollment ID and Access key , work with your Azure administrator to get the required
information. Your administrator will
1. Log into the Azure enterprise Portal, and click on Manage on the left-hand ribbon and obtain the Enrollment
Number as shown below
2. From the Azure Enterprise Portal, click on Repor ts and then API Access Key, as shown below to obtain the
Primary Enrollment Account Key

Using the App

To update the parameters at any point, navigate to the Dataset settings and access the associated with the app
workspace, and update the tenant ID, company name, or months of data. After applying your parameters, click
Refresh to reload the data with the new parameters applied.
 Connect to Office365Mon with Power BI
9/9/2020 • 2 minutes to read • Edit Online

Analyzing your Office 365 outages and health performance data is easy with Power BI and the Office365Mon
template app. Power BI retrieves your data, including outages and health probes, then builds an out-of-box
dashboard and reports based on that data.
Connect to the Office365Mon template app for Power BI.

NOTE
An Office365Mon admin account is required to connect and load the Power BI template app.

How to connect
1. Select Get Data at the bottom of the nav pane.

2. In the Ser vices box, select Get .

3. Select Office365Mon > Get .

4. For Authentication Method, select oAuth2 > Sign In .

 When prompted, enter your Office365Mon admin credentials and follow the authentication process.

5. After Power BI imports the data you will see a new dashboard, report, and dataset in the nav pane. New
items are marked with a yellow asterisk *, select the Office365Mon entry.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Troubleshooting
If you get a "login failed" error after using your Office365Mon subscription credentials to login, then the account
you are using doesn't have permissions to retrieve the Office365Mon data from your account. Verify it is an admin
account and try again.

Next steps
What is Power BI?
Get Data for Power BI
 Connect to Power BI Premium Capacity Metrics
9/9/2020 • 2 minutes to read • Edit Online

Monitoring your capacities is essential to making informed decisions on how best to utilize your Premium capacity
resources. The Power BI Premium Capacity Metrics app provides the most in-depth information into how your
capacities are performing.

This article describes how to install the app and connect to data sources. For information about the contents of the
report and how to use it, see Monitor Premium capacities with the app, and the Premium Capacity Metrics app blog
post.
After you've installed the app and connected to the data sources, you can customize the report as per your needs.
You can then distribute it to colleagues in your organization.

NOTE
Installing template apps requires permissions. Contact you tenant admin if you find you don't have sufficient permissions.

Install the app

1. Click the following link to get to the app: Power BI Premium Capacity Metrics template app
2. On the AppSource page for the app, select GET IT NOW .
3. Select Install .

NOTE
If you've installed the app previously, you will be asked whether you want to overwrite that installation or install to a
new workspace.

Once the app has installed, you see it on your Apps page.
Connect to data sources
1. Select the icon on your Apps page to open the app.
2. On the splash screen, select Explore .

The app opens, showing sample data.

3. Select the Connect your data link on the banner at the top of the page.
4. In the dialog box that appears, set the UTC offset, that is, the difference in hours between Coordinated
Universal Time and the time in your location. Then click Next .

Note:
The format for half hours should be decimal (for example, 5.5, 2.5, etc.).
5. In the next dialog that appears, you don't have to do anything. Just select Sign in .
6. At the Microsoft sign-in screen, sign in to Power BI.

After you've signed in, the report connects to the data sources and is populated with up-to-date data. During
this time, the activity monitor turns.
 Your report data will automatically refresh once a day, unless you disabled this during the sign-in process.
You can also set up your own refresh schedule to keep the report data up to date if you so desire.

Customize and share

To start customizing the app, click the pencil icon in the upper right corner.

See Customize and share the app for details.

Next steps
Monitor Premium capacities with the app
Premium Capacity Metrics app blog post
What are Power BI template apps?
Install and distribute template apps in your organization
Questions? Try asking the Power BI Community
 Connect to Project Web App with Power BI
9/9/2020 • 2 minutes to read • Edit Online

Microsoft Project Web App is a flexible online solution for project portfolio management (PPM) and everyday work.
Project Web App enables organizations to get started, prioritize project portfolio investments and deliver the
intended business value. The Project Web App Template App for Power BI allows you to unlock insight from Project
Web App to help manage projects, portfolios and resources.
Connect to the Project Web App Template App for Power BI.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper right corner.

2. In the Ser vices box, select Get .

3. In AppSource, select the Apps tab, and search/select Microsoft Project Web App .
4. You will get a message saying - Install this Power BI App? select Install .
5. In the Apps pane, select the Microsoft Project Web App tile.

6. In Get star ted with your new app , select Connect data .

7. In the Project Web App URL text box, enter the URL for the Project Web App (PWA) you want to connect
to. Note this may differ from the example if you have a custom domain. In the PWA Site Language text
box, type the number that corresponds to your PWA site language. Type the single digit '1' for English, '2' for
French, '3' for German, '4' for Portuguese (Brazil), '5' for Portuguese (Portugal) and '6' for Spanish.
 8. For Authentication Method, select oAuth2 > Sign In . When prompted, enter your Project Web App
credentials and follow the authentication process.

NOTE
You need to have Portfolio Viewer, Portfolio Manager, or Administrator permissions for the Project Web App you are
connecting to.

9. You’ll see a notification indicating your data is loading. Depending on the size of your account this may take
some time. After Power BI imports the data, you will see the contents of your new workspace. You may need
to refresh the dataset to get the latest updates.
After Power BI imports the data you will see the report with 13 pages and dataset in the nav pane.
10. Once your reports are ready, go ahead and start exploring your Project Web App data! The Template App
comes with 13 rich and detailed reports for the Portfolio Overview (6 report pages), Resource Overview (5
report pages) and Project Status (2 report pages).
What now?
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now .
Expand the Template App
Download the GitHub PBIT file to further customize and update the Content Pack.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to QuickBooks Online with Power BI
9/9/2020 • 2 minutes to read • Edit Online

When you connect to your QuickBooks Online data from Power BI you immediately get a Power BI dashboard and
Power BI reports that provide insights about your business cash flow, profitability, customers, and more. Use the
dashboard and reports as they are, or customize them to highlight the information you care most about. The data is
refreshed automatically once a day.
Connect to the QuickBooks Online template app for Power BI.

NOTE
To import your QuickBooks Online data into Power BI, you need to be an admin on your QuickBooks Online account and
sign in with your admin account credentials. You can't use this connector with QuickBooks Desktop software.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select QuickBooks Online , then select Get .

4. In Install this Power BI app? select Install .

5. In the Apps pane, select the QuickBooks tile.

6. In Get star ted with your new app , select Connect .

 7. Select oAuth2 for Authentication Method and select Sign In .
8. When prompted, enter your QuickBooks Online credentials and follow the QuickBooks Online authentication
process. If you are already signed in to QuickBooks Online in your browser, you may not be prompted for
credentials.

NOTE
You need admin credentials for your QuickBooks Online account.

9. Select the company you would like to connect to Power BI in the next screen.

10. Select Authorize in the next screen to begin the import process. The process can take a few minutes
depending on the size of your company data.

11. After Power BI imports the data, you see the content list for your QuickBooks app: a new dashboard, report,
and dataset.
12. Select the QuickBooks dashboard to start the exploration process. Power BI created this dashboard
 automatically to display your imported data.

What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

Troubleshooting
"Oops! An error has occurred"
If you get this message after selecting Authorize :
“Oops! An error has occurred." Close this window and try again.
The application has already been subscribed to by another user for this company. Contact [admin email] to make
changes to this subscription.”

... this error means another admin in your company has already connected to your company data with Power BI.
Ask that admin to share the dashboard with you. Currently, only one admin user can connect a particular
QuickBooks Online company dataset to Power BI. After Power BI creates the dashboard, the admin can share it with
multiple colleagues on the same Power BI tenants.
"This app is not set up to allow connections from your countr y"
Currently Power BI only supports US editions of QuickBooks Online.

Next steps
What is Power BI?
Basic concepts for designers in the Power BI service
 Connect to the Regional Emergency Response
Dashboard
9/9/2020 • 2 minutes to read • Edit Online

The Regional Emergency Response Dashboard is the reporting component of the Microsoft Power Platform
Regional Emergency Response solution. Regional organization admins can view the dashboard in their Power BI
tenant, enabling them to quickly view important data and metrics that will help them make efficient decisions.

This article tells you how to install the Regional Emergency Response app using the Regional Emergency Response
Dashboard template app, and how to connect to the data sources.
For detailed information about what is presented in the dashboard, see Get insights.
After you've installed the template app and connected to the data sources, you can customize the report as per your
needs. You can then distribute it as an app to colleagues in your organization.

Prerequisites
Before installing this template app, you must first install and set up the Regional Emergency Response solution.
Installing this solution creates the datasource references necessary to populate the app with data.
When installing Regional Emergency Response solution, take note of the URL of your Common Data Service
environment instance. You will need it to connect the template app to the data.

Install the app

1. Click the following link to get to the app: Regional Emergency Response Dashboard template app
2. On the AppSource page for the app, select GET IT NOW .
3. Select Install .

Once the app has installed, you see it on your Apps page.

Connect to data sources

1. Select the icon on your Apps page to open the app.
2. On the splash screen, select Explore .
 The app opens, showing sample data.
3. Select the Connect your data link on the banner at the top of the page.

4. In the dialog box that appears, type the URL of your Common Data Service environment instance. For
example: https://[myenv].crm.dynamics.com. When done, click Next .
5. In the next dialog that appears, set the authentication method to OAuth2 . You don't have to do anything to
the privacy level setting.
Select Sign in .

6. At the Microsoft sign-in screen, sign in to Power BI.

After you've signed in, the report connects to the data sources and is populated with up-to-date data. During
this time, the activity monitor turns.
Schedule report refresh
When the data refresh has completed, set up a refresh schedule to keep the report data up to date.
1. In the top header bar, select Power BI .

2. In the left navigation pane, look for the Regional Emergency Response Dashboard workspace under
Workspaces , and follow the instructions described in the Configure scheduled refresh article.

Customize and share

See Customize and share the app for details. Be sure to review the report disclaimers before publishing or
distributing the app.

Next steps
Understanding the Regional Emergency Response dashboard
Set up and learn about the Crisis Communication sample template in Power Apps
Questions? Try asking the Power BI Community
What are Power BI template apps?
Install and distribute template apps in your organization
 Connect to Salesforce with Power BI
9/9/2020 • 2 minutes to read • Edit Online

With Power BI, you can easily connect to your Salesforce.com account. With this connection, you can retrieve your
Salesforce data and have a dashboard and reports automatically provided.
Read more about the Salesforce integration with Power BI.

How to connect
1. In Power BI, select Get Data at the bottom of the nav pane.

2. In the Ser vices box, select Get .

3. Select Analytics for Salesforce and select Get .

4. Select Sign In to start the sign in flow.

5. When prompted, enter your Salesforce credentials. Select Allow and let Power BI access your basic
Salesforce information and data.

6. Configure what you'd like to import into Power BI using the drop-down option:
Dashboard
Select a predefined dashboard based on a persona (such as Sales Manager ). These dashboards
retrieve a specific set of Salesforce standard data, which doesn't include custom fields.

Repor ts
Select one or more custom reports from your Salesforce account. These reports match your views in
Salesforce and can include data from custom fields or objects.
 If you don't see any reports, add or create them in your Salesforce account and try connecting again.
7. Select Connect to begin the import process. During the import, you see a notification showing the import is
in progress. When the import is complete, you see a dashboard, report, and dataset for your Salesforce data
listed in the nav pane.

You can change the dashboard to display your data how you'd like. You can ask questions with Q&A or select a tile
to open the underlying report and edit or remove dashboard tiles.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Edit or remove a tile in the dashboard
Select a tile to open the underlying report
While your dataset is scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

System requirements and considerations

Connected with a production Salesforce account that has API access enabled
Permission granted to the Power BI app during sign in
 The account has sufficient API calls available to pull and refresh the data
A valid authentication token is required for refresh. Salesforce has a limit of five authentication tokens per
application so make sure you've five or less Salesforce data sets imported.
The Salesforce Reports API has a restriction that supports up to 2,000 rows of data.

Troubleshooting
If you come across any errors, review the requirements above.
Signing in to a custom or sandbox domain isn't currently supported.
"Unable to connect to the remote server" message
If you get an "Unable to connect to the remote server" message when trying to connect to your Salesforce account,
see this solution on the following forum: Salesforce Connector sign in Error Message: Unable to connect to the
remote server

Next steps
What is Power BI?
Data sources for the Power BI service
 Connect to Smartsheet with Power BI
9/9/2020 • 2 minutes to read • Edit Online

This article walks you through pulling your data from your Smartsheet account with a Power BI template app.
Smartsheet offers an easy platform for collaboration and file sharing. The Smartsheet template app for Power BI
provides a dashboard, reports, and dataset that show an overview of your Smartsheet account. You can also use
Power BI Desktop to connect directly to individual sheets in your account.
After you've installed the template app, you can change the dashboard and report. Then you can distribute it as an
app to colleagues in your organization.
Connect to the Smartsheet template app for Power BI.

NOTE
A Smartsheet admin account is preferred for connecting and loading the Power BI template app as it has additional access.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Smar tsheet > Get it now .

4. In Install this Power BI App? select Install .
5. In the Apps pane, select the Smar tsheet tile.

6. In Get star ted with your new app , select Connect .

7. For Authentication Method, select oAuth2 > Sign In .

When prompted, enter your Smartsheet credentials and follow the authentication process.
8. After Power BI imports the data, the Smartsheet dashboard opens.
Modify and distribute your app
You've installed the Smartsheet template app. That means you've also created the Smartsheet workspace. In the
workspace, you can change the report and dashboard, and then distribute it as an app to colleagues in your
organization.
1. To view all the contents of your new Smartsheet workspace, in the nav pane, select Workspaces >
Smar tsheet .

This view is the content list for the workspace. In the upper-right corner, you see Update app . When you're
ready to distribute your app to your colleagues, that's where you'll start.
2. Select Repor ts and Datasets to see the other elements in the workspace.
Read about distributing apps to your colleagues.

What's included
The Smartsheet template app for Power BI includes an overview of your Smartsheet account, such as the number
of workspaces, reports, and sheets you have, when they're modified etc. Admin users also see some information
around the users in their system, such as top sheet creators.
To connect directly to individual sheets in your account, you can use the Smartsheet connector in the Power BI
Desktop.

Next steps
Create the new workspaces in Power BI
Install and use apps in Power BI
COnnect to Power BI apps for external services
Questions? Try asking the Power BI Community
 Connect to Xero with Power BI
9/9/2020 • 3 minutes to read • Edit Online

Xero is easy to use online accounting software that's designed specifically for small businesses. Create compelling
visualizations based on your Xero financials with this Power BI template app. Your default dashboard includes many
small business metrics like cash position, revenue vs. expenses, profit loss trend, debtor days, and return on
investment.
Connect to the Xero template app for Power BI or learn more about the Xero and Power BI integration.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.

3. Select Xero > Get it now .

4. In Install this Power BI app? select Install .
5. In the Apps pane, select the Xero tile.

6. In Get star ted with your new app , select Connect .

7. Enter a nickname for the organization associated with your Xero account. Anything will do, it's mostly to
help users with multiple Xero organizations keep them all straight. See details on finding parameters later in
this article.
8. For Authentication Method , select OAuth . When prompted sign into your Xero account and select the
organization to connect to. Once sign-in is complete, select Sign In to start the loading process.
9. After approving, the import process will begin automatically. When complete, a new dashboard, report, and
model will appear in the nav pane. Select the dashboard to view your imported data.
What now?
Try asking a question in the Q&A box at the top of the dashboard
Change the tiles in the dashboard.
Select a tile to open the underlying report.
While your dataset will be scheduled to refresh daily, you can change the refresh schedule or try refreshing it on
demand using Refresh Now

What's included
The template app dashboard includes tiles and metrics that cover a variety of areas, with corresponding reports to
learn more:

A REA DA SH B O A RD T IL ES REP O RT

Cash Daily cash flow Bank Accounts

Cash in
Cash out
Closing balance by account
Closing balance today

Customer Invoiced sales Customer

Invoiced sales by customer Inventory
Invoiced sales growth trend
Invoices due
Outstanding receivables
Overdue receivables
 A REA DA SH B O A RD T IL ES REP O RT

Supplier Billed purchases Suppliers

Billed purchases by supplier Inventory
Billed purchases growth trend
Bills due
Outstanding payables
Overdue payables

Inventory Monthly sales amount by product Inventory

Profit and loss Monthly profit and loss Profit and Loss
Net profit this fiscal year
Net profit this month
Top expense accounts

Balance sheet Total assets Balance Sheet

Total liabilities
Equity

Health Current ratio Health

Gross profit percentage Glossary and Technical Notes
Return on total assets
Total liabilities to equity ratio

The dataset also includes the following tables to customize your reports and dashboards:
Addresses
Alerts
Bank Statement Daily Balance
Bank Statements
Contacts
Expense Claims
Invoice Line Items
Invoices
Items
Month End
Organization
Trial Balance
Xero Accounts

System requirements
The following roles are required to access the Xero template app: "Standard + Reports" or "Advisor".

Finding parameters
Provide a name for your organization to track in Power BI. A specific name allows you to connect to multiple
different organizations. You can't connect to the same organization multiple times, as it will affect the scheduled
refresh.

Troubleshooting
Xero users must have the following roles to access the Xero template app for Power BI: "Standard + Reports" or
 "Advisor". The template app relies on the user-based permissions to access reporting data through Power BI.
During the load, the tiles on the dashboard are in a generic loading state. They stay that way until the full load
completes. If you receive a notification that your load completed but the tiles are still loading, try refreshing the
dashboard tiles using the ... in the top right of your dashboard.
If your template app fails to refresh, check if you have connected to the same organization more than once in
Power BI. Xero only allows a single active connection to an organization and you may see an error indicating
your credentials are invalid if you connect to the same one more than once.
For issues connecting the Xero template app for Power BI, like error messages or slow load times, first clear the
cache / cookies and restart the browser, then reconnect to Power BI.
For other issues, file a ticket at https://support.powerbi.com if the issue persists.

Next steps
Get started in Power BI
Get data in Power BI
 Connect to Zendesk with Power BI
9/9/2020 • 3 minutes to read • Edit Online

This article walks you through pulling your data from your Zendesk account with a Power BI template app. The
Zendesk app offers a Power BI dashboard and a set of Power BI reports that provide insights about your ticket
volumes and agent performance. The data is refreshed automatically once a day.
After you've installed the template app, you can customize the dashboard and report to highlight the information
you care about most. Then you can distribute it as an app to colleagues in your organization.
Connect to the Zendesk template app or read more about the Zendesk integration with Power BI.
After you've installed the template app, you can change the dashboard and report. Then you can distribute it as an
app to colleagues in your organization.

NOTE
You need a Zendesk Admin account to connect. More details on requirements below.

WARNING
Before Oct 15, 2019, the Zendesk Support Search API allowed for a total of 200,000 results to be received through
pagination of large queries. To align search usage with its intended scope, Zendesk now limits the maximum number of
results returned to 1,000 total results, with a maximum of 100 results per page. However, the current Power BI Zendesk
connector can still create API calls that exceed these new limits, resulting in possibly misleading results.

How to connect
1. Select Apps in the nav pane > select Get apps in the upper-right corner.

2. In AppSource, select the Apps tab, and search for the service you want.
3. Select Zendesk > Get it now .
4. In Install this Power BI App? select Install .
5. In the Apps pane, select the Zendesk tile.

6. In Get star ted with your new app , select Connect .

7. Provide the URL associated with your account. The URL has the form https://company.zendesk .com . See
details on finding these parameters below.
8. When prompted, enter your Zendesk credentials. Select oAuth 2 as the Authentication Mechanism and click
Sign In . Follow the Zendesk authentication flow. (If you're already signed in to Zendesk in your browser, you
may not be prompted for credentials.)

NOTE
This template app requires that you connect with a Zendesk Admin account.

9. Click Allow to allow Power BI to access your Zendesk data.

10. Click Connect to begin the import process.
11. After Power BI imports the data, you see the content list for your Zendesk app: a new dashboard, report, and
dataset.
12. Select the dashboard to start the exploration process.

Modify and distribute your app

You've installed the Zendesk template app. That means you've also created the Zendesk workspace. In the
workspace, you can change the report and dashboard, and then distribute it as an app to colleagues in your
organization.
1. To view all the contents of your new Zendesk workspace, in the nav pane, select Workspaces > Zendesk .

This view is the content list for the workspace. In the upper-right corner, you see Update app . When you're
ready to distribute your app to your colleagues, that's where you'll start.
2. Select Repor ts and Datasets to see the other elements in the workspace.
Read about distributing apps to your colleagues.

System requirements
A Zendesk Administrator account is required to access the Zendesk template app. If you're an agent or an end user
and are interested in viewing your Zendesk data, add a suggestion and review the Zendesk connector in the Power
BI Desktop.

Finding parameters
Your Zendesk URL will be the same as the URL you use to sign into your Zendesk account. If you're not sure of your
Zendesk URL, you can use the Zendesk login help.

Troubleshooting
If you're having issues connecting, check your Zendesk URL and confirm you're using a Zendesk administrator
account.

Next steps
Create the new workspaces in Power BI
Install and use apps in Power BI
COnnect to Power BI apps for external services
Questions? Try asking the Power BI Community
 On-premises data gateway in-depth
9/9/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

We moved the information from this article to several articles across the Power BI and general docs. Follow the
links under each heading to find the relevant content.

How the gateway works

See On-premises data gateway architecture.

List of available data source types

See Manage data sources.

Authentication to on-premises data sources

See Authentication to on-premises data sources.

Authentication to a live Analysis Services data source

See Authentication to a live Analysis Services data source.

Role-based security
See Role-based security.

Row-level security
See Row-level security.

What about Azure Active Directory?

See Azure Active Directory.

How do I tell what my UPN is?

See How do I tell what my UPN is?.

Map user names for Analysis Services data sources

See Map user names for Analysis Services data sources.

Synchronize an on-premises Active Directory with Azure Active

Directory
See Synchronize an on-premises Active Directory with Azure Active Directory.

What to do next?
See the articles on data sources:
Manage data sources Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/Scheduled refresh

Where things can go wrong

See Troubleshoot the on-premises data gateway and Troubleshoot gateways - Power BI.

Sign in account
See Sign in account.

Windows Service account

See Change the on-premises data gateway service account.

Ports
See Ports.

Forcing HTTPS communication with Azure Service Bus

See Force HTTPS communication with Azure Service Bus.

Support for TLS 1.2

See TLS 1.2 for gateway traffic.

How to restart the gateway

See Restart a gateway.

Next steps
What is the on-premises data gateway?
More questions? Try the Power BI Community
 Use personal gateways in Power BI
9/9/2020 • 3 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

The on-premises data gateway (personal mode) is a version of the on-premises data gateway that works only
with Power BI. You can use a personal gateway to install a gateway on your own computer and gain access to on-
premises data.

NOTE
You can have only one personal mode gateway running for each Power BI user. If you install another personal mode
gateway for the same user, even on a different computer, the most recent installation replaces the existing previous
installation.

On-premises data gateway vs. on-premises data gateway (personal

mode)
The following table describes differences between an on-premises data gateway and an on-premises data
gateway (personal mode).

O N - P REM ISES DATA GAT EWAY

O N - P REM ISES DATA GAT EWAY ( P ERSO N A L M O DE)

Cloud services supported Power BI, PowerApps, Azure Logic Power BI

Apps, Power Automate, Azure Analysis
Services, dataflows

Runs As configured by users who have As you for Windows authentication

access to the gateway and as configured by you for other
authentication types

Can install only as computer admin Yes No

Centralized gateway and data source Yes No

management

Import data and schedule refresh Yes Yes

DirectQuery support Yes No

LiveConnect support for Analysis Yes No

Services

Install the on-premises data gateway (personal mode)

To install the on-premises data gateway (personal mode):
1. Download the on-premises data gateway.
2. In the installer, select the on-premises data gateway (personal mode), and then select Next .

The gateway files are installed in "%localappdata%\Microsoft\On-premises data gateway (personal mode). After
the installation finishes successfully and you sign in, you see the following screen.
Use Fast Combine with the personal gateway
Fast Combine on a personal gateway helps you ignore specified privacy levels while executing queries. To enable
Fast Combine to work with the on-premises data gateway (personal mode):
1. Using File Explorer, open the following file:
%localappdata%\Microsoft\On-premises data gateway (personal
mode)\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

2. At the bottom of the file, add the following text:

<setting name="EnableFastCombine" serializeAs="String">

<value>true</value>
</setting>

3. After it finishes, the setting takes effect in approximately one minute. To check that it's working properly,
try an on-demand refresh in the Power BI service to confirm that Fast Combine is working.

Frequently asked questions (FAQ)

Question: Can I run the on-premises data gateway (personal mode) side by side with the on-premises data
gateway (previously known as the Enterprise version of the gateway)?
Answer : Yes, both gateways can run simultaneously.
Question: Can I run the on-premises data gateway (personal mode) as a service?
Answer : No. The on-premises data gateway (personal mode) can run only as an application. If you need to run
the gateway as a service or in admin mode, you need to consider the on-premises data gateway (previously
known as the Enterprise gateway).
Question: How often is the on-premises data gateway (personal mode) updated?
Answer : We plan to update the personal gateway monthly.
Question: Why am I asked to update my credentials?
Answer : Many situations can trigger a request for credentials. The most common is that you've reinstalled the
on-premises data gateway (personal mode) on a different machine than your Power BI - personal gateway. It
could also be an issue in the data source, and Power BI failed to perform a test connection, or a timeout or a
system error occurred. To update your credentials in the Power BI service, select the gear icon and select
Settings > Datasets . Find the dataset in question, and select Data source credentials .
Question: How long will my previous personal gateway be offline during the upgrade?
Answer : Upgrading the personal gateway to the new version takes only few minutes.
Question: I'm using R and Python scripts. Are they supported?
Answer : R and Python scripts are supported for personal mode.

Next steps
Configuring proxy settings for the on-premises data gateway
More questions? Try the Power BI Community.
 Manage data sources
9/9/2020 • 5 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

Power BI supports many on-premises data sources, and each has its own requirements. A gateway can be used for
a single data source or multiple data sources. For this example, we show you how to add SQL Server as a data
source. The steps are similar for other data sources.
Most data sources management operations can be performed by using APIs as well. For more information, see
REST APIs (Gateways).

Add a data source

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways .

2. Select a gateway and then select Add data source . Or, go to Gateways > Add data source .

3. Select the Data Source Type .

4. Enter information for the data source. For this example, it's Ser ver , Database , and other information.

5. For SQL Server, you choose an Authentication Method of Windows or Basic (SQL Authentication). If you
 choose Basic , enter the credentials for your data source.

NOTE
If the selected authentication method is OAuth, any query that runs longer than the OAuth token expiration policy
may fail.

6. Under Advanced settings , you could configure Single Sign-On(SSO) for your data source.

You could either configure Use SSO via Kerberos for DirectQuer y queries or Use SSO via Kerberos for
DirectQuer y And Impor t queries for DirectQuery based Reports and Use SSO via Kerberos for
DirectQuer y And Impor t queries for Refresh based Reports.
If you use the Use SSO via Kerberos for DirectQuer y queries and use this data source for a DirectQuery
based Report, it will use the user that's mapped to the (Azure) Active Directory user that signs in to the Power BI
service. For a Refresh based Report, it will use the credentials that you enter in the Username and Password
fields.
If you use the Use SSO via Kerberos for DirectQuer y And Impor t queries , you do not need to provide any
credentials. If this data source is used for DirectQuery based Report, it will use the user that's mapped to the
(Azure) Active Directory user that signs in to the Power BI service. For a Refresh based Report, it will use the
dataset owner's security context

NOTE
SSO for Import Queries is available only for the list of SSO data sources using Kerberos constrained delegation.

7. Under Advanced settings , optionally configure the privacy level for your data source (doesn't apply to
DirectQuery).
8. Select Add . You see Connection Successful if the process succeeds.

You can now use this data source to include data from SQL Server in your Power BI dashboards and reports.

Remove a data source

You can remove a data source if you no longer use it. Removing a data source breaks any dashboards and reports
that rely on that data source.
To remove a data source, go to the data source and then select Remove .

Use the data source for scheduled refresh or DirectQuery

After you create the data source, it's available to use with either DirectQuery connections or through scheduled
refresh.

NOTE
Server and database names must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source in the gateway is based on your server name and database
name. These names must match. For example, if you supply an IP address for the server name, in Power BI
Desktop, you must use the IP address for the data source in the gateway configuration. If you use
SERVER\INSTANCE in Power BI Desktop, you must use the same in the data source configured for the gateway.
If you're listed in the Users tab of the data source configured in the gateway, and the server and database name
match, you see the gateway as an option to use with scheduled refresh.
 WARNING
If your dataset contains multiple data sources, each data source must be added in the gateway. If one or more data sources
aren't added to the gateway, you won't see the gateway as available for scheduled refresh.

Limitations
OAuth is a supported authentication scheme only for custom connectors with the on-premises data gateway. You
can't add other data sources that require OAuth. If your dataset has a data source that requires OAuth and this data
source isn't a custom connector, you won't be able to use the gateway for scheduled refresh.

Manage users
After you add a data source to a gateway, you give users and email-enabled security groups access to the specific
data source (not the entire gateway). The data source users list controls only who is allowed to publish reports that
include data from the data source. Report owners can create dashboards, content packs, and apps, and then share
those items with other users.
You can also give users and security groups administrative access to the gateway.

NOTE
Users with access to the data source can associate datasets to the data source, and connect, based on the security options
(either the stored credentials or Single Sign-On) selected while creating a data source.

Add users to a data source

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways .
2. Select the data source where you want to add users.
3. Select Users , and enter a user from your organization who you want to grant access to the selected data
source. For example, in the following screen, you add Maggie and Adam.
4. Select Add , and the added member's name shows up in the box.

Remember that you need to add users to each data source that you want to grant access to. Each data source has a
separate list of users. Add users to each data source separately.
Remove users from a data source
On the Users tab for the data source, you can remove users and security groups that use this data source.
Store encrypted credentials in the cloud
When you add a data source to the gateway, you must provide credentials for that data source. All queries to the
data source will run by using these credentials. The credentials are encrypted securely. They use symmetric
encryption so that they can't be decrypted in the cloud before they're stored in the cloud. The credentials are sent
to the machine that runs the gateway, on-premises, where they're decrypted when the data sources are accessed.

List of available data source types

For information about which data sources the on-premises data gateway supports, see Power BI data sources.

Next steps
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/scheduled refresh
Guidance for deploying a data gateway
More questions? Try the Power BI Community.
 Manage your data source - Analysis Services
9/9/2020 • 14 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

After you install the on-premises data gateway, you need to add data sources that can be used with the gateway.
This article looks at how to work with gateways and SQL Server Analysis Services (SSAS) data sources that are
used either for scheduled refresh or for live connections.
To learn more about how to set up a live connection to Analysis Services, watch this video.

NOTE
If you have an Analysis Services data source, you need to install the gateway on a computer joined to the same
forest/domain as your Analysis Services server.

Add a data source

For information about how to add a data source, see Add a data source. Select Analysis Ser vices for Data
Source Type if you're connecting to either a multidimensional or tabular server.

Fill in the information for the data source, which includes Ser ver and Database . The information that you enter
for Username and Password is used by the gateway to connect to the Analysis Services instance.
 NOTE
The Windows account you enter must be a member of the Server Administrator role on the Analysis Services instance
you're connecting to. If this account’s password is set to expire, users could get a connection error if the password isn’t
updated for the data source. To learn more about how credentials are stored, see Store encrypted credentials in the cloud.

After you fill in everything, select Add . You can now use this data source for scheduled refresh or live connections
against an Analysis Services instance that's on-premises. You see Connection Successful if it succeeded.

Advanced settings
Optionally, you can configure the privacy level for your data source. This setting controls how data can be
combined. It's only used for scheduled refresh. The privacy-level setting doesn't apply to live connections. To learn
more about privacy levels for your data source, see Privacy levels (Power Query).
User names with Analysis Services
https://www.youtube.com/embed/Qb5EEjkHoLg
Each time a user interacts with a report connected to Analysis Services, the effective user name is passed to the
gateway and then passed on to your on-premises Analysis Services server. The email address that you use to sign
in to Power BI is passed to Analysis Services as the effective user. It's passed in the connection property
EffectiveUserName.
The email address must match a defined user principal name (UPN) within the local Active Directory domain. The
UPN is a property of an Active Directory account. The Windows account must be present in an Analysis Services
role. If a match can't be found in Active Directory, the sign-in isn't successful. To learn more about Active Directory
and user naming, see User naming attributes.
You can also map your Power BI sign-in name with a local directory UPN.

Map user names for Analysis Services data sources

https://www.youtube.com/embed/eATPS-c7YRU
Power BI allows for mapping user names for Analysis Services data sources. You can configure rules to map a user
name signed in with Power BI to a name that's passed for EffectiveUserName on the Analysis Services connection.
The map user names feature is a great way to work around when your user name in Azure Active Directory (Azure
AD) doesn't match a UPN in your local Active Directory instance. For example, if your email address is
[email protected], you map it to [email protected] and that value is passed to the gateway.
You can map user names for Analysis Services in two different ways:
Manual user remapping
On-premises Active Directory property lookup to remap Azure AD UPNs to Active Directory users (Active
Directory lookup mapping)
It's possible to perform manual mapping by using the second approach, but doing so is time consuming and
difficult to maintain. It's especially difficult when pattern matching doesn't suffice. Examples are when domain
names are different between Azure AD and on-premises Active Directory or when user account names are
different between Azure AD and Active Directory. That's why manual mapping with the second approach isn't
recommended.
We describe these two approaches, in order, in the following two sections.
Manual user name remapping
For Analysis Services data sources, you can configure custom UPN rules. Custom rules help you if your Power BI
service sign-in names don't match your local directory UPN. For example, if you sign in to Power BI with
[email protected] but your local directory UPN is [email protected], you can configure a mapping rule to have
[email protected] passed to Analysis Services.
To get to the UPN mapping screen, follow these steps.
1. Go to the gear icon, and select Manage Gateways .
2. Expand the gateway that contains the Analysis Services data source. Or, if you haven't created the Analysis
Services data source, you can do that at this point.
3. Select the data source, and then select the Users tab.
4. Select Map user names .

You see options to add rules and test for a given user.

NOTE
You might change a user that you didn't intend to change. For example, if Replace (original value) is contoso.com and
With (New name) is @contoso.local, all users with a sign-in that contains @contoso.com are then replaced with
@contoso.local. Also, if Replace (Original name) is [email protected] and With (New name) is [email protected], a
user with the sign-in of [email protected] is sent as [email protected].

Active Directory lookup mapping

To perform on-premises Active Directory property lookup to remap Azure AD UPNs to Active Directory users,
follow the steps in this section. To begin with, let's review how this works.
In the Power BI service, the following occurs:
For each query by a Power BI Azure AD user to an on-premises SSAS server, a UPN string is passed along, such
as [email protected].

NOTE
Any manual UPN user mappings defined in the Power BI data source configuration are still applied before the user name
string is sent to the on-premises data gateway.

In the on-premises data gateway with configurable custom user mapping, follow these steps.
1. Find Active Directory to search. You can use automatic or configurable.
2. Look up the attribute of the Active Directory person, such as Email, from the Power BI service. The attribute is
based on an incoming UPN string like [email protected].
3. If the Active Directory lookup fails, it attempts to use the passed-along UPN as EffectiveUser to SSAS.
4. If the Active Directory lookup succeeds, it retrieves UserPrincipalName of that Active Directory person.
5. It passes the UserPrincipalName email as EffectiveUser to SSAS, such as [email protected].
To configure your gateway to perform the Active Directory lookup:
1. Download and install the latest gateway.
2. In the gateway, change the on-premises data gateway service to run with a domain account instead of a
local service account. Otherwise, the Active Directory lookup won’t work properly at runtime. Go to the on-
premises data gateway app on your machine, and then go to Ser vice settings > Change ser vice
account . Make sure you have the recovery key for this gateway because you need to restore it on the
same machine unless you want to create a new gateway instead. Restart the gateway service for the
change to take effect.
3. Go to the gateway’s installation folder, C:\Program Files\On-premises data gateway, as an administrator to
ensure that you have write permissions. Open the
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file.
4. Edit the following two configuration values according to your Active Directory attribute configurations for
your Active Directory users. The following configuration values are examples. Specify the values based on
your Active Directory configuration. These configurations are case sensitive, so make sure they match the
values in Active Directory.

If no value is provided for the ADServerPath configuration, the gateway uses the default global catalog. You
can also specify multiple values for the ADServerPath. Each value must be separated by a semicolon, as
shown in the following example:

<setting name="ADServerPath" serializeAs="String">

<value> >GC://serverpath1; GC://serverpath2;GC://serverpath3</value>
</setting>

The gateway parses the values for ADServerPath from left to right until it finds a match. If no match is
 found, the original UPN is used. Make sure the account that runs the gateway service (PBIEgwService) has
query permissions to all Active Directory servers that you specify in ADServerPath.
The gateway supports two types of ADServerPath, as shown in the following examples:
WinNT

<value="WinNT://usa.domain.corp.contoso.com,computer"/>

GC

<value> GC://USA.domain.com </value>

5. Restart the on-premises data gateway service for the configuration change to take effect.
Work with mapping rules
To create a mapping rule, enter a value for Original name and New name and then select Add .

F IEL D DESC RIP T IO N

Replace (Original name) The email address that you used to sign in to Power BI.

With (New name) The value you want to replace it with. The result of the
replacement is what is passed to the EffectiveUserName
property for the Analysis Services connection.

When you select an item in the list, you can choose to reorder it by using the chevron icons. Or, you can delete the
entry.
Use a wildcard
You can use a wildcard (*) for your Replace (Original name) string. It can only be used on its own and not with
any other string part. Use a wildcard if you want to take all users and pass a single value to the data source. This
approach is useful when you want all users in your organization to use the same user in your local environment.
Test a mapping rule
To validate what an original name is replaced with, enter a value for Original name . Select Test rule .

NOTE
Rules that are saved take a few minutes before the service starts to use them. The rule works immediately in the browser.

Limitations for mapping rules

Mapping is for the specific data source that's being configured. It's not a global setting. If you have multiple
Analysis Services data sources, you have to map the users for each data source.

Authentication to a live Analysis Services data source

Each time a user interacts with Analysis Services, the effective user name is passed to the gateway and then on to
your on-premises Analysis Services server. The UPN, which is typically the email address you use to sign in to the
cloud, is passed to Analysis Services as the effective user. The UPN is passed in the connection property
EffectiveUserName.
This email address should match a defined UPN within the local Active Directory domain. The UPN is a property
of an Active Directory account. That Windows account must be present in an Analysis Services role to have access
to the server. If no match is found in Active Directory, the sign-in won't be successful.
Analysis Services can also provide filtering based on this account. The filtering can occur with either role-based
security or row-level security.

Role-based security
Models provide security based on user roles. Roles are defined for a particular model project during authoring in
SQL Server Data Tools – Business Intelligence or, after a model is deployed, by using SQL Server Management
Studio. Roles contain members by Windows user name or by Windows group. Roles define the permissions a user
has to query or perform actions on the model. Most users belong to a role with read permissions. Other roles are
meant for administrators with permissions to process items, manage database functions, and manage other roles.

Row-level security
Row-level security is specific to Analysis Services row-level security. Models can provide dynamic, row-level
security. Unlike having at least one role that users belong to, dynamic security isn't required for any tabular model.
At a high level, dynamic security defines a user’s read access to data right down to a particular row in a particular
table. Similar to roles, dynamic row-level security relies on a user’s Windows user name.
A user’s ability to query and view model data is determined by:
The roles that their Windows user account belong to as a member.
Dynamic row-level security, if it's configured.
Implementing role and dynamic row-level security in models are beyond the scope of this article. To learn more,
see Roles (SSAS tabular) and Security roles (Analysis Services - Multidimensional data) on MSDN. For the most in-
depth understanding of tabular model security, download and read the Securing the tabular BI semantic model
whitepaper.

What about Azure AD?

Microsoft cloud services use Azure AD to take care of authenticating users. Azure AD is the tenant that contains
user names and security groups. Typically, the email address a user signs in with is the same as the UPN of the
account.

What is the role of my local Active Directory instance?

For Analysis Services to determine if a user connecting to it belongs to a role with permissions to read data, the
server needs to convert the effective user name passed from Azure AD to the gateway and on to the Analysis
Services server. The Analysis Services server passes the effective user name to a Windows Active Directory
domain controller (DC). The Active Directory DC then validates that the effective user name is a valid UPN on a
local account. It returns that user’s Windows user name back to the Analysis Services server.
EffectiveUserName can't be used on a non-domain-joined Analysis Services server. The Analysis Services server
must be joined to a domain to avoid any sign-in errors.

How do I tell what my UPN is?

You might not know what your UPN is, and you might not be a domain administrator. You can use the following
command from your workstation to find out the UPN for your account.

whoami /upn

The result looks similar to an email address, but it's the UPN that's on your domain account. If you use an Analysis
Services data source for live connections, and if this UPN doesn't match the email address you use to sign in to
Power BI, you might want to look at how to map user names.

Synchronize an on-premises Active Directory with Azure AD

If you plan to use Analysis Services live connections, your local Active Directory accounts must match Azure AD.
The UPN must match between the accounts.
The cloud services only know about accounts within Azure AD. It doesn’t matter if you added an account in your
local Active Directory instance. If the account doesn’t exist in Azure AD, it can't be used. There are different ways
that you can match your local Active Directory accounts with Azure AD:
You can add accounts manually to Azure AD.
You can create an account on the Azure portal, or within the Microsoft 365 admin center, and the account
name matches the UPN of the local Active Directory account.
You can use the Azure AD Connect tool to synchronize local accounts to your Azure AD tenant.
 The Azure AD Connect tool provides options for directory synchronization and setting up authentication.
Options include password hash sync, pass-through authentication, and federation. If you're not a tenant
admin or a local domain administrator, contact your IT admin to help with configuration.
Using Azure AD Connect ensures that the UPN matches between Azure AD and your local Active Directory
instance.

NOTE
Synchronizing accounts with the Azure AD Connect tool creates new accounts within your Azure AD tenant.

Use the data source

After you create the data source, it's available to use with either live connections or through scheduled refresh.

NOTE
The server and database name must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source within the gateway is based on your server name and database
name. These names must match. For example, if you supply an IP address for the server name within Power BI
Desktop, you must use the IP address for the data source within the gateway configuration. If you use
SERVER\INSTANCE in Power BI Desktop, you also must use it within the data source configured for the gateway.
This requirement is the case for both live connections and scheduled refresh.
Use the data source with live connections
Make sure that the server and database name matches between Power BI Desktop and the configured data source
for the gateway. You also need to make sure your user is listed in the Users tab of the data source to publish live
connection datasets. The selection for live connections occurs within Power BI Desktop when you first import data.
After you publish, either from Power BI Desktop or Get Data , your reports should start to work. It might take
several minutes after you create the data source within the gateway for the connection to be usable.
Use the data source with scheduled refresh
If you're listed in the Users tab of the data source configured within the gateway and the server and database
name match, you see the gateway as an option to use with scheduled refresh.

Limitations of Analysis Services live connections

You can use a live connection against tabular or multidimensional instances.
 SERVER VERSIO N REQ UIRED SK U

2012 SP1 CU4 or later Business Intelligence and Enterprise SKU

2014 Business Intelligence and Enterprise SKU

2016 Standard SKU or higher

Cell level formatting and translation features aren't supported.

Actions and named sets aren't exposed to Power BI. You can still connect to multidimensional cubes that also
contain actions or named sets and create visuals and reports.

Next steps
Troubleshooting the on-premises data gateway
Troubleshoot gateways - Power BI
More questions? Try the Power BI Community.
 Manage your data source - SAP HANA
9/9/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

After you install the on-premises data gateway, you need to add data sources that can be used with the gateway.
This article looks at how to work with gateways and SAP HANA data sources that are used either for scheduled
refresh or for DirectQuery.

Add a data source

For more information about how to add a data source, see Add a data source. Under Data Source Type , select
SAP HANA .

After you select the SAP HANA data source type, fill in the Ser ver , Username , and Password information for the
data source.

NOTE
All queries to the data source will run using these credentials. To learn more about how credentials are stored, see Store
encrypted credentials in the cloud.
After you fill in everything, select Add . You can now use this data source for scheduled refresh or DirectQuery
against an SAP HANA server that is on-premises. You see Connection Successful if it succeeded.

Advanced settings
Optionally, you can configure the privacy level for your data source. This setting controls how data can be
combined. It's only used for scheduled refresh. The privacy-level setting doesn't apply to DirectQuery. To learn
more about privacy levels for your data source, see Privacy levels (Power Query).

Use the data source

After you create the data source, it's available to use with either DirectQuery connections or through scheduled
refresh.

NOTE
The server and database names must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source within the gateway is based on your server name and database
name. These names must match. For example, if you supply an IP address for the server name within Power BI
Desktop, you must use the IP address for the data source within the gateway configuration. If you use
SERVER\INSTANCE in Power BI Desktop, you also must use it within the data source configured for the gateway.
This requirement is the case for both DirectQuery and scheduled refresh.
Use the data source with DirectQuery connections
Make sure that the server and database names match between Power BI Desktop and the configured data source
for the gateway. You also need to make sure your user is listed in the Users tab of the data source to publish
DirectQuery datasets. The selection for DirectQuery occurs within Power BI Desktop when you first import data.
For more information about how to use DirectQuery, see Use DirectQuery in Power BI Desktop.
After you publish, either from Power BI Desktop or Get Data , your reports should start to work. It might take
several minutes after you create the data source within the gateway for the connection to be usable.
Use the data source with scheduled refresh
If you're listed in the Users tab of the data source configured within the gateway and the server name and
database name match, you see the gateway as an option to use with scheduled refresh.

Next steps
Troubleshooting the on-premises data gateway
Troubleshoot gateways - Power BI
More questions? Try asking the Power BI Community.
 Manage your data source - SQL Server
9/9/2020 • 3 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

After you install the on-premises data gateway, you can add data sources that can be used with the gateway. This
article looks at how to work with gateways and SQL Server data sources that are used either for scheduled refresh
or for DirectQuery.

Add a data source

For more information about how to add a data source, see Add a data source. Under Data Source Type , select
SQL Ser ver .

NOTE
When you use DirectQuery, the gateway supports only SQL Ser ver 2012 SP1 and subsequent versions.

Then fill in the information for the data source, which includes Ser ver and Database .
Under Authentication Method , choose either Windows or Basic . Choose Basic if you plan to use SQL
authentication instead of Windows authentication. Then enter the credentials to be used for this data source.
 NOTE
All queries to the data source will run using these credentials, unless Kerberos single sign-on (SSO) is configured and enabled
for the data source. With SSO, import datasets use the stored credentials, but DirectQuery datasets use the current Power BI
user to execute the queries using SSO. To learn more about how credentials are stored, see Store encrypted credentials in the
cloud. Or, see the article that describes how to use Kerberos for single sign-on (SSO) from Power BI to on-premises data
sources.

After you fill in everything, select Add . You can now use this data source for scheduled refresh or DirectQuery
against a SQL Server that's on-premises. You see Connection Successful if it succeeded.

Advanced settings
Optionally, you can configure the privacy level for your data source. This setting controls how data can be
combined. It's only used for scheduled refresh. The privacy-level setting doesn't apply to DirectQuery. To learn
more about privacy levels for your data source, see Privacy levels (Power Query).

Use the data source

After you create the data source, it's available to use with either DirectQuery connections or through scheduled
refresh.

NOTE
The server and database names must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source within the gateway is based on your server name and database
name. These names must match. For example, if you supply an IP address for the server name within Power BI
Desktop, you must use the IP address for the data source within the gateway configuration. If you use
SERVER\INSTANCE in Power BI Desktop, you must use it within the data source configured for the gateway.
This requirement is the case for both DirectQuery and scheduled refresh.
Use the data source with DirectQuery connections
Make sure that the server and database names match between Power BI Desktop and the configured data source
for the gateway. You also need to make sure your user is listed in the Users tab of the data source to publish
DirectQuery datasets. The selection for DirectQuery occurs within Power BI Desktop when you first import data.
For more information about how to use DirectQuery, see Use DirectQuery in Power BI Desktop.
After you publish, either from Power BI Desktop or Get Data , your reports should start to work. It might take
several minutes after you create the data source within the gateway for the connection to be usable.
Use the data source with scheduled refresh
If you're listed in the Users tab of the data source configured within the gateway and the server name and
database name match, you see the gateway as an option to use with scheduled refresh.
Next steps
Connect to on-premises data in SQL Server
Troubleshooting the on-premises data gateway
Troubleshoot gateways - Power BI
Use Kerberos for single sign-on (SSO) from Power BI to on-premises data sources
More questions? Try asking the Power BI Community.
 Manage your data source - Oracle
9/9/2020 • 5 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

After you install the on-premises data gateway, you need to add data sources that can be used with the gateway.
This article looks at how to work with gateways and Oracle data sources either for scheduled refresh or for
DirectQuery.

Connect to an Oracle database

To connect to an Oracle database with the on-premises data gateway, the correct Oracle client software must be
installed on the computer running the gateway. The Oracle client software you use depends on the Oracle server
version, but will always match the 64-bit gateway.
Supported Oracle versions:
Oracle Server 9 and later
Oracle Data Access Client (ODAC) software 11.2 and later

Install the Oracle client

download and install the 64-bit Oracle client.

NOTE
Choose a version of Oracle Data Access Client (ODAC) which is compatible with your Oracle Server. For instance, ODAC 12.x
does not always support Oracle Server version 9. Choose the Windows installer of the Oracle Client. During the setup of the
Oracle client, make sure you enable Configure ODP.NET and/or Oracle Providers for ASP.NET at machine-wide level by
selecting the corresponding checkbox during the setup wizard. Some versions of the Oracle client wizard selects the
checkbox by default, others do not. Make sure that checkbox is selected so that Power BI can connect to your Oracle
database.

After the client is installed and ODAC is configured properly, we recommend using PowerBI Desktop or other test
client to verify correct installation and configuration on the Gateway.

Add a data source

For more information about how to add a data source, see Add a data source. Under Data Source Type , select
Oracle .
After you select the Oracle data source type, fill in the information for the data source, which includes Ser ver and
Database .
Under Authentication Method , you can choose either Windows or Basic . Choose Basic if you plan to use an
account that's created within Oracle instead of Windows authentication. Then enter the credentials to be used for
this data source.

NOTE
All queries to the data source will run using these credentials. To learn more about how credentials are stored, see Store
encrypted credentials in the cloud.
After you fill in everything, select Add . You can now use this data source for scheduled refresh or DirectQuery
against an Oracle server that's on-premises. You see Connection Successful if it succeeded.

Advanced settings
Optionally, you can configure the privacy level for your data source. This setting controls how data can be
combined. It's only used for scheduled refresh. The privacy-level setting doesn't apply to DirectQuery. To learn
more about privacy levels for your data source, see Privacy levels (Power Query).
Use the data source
After you create the data source, it's available to use with either DirectQuery connections or through scheduled
refresh.

WARNING
The server and database names must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source within the gateway is based on your server name and database
name. These names must match. For example, if you supply an IP address for the server name within Power BI
Desktop, you must use the IP address for the data source within the gateway configuration. This name also has to
match an alias defined within the tnsnames.ora file. For more information about the tnsnames.ora file, see Install
the Oracle client.
This requirement is the case for both DirectQuery and scheduled refresh.
Use the data source with DirectQuery connections
Make sure that the server and database names match between Power BI Desktop and the configured data source
for the gateway. You also need to make sure your user is listed in the Users tab of the data source to publish
DirectQuery datasets. The selection for DirectQuery occurs within Power BI Desktop when you first import data.
For more information about how to use DirectQuery, see Use DirectQuery in Power BI Desktop.
After you publish, either from Power BI Desktop or Get Data , your reports should start to work. It might take
several minutes after you create the data source within the gateway for the connection to be usable.
Use the data source with scheduled refresh
If you're listed in the Users tab of the data source configured within the gateway and the server name and
database name match, you see the gateway as an option to use with scheduled refresh.
Troubleshooting
You might encounter any of several errors from Oracle when the naming syntax is either incorrect or not
configured properly:
ORA-12154: TNS:could not resolve the connect identifier specified.
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.
ORA-12541: TNS:no listener.
ORA-12170: TNS:connect timeout occurred.
ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA.
These errors might occur if the Oracle client either isn't installed or isn't configured properly. If it's installed, verify
that the tnsnames.ora file is properly configured and you're using the proper net_service_name. You also need to
make sure that the net_service_name is the same between the machine that uses Power BI Desktop and the
machine that runs the gateway. For more information, see Install the Oracle client.
You might also encounter a compatibility issue between the Oracle server version and the Oracle Data Access
Client version. Typically, you want these versions to match, as some combinations are incompatible. For instance,
ODAC 12.x does not support Oracle Server version 9.
For diagnosing connectivity issues between the data source server and the Gateway machine, we recommend
installing a client(such as PowerBI Desktop or Oracle ODBC Test) on the gateway machine. You can use the client to
check connectivity to the data source server.
For additional troubleshooting information that relates to the gateway, see Troubleshooting the on-premises data
gateway.

Next steps
Troubleshoot gateways - Power BI
Power BI Premium
More questions? Try asking the Power BI Community.
 Manage your data source - Import/scheduled refresh
9/9/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

After you install the on-premises data gateway, you need to add data sources that can be used with the gateway.
This article looks at how to work with gateways and data sources that are used for scheduled refresh as opposed
to DirectQuery or live connections.

Add a data source

For more information about how to add a data source, see Add a data source. Select a data source type.
All of the data source types listed can be used for scheduled refresh with the on-premises data gateway. Analysis
Services, SQL Server, and SAP HANA can be used for either scheduled refresh or DirectQuery/live connections.

Then fill in the information for the data source, which includes the source information and credentials that are
used to access the data source.

NOTE
All queries to the data source run by using these credentials. To learn more about how credentials are stored, see Store
encrypted credentials in the cloud.
For a list of data source types that can be used with scheduled refresh, see List of available data source types.
After you fill in everything, select Add . You can now use this data source for scheduled refresh with your on-
premises data. You see Connection Successful if it succeeded.

Advanced settings
Optionally, you can configure the privacy level for your data source. This setting controls how data can be
combined. It's only used for scheduled refresh. To learn more about privacy levels for your data source, see
Privacy levels (Power Query).
Use the data source for scheduled refresh
After you create the data source, it's available to use with either DirectQuery connections or through scheduled
refresh.

NOTE
The server and database names must match between Power BI Desktop and the data source within the on-premises data
gateway.

The link between your dataset and the data source within the gateway is based on your server name and
database name. These names must match. For example, if you supply an IP address for the server name within
Power BI Desktop, you must use the IP address for the data source within the gateway configuration. If you use
SERVER\INSTANCE in Power BI Desktop, you also must use it within the data source configured for the gateway.
If you're listed in the Users tab of the data source configured within the gateway and the server name and
database name match, you see the gateway as an option to use with scheduled refresh.

WARNING
If your dataset contains multiple data sources, each data source must be added within the gateway. If one or more data
sources aren't added to the gateway, you won't see the gateway as available for scheduled refresh.

Limitations
OAuth isn't a supported authentication scheme with the on-premises data gateway. You can't add data sources
that require OAuth. If your dataset has a data source that requires OAuth, you can't use the gateway for scheduled
refresh.
Next steps
Troubleshooting the on-premises data gateway
Troubleshoot gateways - Power BI
More questions? Try the Power BI Community.
 Merge or append on-premises and cloud data
sources
9/9/2020 • 2 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

You can use the on-premises data gateway to merge or append on-premises and cloud data sources in the same
query. This solution is helpful when you want to combine data from multiple sources without having to use
separate queries.

NOTE
This article applies only to datasets that have cloud and on-premises data sources merged or appended in a single query. For
datasets that include separate queries--one that connects to an on-premises data source and the other to a cloud data
source--the gateway doesn't execute the query for the cloud data source.

Prerequisites
A gateway installed on a local computer.
A Power BI Desktop file with queries that combine on-premises and cloud data sources.

NOTE
To access any cloud data sources, you must ensure that the gateway has access to those data sources.

1. In the upper-right corner of the Power BI service, select the gear icon > Manage gateways .

2. Select the gateway you want to configure.

3. Under Gateway Cluster Settings , select Allow user's cloud data sources to refresh through this
gateway cluster > Apply .

4. Under this gateway cluster, add any on-premises data sources used in your queries. You don't need to add
the cloud data sources here.
5. Upload to the Power BI service your Power BI Desktop file with the queries that combine on-premises and
cloud data sources.
6. On the Dataset settings page for the new dataset:
For the on-premises source, select the gateway associated with this data source.
Under Data source credentials , edit the cloud data source credentials, as necessary.
Make sure privacy levels for both cloud and on-premises data sources are set appropriately to ensure the
joins are handled securely.
7. With the cloud credentials set, you can now refresh the dataset by using the Refresh now option. Or, you
can schedule it to refresh periodically.

Next steps
To learn more about data refresh for gateways, see Use the data source for scheduled refresh.
 Overview of single sign-on (SSO) for gateways in
Power BI
9/9/2020 • 2 minutes to read • Edit Online

You can get seamless single sign-on connectivity, enabling Power BI reports and dashboards to update in real time
from on-premises data, by configuring your on-premises data gateway. You have the option of configuring your
gateway with either Kerberos constrained delegation or Security Assertion Markup Language (SAML). The on-
premises data gateway supports SSO by using DirectQuery or for Refresh, which connects to on-premises data
sources.
Power BI supports the following data sources:
SQL Server (Kerberos)
SAP HANA (Kerberos and SAML)
SAP BW Application Server (Kerberos)
SAP BW Message Server (Kerberos)
Oracle (Kerberos)
Teradata (Kerberos)
Spark (Kerberos)
Impala (Kerberos)
We don't currently support SSO for M-extensions.
When a user interacts with a DirectQuery report in the Power BI Service, each cross-filter, slice, sort, and report
editing operation can result in queries that execute live against the underlying on-premises data source. When you
configure SSO for the data source, queries execute under the identity of the user that interacts with Power BI (that
is, through the web experience or Power BI mobile apps). Therefore, each user sees precisely the data for which
they have permissions in the underlying data source.
You can also configure a report which is set up for refresh in the Power BI Service to use SSO. When you configure
SSO for this data source, queries execute under the identity of the dataset owner within Power BI. Therefore, the
refresh happens based on the dataset owner's permissions on the underlying data source. Refresh using SSO is
currently enabled only for data sources using Kerberos constrained delegation

Query steps when running SSO

A query that runs with SSO consists of three steps, as shown in the following diagram.
Here are additional details about each step:
1. For each query, the Power BI service includes the user principal name (UPN), which is the fully qualified
username of the user currently signed in to the Power BI service, when it sends a query request to the
configured gateway.
2. The gateway must map the Azure Active Directory UPN to a local Active Directory identity:
a. If Azure AD DirSync (also known as Azure AD Connect) is configured, then the mapping works
automatically in the gateway.
b. Otherwise, the gateway can look up and map the Azure AD UPN to a local AD user by performing a
lookup against the local Active Directory domain.
3. The gateway service process impersonates the mapped local user, opens the connection to the underlying
database, and then sends the query. You don't need to install the gateway on the same machine as the
database.

Next steps
Now that you understand the basics of enabling SSO through the gateway, read more detailed information about
Kerberos and SAML:
Single sign-on (SSO) - Kerberos
Single sign-on (SSO) - SAML
 Configure Kerberos-based SSO from Power BI
service to on-premises data sources
9/9/2020 • 13 minutes to read • Edit Online

Enabling SSO makes it easy for Power BI reports and dashboards to refresh data from on-premises sources
while respecting user-level permissions configured on those sources. Use Kerberos constrained delegation to
enable seamless SSO connectivity.

Prerequisites
Several items must be configured for Kerberos constrained delegation to work properly, including Service
Principal Names (SPN) and delegation settings on service accounts.
Install and configure the Microsoft on-premises data gateway
The on-premises data gateway supports an in-place upgrade, and settings takeover of existing gateways.
Run the gateway Windows service as a domain account
In a standard installation, the gateway runs as the machine-local service account, NT Ser vice\PBIEgwSer vice .

To enable Kerberos constrained delegation, the gateway must run as a domain account, unless your Azure Active
Directory (Azure AD) instance is already synchronized with your local Active Directory instance (by using Azure
AD DirSync/Connect). To switch to a domain account, see change the gateway service account.

NOTE
If Azure AD Connect is configured and user accounts are synchronized, the gateway service doesn't need to perform local
Azure AD lookups at runtime. Instead, you can simply use the local service SID for the gateway service to complete all
required configuration in Azure AD. The Kerberos constrained delegation configuration steps outlined in this article are the
same as the configuration steps required in the Azure AD context. They are applied to the gateway's computer object (as
identified by the local service SID) in Azure AD instead of the domain account.

Obtain domain admin rights to configure SPNs (SetSPN) and Kerberos

constrained delegation settings
To configure SPNs and Kerberos delegation settings, a domain administrator should avoid granting rights to
someone that doesn't have domain admin rights. In the following section, we cover the recommended
configuration steps in more detail.

Configure Kerberos constrained delegation for the gateway and data

source
If necessary, configure an SPN for the gateway service domain account as a domain administrator and configure
delegation settings on the gateway service domain account.
Configure an SPN for the gateway service account
First, determine whether an SPN was already created for the domain account used as the gateway service
account:
1. As a domain administrator, launch the Active Director y Users and Computers Microsoft Management
Console (MMC) snap-in.
2. In the left pane, right-click the domain name, select Find , and then enter the account name of the gateway
service account.
3. In the search result, right-click the gateway service account and select Proper ties .
4. If the Delegation tab is visible on the Proper ties dialog, then an SPN was already created and you can
skip to Decide on the type of Kerberos constrained delegation to use.
5. If there isn't a Delegation tab on the Proper ties dialog box, you can manually create an SPN on the
account to enable it. Use the setspn tool that comes with Windows (you need domain admin rights to
create the SPN).
For example, suppose the gateway service account is Contoso\GatewaySvc and the gateway service is
running on the machine named MyGatewayMachine . To set the SPN for the gateway service account,
run the following command:
setspn -a gateway/MyGatewayMachine Contoso\GatewaySvc

You can also set the SPN by using the Active Director y Users and Computers MMC snap-in.
Add gateway service account to Windows Authorization and Access Group if required
In certain scenarios the gateway service account must be added to the Windows Authorization and Access
Group. These scenarios include security hardening of the Active Directory environment, and when the gateway
service account and the user accounts that the gateway will impersonate are in separate domains or forests. You
can also add the gateway service account to Windows Authorization and Access Group in situations where the
domain / forest has not been hardened, but it isn't required.
For more information, see Windows Authorization and Access Group.
To complete this configuration step, for each domain that contains Active Directory users you want the gateway
service account to be able to impersonate:
1. Sign in to a computer in the domain, and launch the Active Directory Users and Computers MMC snap-in.
2. Locate the group Windows Authorization and Access Group , which is typically found in the Builtin
container.
3. Double click on the group, and click on the Members tab.
4. Click Add , and change the domain location to the domain that the gateway service account resides in.
5. Type in the gateway service account name and click Check Names to verify that the gateway service account
is accessible.
6. Click OK .
7. Click Apply .
8. Restart the gateway service.
Decide on the type of Kerberos constrained delegation to use
You can configure delegation settings for either standard Kerberos constrained delegation or resource-based
Kerberos constrained delegation. Use resource-based delegation (requires Windows Server 2012 or later) if your
data source belongs to a different domain than your gateway. For more information on the differences between
the two approaches to delegation, see Kerberos constrained delegation overview.
Depending on which approach you want to use, proceed to one of the following sections. Don't complete both
sections:
 Configure the gateway service account for standard Kerberos constrained delegation
Configure the gateway service account for resource-based Kerberos constrained delegation.

Configure the gateway service account for standard Kerberos

constrained delegation
NOTE
Complete the steps in this section if you want to enable standard Kerberos constrained delegation. Otherwise, if you want
to enable resource-based Kerberos constrained delegation, complete the steps in Configure the gateway service account
for resource-based Kerberos constrained delegation.

We'll now set the delegation settings for the gateway service account. There are multiple tools you can use to
perform these steps. Here, we'll use the Active Director y Users and Computers MMC snap-in to administer
and publish information in the directory. It's available on domain controllers by default; on other machines, you
can enable it through Windows feature configuration.
We need to configure Kerberos constrained delegation with protocol transiting. With constrained delegation, you
must be explicit about which services you allow the gateway to present delegated credentials to. For example,
only SQL Server or your SAP HANA server accepts delegation calls from the gateway service account.
This section assumes you have already configured SPNs for your underlying data sources (such as SQL Server,
SAP HANA, SAP BW, Teradata, or Spark). To learn how to configure those data source server SPNs, refer to the
technical documentation for the respective database server and see the section What SPN does your app
require? in the My Kerberos Checklist blog post.
In the following steps, we assume an on-premises environment with two machines in the same domain: a
gateway machine and a database server running SQL Server that has already been configured for Kerberos-
based SSO. The steps can be adopted for one of the other supported data sources, so long as the data source has
already been configured for Kerberos-based single sign-on. For this example, we'll use the following settings:
Active Directory Domain (Netbios): Contoso
Gateway machine name: MyGatewayMachine
Gateway service account: Contoso\GatewaySvc
SQL Server data source machine name: TestSQLSer ver
SQL Server data source service account: Contoso\SQLSer vice
Here's how to configure the delegation settings:
1. With domain administrator rights, open the Active Director y Users and Computers MMC snap-in.
2. Right-click the gateway service account (Contoso\GatewaySvc ), and select Proper ties .
3. Select the Delegation tab.
4. Select Trust this computer for delegation to specified ser vices only > Use any authentication
protocol .
5. Under Ser vices to which this account can present delegated credentials , select Add .
6. In the new dialog box, select Users or Computers .
7. Enter the service account for the data source, and then select OK .
For example, a SQL Server data source can have a service account like Contoso\SQLService. An
appropriate SPN for the data source should have already been set on this account.
 8. Select the SPN that you created for the database server.
In our example, the SPN begins with MSSQLSvc. If you added both the FQDN and the NetBIOS SPN for
your database service, select both. You might see only one.
9. Select OK .
You should now see the SPN in the list of services to which the gateway service account can present
delegated credentials.

10. To continue the setup process, proceed to Grant the gateway service account local policy rights on the
gateway machine.

Configure the gateway service account for resource-based Kerberos

constrained delegation
 NOTE
Complete the steps in this section if you want to enable resource-based Kerberos constrained delegation. Otherwise, if
you want to enable standard Kerberos constrained delegation, complete the steps in Configure the gateway service
account for standard Kerberos constrained delegation.

You use resource-based Kerberos constrained delegation to enable single sign-on connectivity for Windows
Server 2012 and later versions. This type of delegation permits front-end and back-end services to be in different
domains. For it to work, the back-end service domain needs to trust the front-end service domain.
In the following steps, we assume an on-premises environment with two machines in different domains: a
gateway machine and a database server running SQL Server that has already been configured for Kerberos-
based SSO. These steps can be adopted for one of the other supported data sources, so long as the data source
has already been configured for Kerberos-based single sign-on. For this example, we'll use the following settings:
Active Directory frontend Domain (Netbios): ContosoFrontEnd
Active Directory backend Domain (Netbios): ContosoBackEnd
Gateway machine name: MyGatewayMachine
Gateway service account: ContosoFrontEnd\GatewaySvc
SQL Server data source machine name: TestSQLSer ver
SQL Server data source service account: ContosoBackEnd\SQLSer vice
Complete the following configuration steps:
1. Use the Active Director y Users and Computers MMC snap-in on the domain controller for the
ContosoFrontEnd domain and verify no delegation settings are applied for the gateway service account.
2. Use Active Director y Users and Computers on the domain controller for the ContosoBackEnd
domain and verify no delegation settings are applied for the back-end service account.
3. In the Attribute Editor tab of the account properties, verify that the msDS-
AllowedToActOnBehalfOfOtherIdentity attribute isn't set.
4. In Active Director y Users and Computers , create a group on the domain controller for the
ContosoBackEnd domain. Add the GatewaySvc gateway service account to the ResourceDelGroup
group.
5. Open a command prompt and run the following commands in the domain controller for the
ContosoBackEnd domain to update the msDS-AllowedToActOnBehalfOfOtherIdentity attribute of
the back-end service account:

$c = Get-ADGroup ResourceDelGroup
Set-ADUser SQLService -PrincipalsAllowedToDelegateToAccount $c

6. In Active Director y Users and Computers , verify that the update is reflected in the Attribute Editor
tab in the properties for the back-end service account.

Grant the gateway service account local policy rights on the gateway
machine
Finally, on the machine running the gateway service (MyGatewayMachine in our example), grant the gateway
service account the local policies Impersonate a client after authentication and Act as par t of the
operating system (SeTcbPrivilege) . Perform this configuration with the Local Group Policy Editor
(gpedit.msc ).
1. On the gateway machine, run gpedit.msc .
2. Go to Local Computer Policy > Computer Configuration > Windows Settings > Security
 Settings > Local Policies > User Rights Assignment .

3. Under User Rights Assignment , from the list of policies, select Impersonate a client after
authentication .

4. Right-click the policy, open Proper ties , and then view the list of accounts.
The list must include the gateway service account (Contoso\GatewaySvc or
ContosoFrontEnd\GatewaySvc depending on the type of constrained delegation).
5. Under User Rights Assignment , select Act as par t of the operating system (SeTcbPrivilege) from
the list of policies. Ensure that the gateway service account is included in the list of accounts.
6. Restart the On-premises data gateway service process.
Set user-mapping configuration parameters on the gateway machine (if necessary)
If you don't have Azure AD Connect configured, follow these steps to map a Power BI service user to a local
Active Directory user. Each Active Directory user mapped in this way needs to have SSO permissions for your
data source. For more information, see Guy in a Cube video.
1. Open the main gateway configuration file, Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll. By
default, this file is stored at C:\Program Files\On-premises data gateway.
2. Set ADUserNameLookupProper ty to an unused Active Directory attribute. We'll use
msDS-cloudExtensionAttribute1 in the steps that follow. This attribute is available only in Windows Server
2012 and later.
3. Set ADUserNameReplacementProper ty to SAMAccountName and then save the configuration file.
4. From the Ser vices tab of Task Manager, right-click the gateway service and select Restar t .

5. For each Power BI service user you want to enable Kerberos SSO for, set the
msDS-cloudExtensionAttribute1 property of a local Active Directory user (with SSO permission to your
data source) to the full username (UPN) of the Power BI service user. For example, if you sign in to Power
BI service as [email protected] and you want to map this user to a local Active Directory user with SSO
 permissions, say, [email protected], set this user's msDS-cloudExtensionAttribute1 attribute to
[email protected].
You can set the msDS-cloudExtensionAttribute1 property with the Active Directory Users and Computers
MMC snap-in:
a. As a domain administrator, launch Active Director y Users and Computers .
b. Right-click the domain name, select Find , and then enter the account name of the local Active
Directory user to map.
c. Select the Attribute Editor tab.
Locate the msDS-cloudExtensionAttribute1 property, and double-click it. Set the value to the full
username (UPN) of the user you use to sign in to the Power BI service.
d. Select OK .

e. Select Apply . Verify that the correct value has been set in the Value column.

Complete data source-specific configuration steps

SAP HANA and SAP BW have additional data-source specific configuration requirements and prerequisites that
you need to meet before you can establish an SSO connection through the gateway to these data sources. For
more information, see SAP HANA configuration and the SAP BW - CommonCryptoLib (sapcrypto.dll)
configuration page. Although it's possible to configure SAP BW for use with the gx64krb5 SNC library, this
library isn't recommended because it's no longer supported by SAP. You should use CommonCryptoLib or
gx64krb5 as your SNC library. Don't complete the configuration steps for both libraries.

NOTE
Although other SNC libraries might also work for BW SSO, they aren't officially supported by Microsoft.

Run a Power BI report

After you complete all the configuration steps, use the Manage Gateway page in Power BI to configure the data
source to use for SSO. If you have multiple gateways, ensure that you select the gateway you've configured for
Kerberos SSO. Then, under Advanced Settings for the data source, ensure Use SSO via Kerberos for
DirectQuer y queries or Use SSO via Kerberos for DirectQuer y And Impor t queries is checked for
DirectQuery based Reports and Use SSO via Kerberos for DirectQuer y And Impor t queries is checked for
Refresh based Reports.
If you publish a DirectQuery-based report from Power BI Desktop and map it to a data source having the Use
SSO via Kerberos for DirectQuer y queries or the Use SSO via Kerberos for DirectQuer y And Impor t
queries checked, this report would use data that is accessible to the user that's mapped to the (Azure) Active
Directory user that signs in to the Power BI service.
Similarly if you publish a Refresh-based report from Power BI desktop and map it to a data source having the
Use SSO via Kerberos for DirectQuer y And Impor t queries checked, you do not need to provide any
credentials. The refresh is executed under the the dataset owner's active directory context.
If however, you map it to a data source where Use SSO via Kerberos for DirectQuer y And Impor t queries
isn't checked, the refresh uses the credentials that you entered in the Username and Password fields when you
created the data source. In other words, Kerberos SSO is not used.
When you publish, select the gateway you've configured for SSO if you have multiple gateways.
This configuration works in most cases. However, with Kerberos there can be different configurations depending
on your environment. If the report won't load, contact your domain administrator to investigate further. If your
data source is SAP BW, refer to the troubleshooting sections of the data source-specific configuration pages for
CommonCryptoLib and gx64krb5/gsskrb5, depending on which SNC library you've chosen.

Next steps
For more information about the on-premises data gateway and DirectQuery, see the following resources:
What is an on-premises data gateway?
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use Kerberos for single sign-on (SSO) to SAP HANA
9/9/2020 • 2 minutes to read • Edit Online

This article describes how to configure your SAP HANA data source to enable SSO from the Power BI service.

NOTE
Before you attempt to refresh a SAP HANA-based report that uses Kerberos SSO, complete both the steps in this article and
the steps in Configure Kerberos SSO.

Enable SSO for SAP HANA

To enable SSO for SAP HANA, follow these steps:
1. Ensure the SAP HANA server is running the required minimum version, which depends on your SAP HANA
server platform level:
HANA 2 SPS 01 Rev 012.03
HANA 2 SPS 02 Rev 22
HANA 1 SP 12 Rev 122.13
2. On the gateway machine, install the latest SAP HANA ODBC driver. The minimum version is HANA ODBC
version 2.00.020.00 from August 2017.
3. Ensure that the SAP HANA server has been configured for Kerberos-based SSO. For more information about
setting up SSO for SAP HANA by using Kerberos, see Single Sign-on Using Kerberos in the SAP HANA
Security Guide. Also see the links from that page, particularly SAP Note 1837331 – HOWTO HANA DBSSO
Kerberos/Active Directory.
We also recommend following these additional steps, which can yield a small performance improvement:
1. In the gateway installation directory, find and open this configuration file:
Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config.
2. Find the FullDomainResolutionEnabled property, and change its value to True .

<setting name=" FullDomainResolutionEnabled " serializeAs="String">

<value>True</value>
</setting>

Now, Run a Power BI report.

Next steps
For more information about the on-premises data gateway and DirectQuery, see the following resources:
What is an on-premises data gateway?
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use Kerberos single sign-on for SSO to SAP BW
using CommonCryptoLib (sapcrypto.dll)
9/9/2020 • 6 minutes to read • Edit Online

This article describes how to configure your SAP BW data source to enable SSO from the Power BI service by using
CommonCryptoLib (sapcrypto.dll).

NOTE
Before you attempt to refresh a SAP BW-based report that uses Kerberos SSO, complete both the steps in this article and
the steps in Configure Kerberos SSO. Using CommonCryptoLib as your SNC library enables SSO connections to both SAP
BW Application Servers and SAP BW Message Servers.

Configure SAP BW to enable SSO using CommonCryptoLib

NOTE
The on-premises data gateway is 64-bit software and therefore requires the 64-bit version of CommonCryptoLib
(sapcrypto.dll) to perform BW SSO. If you plan to test the SSO connection to your SAP BW server in SAP GUI prior to
attempting an SSO connection through the gateway (recommended), you'll also need the 32-bit version of
CommonCryptoLib, as SAP GUI is 32-bit software.

1. Ensure that your BW server is correctly configured for Kerberos SSO using CommonCryptoLib. If it is, you
can use SSO to access your BW server (either directly or through an SAP BW Message Server) with an SAP
tool like SAP GUI that has been configured to use CommonCryptoLib.
For more information on setup steps, see SAP Single Sign-On: Authenticate with Kerberos/SPNEGO. Your
BW server should use CommonCryptoLib as its SNC Library and have an SNC name that starts with CN=,
such as CN=BW1. For more information on SNC name requirements (specifically, the snc/identity/as
parameter), see SNC Parameters for Kerberos Configuration.
2. If you haven't already done so, install the x64-version of the SAP .NET Connector on the computer the
gateway has been installed on.
You can check whether the component has been installed by attempting to connect to your BW server in
Power BI Desktop from the gateway computer. If you can't connect by using the 2.0 implementation, the .NET
Connector isn't installed or hasn't been installed to the GAC.
3. Ensure that SAP Secure Login Client (SLC) isn't running on the computer the gateway is installed on.
SLC caches Kerberos tickets in a way that can interfere with the gateway's ability to use Kerberos for SSO.
4. If SLC is installed, uninstall it or make sure you exit SAP Secure Login Client. Right-click the icon in the
system tray and select Log Out and Exit before you attempt an SSO connection by using the gateway.
SLC isn't supported for use on Windows Server machines. For more information, see SAP Note 2780475 (s-
user required).
5. If you uninstall SLC or select Log Out and Exit , open a cmd window and enter klist purge to clear any
cached Kerberos tickets before you attempt an SSO connection through the gateway.
6. Download 64-bit CommonCryptoLib (sapcrypto.dll) version 8.5.25 or greater from the SAP Launchpad, and
copy it to a folder on your gateway machine. In the same directory where you copied sapcrypto.dll, create a
file named sapcrypto.ini, with the following content:

ccl/snc/enable_kerberos_in_client_role = 1

The .ini file contains configuration information required by CommonCryptoLib to enable SSO in the gateway
scenario.

NOTE
These files must be stored in the same location; in other words, /path/to/sapcrypto/ should contain both
sapcrypto.ini and sapcrypto.dll.

Both the gateway service user and the Active Directory (AD) user that the service user impersonates need
read and execute permissions for both files. We recommend granting permissions on both the .ini and .dll
files to the Authenticated Users group. For testing purposes, you can also explicitly grant these permissions
to both the gateway service user and the Active Directory user you use for testing. In the following
screenshot we've granted the Authenticated Users group Read & execute permissions for sapcrypto.dll:
 7. If you don't already have an SAP BW data source associated with the gateway you want the SSO connection
to flow through, add one on the Manage gateways page in the Power BI service. If you already have such a
data source, edit it:
Choose SAP Business Warehouse as the Data Source Type if you want to create an SSO connection
to a BW Application Server.
Select Sap Business Warehouse Message Ser ver if you want to create an SSO connection to a BW
Message Server.
8. For SNC Librar y , select either the SNC_LIB or SNC_LIB_64 environment variable, or Custom .
If you select SNC_LIB , you must set the value of the SNC_LIB_64 environment variable on the
gateway machine to the absolute path of the 64-bit copy of sapcrypto.dll on the gateway machine.
For example, C:\Users\Test\Desktop\sapcrypto.dll.
If you choose Custom , paste the absolute path to sapcrypto.dll into the Custom SNC Library Path
field that appears on the Manage gateways page.
9. For SNC Par tner Name , enter the SNC Name of the BW server. Under Advanced settings , ensure that
Use SSO via Kerberos for DirectQuer y queries is checked. Fill in the other fields as if you were
establishing a Windows Authentication connection from PBI Desktop.
10. Create a CCL_PROFILE system environment variable and set its value to the path to sapcrypto.ini.
 The sapcrypto .dll and .ini files must exist in the same location. In the above example, sapcrypto.ini and
sapcrypto.dll are both located on the desktop.
11. Restart the gateway service.

12. Run a Power BI report

Troubleshooting
If you're unable to refresh the report in the Power BI service, you can use gateway tracing, CPIC tracing, and
CommonCryptoLib tracing to diagnose the issue. Because CPIC tracing and CommonCryptoLib are SAP products,
Microsoft can't provide support for them.
Gateway logs
1. Reproduce the issue.
2. Open the gateway app, and select Expor t logs from the Diagnostics tab.

CPIC tracing
1. To enable CPIC tracing, set two environment variables: CPIC_TRACE and CPIC_TRACE_DIR .
The first variable sets the trace level and the second variable sets the trace file directory. The directory must
be a location that members of the Authenticated Users group can write to.
2. Set CPIC_TRACE to 3 and CPIC_TRACE_DIR to whichever directory you want the trace files written to. For
example:

3. Reproduce the issue and ensure that CPIC_TRACE_DIR contains trace files.
CPIC tracing can diagnose higher level issues such as a failure to load the sapcrypto.dll library. For example,
here is a snippet from a CPIC trace file where a .dll load error occured:

[Thr 7228] *** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("C:\Users\test\Desktop\sapcrypto.dll")

Error 5 = "Access is denied." [dlnt.c 255]

If you encounter such a failure but you've set the Read & Execute permissions on sapcrypto.dll and
sapcrypto.ini as described in the section above, try setting the same Read & Execute permissions on the
folder that contains the files.
If you're still unable to load the .dll, try turning on auditing for the file. Examining the resulting audit logs in
the Windows Event Viewer might help you determine why the file is failing to load. Look for a failure entry
initiated by the impersonated Active Directory user. For example, for the impersonated user
MYDOMAIN\mytestuser a failure in the audit log would look something like this:
 A handle to an object was requested.

Subject:
Security ID: MYDOMAIN\mytestuser
Account Name: mytestuser
Account Domain: MYDOMAIN
Logon ID: 0xCF23A8

Object:
Object Server: Security
Object Type: File
Object Name: <path information>\sapcrypto.dll
Handle ID: 0x0
Resource Attributes: -

Process Information:
Process ID: 0x2b4c
Process Name: C:\Program Files\On-premises data gateway\Microsoft.Mashup.Container.NetFX45.exe

Access Request Information:

Transaction ID: {00000000-0000-0000-0000-000000000000}
Accesses: ReadAttributes

Access Reasons: ReadAttributes: Not granted

Access Mask: 0x80

Privileges Used for Access Check: -
Restricted SID Count: 0

CommonCryptoLib tracing
1. Turn on CommonCryptoLib tracing by adding these lines to the sapcrypto.ini file you created earlier:

ccl/trace/level=5
ccl/trace/directory=<drive>:\logs\sectrace

2. Change the ccl/trace/directory option to a location to which members of the Authenticated Users group
can write.
3. Alternatively, create a new .ini file to change this behavior. In the same directory as sapcrypto.ini and
sapcrypto.dll, create a file named sectrace.ini, with the following content. Replace the DIRECTORY option with
a location on your machine that members of the Authenticated Users group can write to:

LEVEL = 5
DIRECTORY = <drive>:\logs\sectrace

4. Reproduce the issue and verify that the location pointed to by DIRECTORY contains trace files.
5. When you're finished, turn off CPIC and CCL tracing.
For more information on CommonCryptoLib tracing, see SAP Note 2491573 (SAP s-user required).

Next steps
For more information about the on-premises data gateway and DirectQuery, see the following resources:
What is an on-premises data gateway?
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use Kerberos for single sign-on (SSO) to SAP BW
using gx64krb5
9/9/2020 • 10 minutes to read • Edit Online

This article describes how to configure your SAP BW data source to enable SSO from the Power BI service by using
gx64krb5.

NOTE
You can complete the steps in this article in addition to the steps in Configure Kerberos SSO to enable SSO-based refresh for
SAP BW Application Server-based reports in Power BI service. However, Microsoft recommends the use of
CommonCryptoLib, not gx64krb5 as your SNC library. SAP no longer supports gx64krb5 and the steps required to configure
it for the gateway are significantly more complex compared to CommonCryptoLib. For information about how to configure
SSO by using CommonCryptoLib, see Configure SAP BW for SSO using CommonCryptoLib. You should use
CommonCryptoLib or gx64krb5 as your SNC library. Do not complete the configuration steps for both libraries.

This guide is comprehensive; if you've already completed some of the described steps, you can skip them. For
example, you might have already configured your SAP BW server for SSO using gx64krb5.

Set up gx64krb5 on the gateway machine and the SAP BW server

NOTE
The gx64krb5 library is no longer supported by SAP. For more information, see SAP Note 352295. Note that gx64krb5
doesn't allow for SSO connections from the data gateway to SAP BW Message Servers; only connections to SAP BW
Application Servers are possible. This restriction doesn't exist if you use CommonCryptoLib as your SNC library. Although
other SNC libraries might also work for BW SSO, they aren't officially supported by Microsoft.

The gx64krb5 library must be used by both the client and server to complete an SSO connection through the
gateway. That is, both the client and server must be using the same SNC library.
1. Download gx64krb5.dll from SAP Note 2115486 (SAP s-user required). Ensure you have at least version
1.0.11.x. Also, download gsskrb5.dll (the 32-bit version of the library) if you want to test the SSO connection
in SAP GUI before you attempt the SSO connection through the gateway (recommended). The 32-bit version
is required to test with SAP GUI because SAP GUI is 32-bit only.
2. Put gx64krb5.dll in a location on your gateway machine that's accessible by your gateway service user. If you
want to test the SSO connection with SAP GUI, also put a copy of gsskrb5.dll on your machine and set the
SNC_LIB environment variable to point to it. Both the gateway service user and the Active Directory (AD)
users that the service user will impersonate need read and execute permissions for the copy of gx64krb5.dll.
We recommend granting permissions on the .dll to the Authenticated Users group. For testing purposes, you
can also explicitly grant these permissions to both the gateway service user and the Active Directory user
you use to test.
3. If your BW server hasn't already been configured for SSO using gx64krb5.dll, put another copy of the .dll on
your SAP BW server machine in a location accessible by the SAP BW server.
For more information on configuring gx64krb5.dll for use with an SAP BW server, see SAP documentation
(SAP s-user required).
4. On the client and server machines, set the SNC_LIB and SNC_LIB_64 environment variables:
If you use gsskrb5.dll, set the SNC_LIB variable to its absolute path.
If you use gx64krb5.dll, set the SNC_LIB_64 variable to its absolute path.

Configure an SAP BW service user and enable SNC communication on

the BW server
Complete this section if you haven't already configured your SAP BW server for SNC communication (for example,
SSO) by using gx64krb5.

NOTE
This section assumes that you've already created a service user for BW and bound a suitable SPN to it (that is, a name that
begins with SAP/).

1. Give the service user access to your SAP BW Application Server:

a. On the SAP BW server machine, add the service user to the Local Admin group. Open the Computer
Management program and identify the Local Admin group for your server.

b. Double-click the Local Admin group, and select Add to add your service user to the group.
c. Select Check Names to ensure you've entered the name correctly, and then select OK .
2. Set the SAP BW server's service user as the user that starts the SAP BW server service on the SAP BW server
machine:
a. Open Run , and then enter Ser vices.msc .
b. Find the service corresponding to your SAP BW Application Server instance, right-click it, and then
select Proper ties .
 c. Switch to the Log on tab, and change the user to your SAP BW service user.
d. Enter the user's password, and then select OK .
3. In SAP Logon, sign in to your server and set the following profile parameters by using the RZ10 transaction:
a. Set the snc/identity/as profile parameter to p:<SAP BW service user you created>. For example,
p:[email protected]. Note that p: precedes the service user's UPN, as opposed to
p:CN=, which precedes the UPN when you use CommonCryptoLib as the SNC library.
b. Set the snc/gssapi_lib profile parameter to <path to gx64krb5.dll on the BW server>. Place the
library in a location that the SAP BW Application Server can access.
c. Set the following additional profile parameters, changing the values as required to fit your needs. The
last five options enable clients to connect to the SAP BW server by using SAP Logon without having
SNC configured.

SET T IN G VA L UE

snc/data_protection/max 3

snc/data_protection/min 1

snc/data_protection/use 9

snc/accept_insecure_cpic 1

snc/accept_insecure_gui 1

snc/accept_insecure_r3int_rfc 1

snc/accept_insecure_rfc 1

snc/permit_insecure_start 1

d. Set the snc/enable property to 1.

4. After you set these profile parameters, open the SAP Management Console on the server machine and
restart the SAP BW instance.
If the server won't start, confirm that you've set the profile parameters correctly. For more information on
profile parameter settings, see the SAP documentation. You can also consult the Troubleshooting section in
this article.
Map an SAP BW user to an Active Directory user
If you haven't done so already, map an Active Directory user to an SAP BW Application Server user and test the
SSO connection in SAP Logon.
1. Sign in to your SAP BW server with SAP Logon. Run transaction SU01.
2. For User , enter the SAP BW user for which you want to enable SSO connection. Select the Edit icon (pen
icon) near the top left of the SAP Logon window.

3. Select the SNC tab. In the SNC name input box, enter p:<your Active Directory user>@<your domain>. For
the SNC name, p: must precede the Active Directory user's UPN. Note that the UPN is case-sensitive.
The Active Directory user you specify should belong to the person or organization for whom you want to
enable SSO access to the SAP BW Application Server. For example, if you want to enable SSO access for the
user [email protected], enter p:[email protected].
4. Select the Save icon (floppy disk image) near the top left of the screen.

Test sign in via SSO

Verify that you can sign in to the server by using SAP Logon through SSO as the Active Directory user for whom
you've enabled SSO access:
1. As the Active Directory user for which you've just enabled SSO access, sign in to a machine in your domain
on which SAP Logon is installed. Launch SAP Logon, and create a new connection.
2. Copy the gsskrb5.dll file you downloaded earlier to a location on the machine you signed-in to. Set the
SNC_LIB environment variable to the absolute path of this location.
3. Launch SAP Logon, and create a new connection.
4. In the Create New System Entr y screen, select User Specified System , then select Next .

5. Fill in the appropriate details on the next screen, including the application server, instance number, and
 system ID. Then, select Finish .
6. Right-click the new connection, select Proper ties , and then select the Network tab.
7. In the SNC Name box, enter p:<SAP BW service user's UPN>. For example,
p:[email protected]. Select OK .

8. Double-click the connection you just created to attempt an SSO connection to your SAP BW server.
If this connection succeeds, continue to the next section. Otherwise, review the earlier steps in this document
to make sure they've been completed correctly, or review the Troubleshooting section. If you can't connect to
the SAP BW server via SSO in this context, you won't be able to connect to the SAP BW server by using SSO
in the gateway context.

Add registry entries to the gateway machine

Add required registry entries to the registry of the machine that the gateway is installed on, and to machines
intended to connect from Power BI Desktop. To add these registry entries, run the following commands:
REG ADD HKLM\SOFTWARE\Wow6432Node\SAP\gsskrb5 /v ForceIniCredOK /t REG_DWORD /d 1 /f

REG ADD HKLM\SOFTWARE\SAP\gsskrb5 /v ForceIniCredOK /t REG_DWORD /d 1 /f

Add a new SAP BW Application Server data source to the Power BI

service, or edit an existing one
1. In the data source configuration window, enter the SAP BW Application Server's Hostname , System
Number , and client ID , as you would to sign in to your SAP BW server from Power BI Desktop.
2. In the SNC Par tner Name field, enter p:<SPN you mapped to your SAP BW service user>. For example, if
the SPN is SAP/[email protected], enter p:SAP/[email protected] in the
SNC Par tner Name field.
3. For the SNC Library, select SNC_LIB or SNC_LIB_64 . Make sure that SNC_LIB_64 on the gateway
 machine points to gx64krb5.dll. Alternatively, you can select the Custom option and provide the absolute
path for gx64krb5.dll on the gateway machine.
4. Select Use SSO via Kerberos for DirectQuer y queries , and then select Apply . If the test connection is
not successful, verify that the previous setup and configuration steps were completed correctly.
5. Run a Power BI report

Troubleshooting
Troubleshoot gx64krb5 configuration
If you encounter any of the following problems, follow these steps to troubleshoot the gx64krb5 installation and
SSO connections:
You encounter errors when you complete the gx64krb5 setup steps. For example, the SAP BW server won't
start after you've changed the profile parameters. View the server logs (…work\dev_w0 on the server
machine) to troubleshoot these errors.
You can't start the SAP BW service due to a sign-on failure. You might have provided the wrong password
when you set the SAP BW start-as user. Verify the password by signing in as the SAP BW service user on a
machine in your Active Directory environment.
You get errors about underlying data source credentials (for example, SQL Server), which prevent the server
from starting, verify that you've granted the service user access to the SAP BW database.
You get the following message: (GSS-API) specified target is unknown or unreachable. This error usually
means you have the wrong SNC name specified. Make sure to use p: only, not p:CN=, to precede the service
user's UPN in the client application.
You get the following message: (GSS-API) An invalid name was supplied. Make sure p: is the value of the
server's SNC identity profile parameter.
You get the following message: (SNC error) the specified module could not be found. This error is often
caused by placing gx64krb5.dll in a location that requires elevated privileges (../administrator rights) to
access.
Troubleshoot gateway connectivity issues
1. Check the gateway logs. Open the gateway configuration application, and select Diagnostics , then Expor t
logs . The most recent errors are at the end of any log files you examine.
2. Turn on SAP BW tracing, and review the generated log files. There are several different types of SAP BW
tracing available (for example, CPIC tracing):
a. To enable CPIC tracing, set two environment variables: CPIC_TRACE and CPIC_TRACE_DIR .
The first variable sets the trace level and the second variable sets the trace file directory. The directory must
be a location that members of the Authenticated Users group can write to.
b. Set CPIC_TRACE to 3 and CPIC_TRACE_DIR to whichever directory you want the trace files written to.
For example:

c. Reproduce the issue and ensure that CPIC_TRACE_DIR contains trace files.
d. Examine the contents of the trace files to determine the blocking issue. For example, you may find that
gx64krb5.dll was not loaded properly, or that an Active Directory user different than the one you were
expecting initiated the SSO connection attempt.

Next steps
For more information about the on-premises data gateway and DirectQuery, see the following resources:
What is an on-premises data gateway?
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Use Security Assertion Markup Language (SAML) for
SSO from Power BI to on-premises data sources
9/9/2020 • 6 minutes to read • Edit Online

Enabling SSO makes it easy for Power BI reports and dashboards to refresh data from on-premises sources while
respecting user-level permissions configured on those sources. Use Security Assertion Markup Language (SAML)
to enable seamless single sign-on connectivity.

Supported data sources

We currently support SAP HANA with SAML. For more information about setting up and configuring single sign-
on for SAP HANA by using SAML, see SAML SSO for BI Platform to HANA.
We support additional data sources with Kerberos (including SAP HANA).
For SAP HANA, it's recommended you enable encryption before you establish a SAML SSO connection. To enable
encryption, configure the HANA server to accept encrypted connections and configure the gateway to use
encryption to communicate with your HANA server. Because the HANA ODBC driver doesn't encrypt SAML
assertions by default, the signed SAML assertion is sent from the gateway to the HANA server in the clear and is
vulnerable to interception and reuse by third parties. For instructions about how to enable encryption for HANA
with the OpenSSL library, see Enable encryption for SAP HANA.

Configuring the gateway and data source

To use SAML, you must establish a trust relationship between the HANA servers for which you want to enable SSO
and the gateway. In this scenario, the gateway serves as the SAML Identity Provider (IdP). There are various ways to
establish this relationship, such as importing the gateway IdP's x509 certificate into the HANA servers' trust store,
or by having the gateway's X509 certificate signed by a root Certification Authority (CA) trusted by the HANA
servers. Although we describe the latter approach in this guide, you can use another approach if it's more
convenient.
While this guide uses OpenSSL as the HANA server's cryptographic provider, SAP recommends you use the SAP
Cryptographic Library (also known as CommonCryptoLib or sapcrypto) instead of OpenSSL to complete the setup
steps in which we establish the trust relationship. For more information, see the official SAP documentation.
The following steps describe how to establish a trust relationship between a HANA server and the gateway IdP by
signing the gateway IdP's X509 certificate with a Root CA trusted by the HANA server. You'll create this Root CA:
1. Create the Root CA's X509 certificate and private key. For example, to create the Root CA's X509 certificate
and private key in .pem format, enter this command:

openssl req -new -x509 -newkey rsa:2048 -days 3650 -sha256 -keyout CA_Key.pem -out CA_Cert.pem -
extensions v3_ca

Ensure that the Root CA's private key is secured properly. If it's obtained by a third party, it could be used to
gain unauthorized access to the HANA server.
2. Add the certificate (for example, CA_Cert.pem) to the HANA server's trust store so that the HANA server will
trust any certificates signed by the Root CA you created.
You can find the location of your HANA server's trust store by examining the ssltruststore configuration
 setting. If you've followed the instructions in the SAP documentation covering how to configure OpenSSL,
your HANA server might already trust a Root CA you that can reuse. For more information, see How to
Configure Open SSL for SAP HANA Studio to SAP HANA Server. If you have multiple HANA servers for
which you want to enable SAML SSO, make sure that each of the servers trusts this Root CA.
3. Create the gateway IdP's X509 certificate.
For example, to create a certificate-signing request (IdP_Req.pem) and a private key (IdP_Key.pem) that are
valid for a year, execute the following command:

openssl req -newkey rsa:2048 -days 365 -sha256 -keyout IdP_Key.pem -out IdP_Req.pem -nodes

4. Sign the certificate-signing request by using the Root CA you've configured your HANA servers to trust.
For example, to sign IdP_Req.pem using CA_Cert.pem and CA_Key.pem (the certificate and key of the Root
CA), execute the following command:

openssl x509 -req -days 365 -in IdP_Req.pem -sha256 -extensions usr_cert -CA CA_Cert.pem -CAkey
CA_Key.pem -CAcreateserial -out IdP_Cert.pem

The resulting IdP certificate is valid for a year (see the -days option).
Import your IdP's certificate in HANA Studio to create a new SAML Identity Provider:
1. In SAP HANA Studio, right-click your SAP HANA server name, then navigate to Security > Open Security
Console > SAML Identity Provider > OpenSSL Cr yptographic Librar y .

2. Select Impor t , navigate to IdP_Cert.pem, and import it.

3. In SAP HANA Studio, select the Security folder.

4. Expand Users , and then select the user you want to map your Power BI user to.
5. Select SAML , and then select Configure .

6. Select the identity provider you created in step 2. For External Identity , enter the Power BI user's UPN
(typically the email address the user uses to sign in to Power BI), and then select Add . If you've configured
 your gateway to use the ADUserNameReplacementProperty configuration option, enter the value that will
replace the Power BI user's original UPN.
For example, if you set ADUserNameReplacementProperty to SAMAccountName you should enter the
user's SAMAccountName .

Now that you have the gateway's certificate and identity configured, convert the certificate to a pfx format and
configure the gateway to use the certificate:
1. Convert the certificate to pfx format by running the following command. This command names the
resulting .pfx file samlcert.pfx and sets root as its password:

openssl pkcs12 -export -out samltest.pfx -in IdP_Cert.pem -inkey IdP_Key.pem -passin pass:root -passout
pass:root

2. Copy the pfx file to the gateway machine:

a. Double-click samltest.pfx, then select Local Machine > Next .
b. Enter the password, then select Next .
c. Select Place all cer tificates in the following store, then select Browse > Personal > OK .
d. Select Next , and then Finish .

3. Grant the gateway service account access to the private key of the certificate:
a. On the gateway machine, run the Microsoft Management Console (MMC).
 b. Under File , select Add/Remove Snap-in .

c. Select Cer tificates > Add , then select Computer account > Next .
d. Select Local Computer > Finish > OK .
e. Expand Cer tificates > Personal > Cer tificates , and find the certificate.
f. Right-click the certificate and navigate to All Tasks > Manage Private Keys .

g. Add the gateway service account to the list. By default, the account is NT SERVICE\PBIEgwSer vice .
You can find out which account is running the Gateway service by running ser vices.msc and
locating On-premises data gateway ser vice .

Finally, follow these steps to add the certificate thumbprint to the gateway configuration:
1. Run the following PowerShell command to list the certificates on your machine:

Get-ChildItem -path cert:\LocalMachine\My

2. Copy the thumbprint for the certificate you created.
3. Navigate to the gateway directory, which by default is C:\Program Files\On-premises data gateway.
4. Open PowerBI.DataMovement.Pipeline.GatewayCore.dll.config, and find the SapHanaSAMLCertThumbprint
section. Paste the thumbprint you copied.
5. Restart the gateway service.

Running a Power BI report

Now you can use the Manage Gateway page in Power BI to configure the SAP HANA data source. Under
Advanced Settings , enable SSO via SAML. Doing so allows you to publish reports and datasets binding to that
data source.

Troubleshooting
After you configure SAML-based SSO, you might see the following error in the Power BI portal: The credentials
provided cannot be used for the SapHana source. This error indicates that the SAML credential was rejected by SAP
HANA.
Server-side authentication traces provide detailed information for troubleshooting credential issues on SAP HANA.
Follow these steps to configure tracing for your SAP HANA server:
1. On the SAP HANA server, turn on the authentication trace by running the following query:

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') set ('trace', 'authentication') =

'debug' with reconfigure

2. Reproduce the issue.

3. In HANA Studio, open the administration console, and select the Diagnosis Files tab.
4. Open the latest index server trace and search for SAMLAuthenticator.cpp.
You should find a detailed error message that indicates the root cause, for example:

[3957]{-1}[-1/-1] 2018-09-11 21:40:23.815797 d Authentication SAMLAuthenticator.cpp(00091) : Element

'{urn:oasis:names:tc:SAML:2.0:assertion}Assertion', attribute 'ID': '123123123123123' is not a valid
value of the atomic type 'xs:ID'.
[3957]{-1}[-1/-1] 2018-09-11 21:40:23.815914 i Authentication SAMLAuthenticator.cpp(00403) : No valid
SAML Assertion or SAML Protocol detected

5. After the troubleshooting is complete, turn off the authentication trace by running the following query:

ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM') UNSET ('trace', 'authentication');

Next steps
For more information about the on-premises data gateway and DirectQuery, see the following resources:
What is an on-premises data gateway?
DirectQuery in Power BI
Data sources supported by DirectQuery
DirectQuery and SAP BW
DirectQuery and SAP HANA
 Troubleshoot gateways - Power BI
9/9/2020 • 10 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and
general content that applies to all services that the gateway supports. You're currently in the Power BI content. To
provide feedback on this article, or the overall gateway docs experience, scroll to the bottom of the article.

This article discusses some common issues when you use the on-premises data gateway with Power BI. If you
encounter an issue that isn't listed here, you can use the Power BI Community site. Or, you can create a
support ticket.

Configuration
Error: Power BI service reported local gateway as unreachable. Restart the gateway and try again.
At the end of configuration, the Power BI service is called again to validate the gateway. The Power BI service
doesn't report the gateway as live. Restarting the Windows service might allow the communication to be
successful. To get more information, you can collect and review the logs as described in Collect logs from the
on-premises data gateway app.

Data sources
Error: Unable to Connect. Details: "Invalid connection credentials"
Within Show details , the error message that was received from the data source is displayed. For SQL Server,
you see something like the following:

Login failed for user 'username'.

Verify that you have the correct username and password. Also, verify that those credentials can successfully
connect to the data source. Make sure the account that's being used matches the authentication method.
Error: Unable to Connect. Details: "Cannot connect to the database"
You were able to connect to the server but not to the database that was supplied. Verify the name of the
database and that the user credential has the proper permission to access that database.
Within Show details , the error message that was received from the data source is displayed. For SQL Server,
you see something like the following:

Cannot open database "AdventureWorks" requested by the login. The login failed. Login failed for user
'username'.

Error: Unable to Connect. Details: "Unknown error in data gateway"

This error might occur for different reasons. Be sure to validate that you can connect to the data source from
the machine that hosts the gateway. This situation could be the result of the server not being accessible.
Within Show details , you can see an error code of DM_GWPipeline_UnknownError .
You can also look in Event Logs > Applications and Ser vices Logs > On-premises data gateway
Ser vice for more information.
Error: We encountered an error while trying to connect to <server>. Details: "We reached the data
gateway, but the gateway can't access the on-premises data source."
You were unable to connect to the specified data source. Be sure to validate the information provided for that
data source.
Within Show details , you can see an error code of DM_GWPipeline_Gateway_DataSourceAccessError .
If the underlying error message is similar to the following, this means that the account you're using for the
data source isn't a server admin for that Analysis Services instance. For more information, see Grant server
admin rights to an Analysis Services instance.

The 'CONTOSO\account' value of the 'EffectiveUserName' XML for Analysis property is not valid.

If the underlying error message is similar to the following, it could mean that the service account for Analysis
Services might be missing the token-groups-global-and-universal (TGGAU) directory attribute.

The username or password is incorrect.

Domains with pre-Windows 2000 compatibility access have the TGGAU attribute enabled. Most newly created
domains don't enable this attribute by default. For more information, see Some applications and APIs require
access to authorization information on account objects.
To confirm whether the attribute is enabled, follow these steps.
1. Connect to the Analysis Services machine within SQL Server Management Studio. Within the
Advanced connection properties, include EffectiveUserName for the user in question and see if this
addition reproduces the error.
2. You can use the dsacls Active Directory tool to validate whether the attribute is listed. This tool is found
on a domain controller. You need to know what the distinguished domain name is for the account and
pass that name to the tool.

dsacls "CN=John Doe,CN=UserAccounts,DC=contoso,DC=com"

You want to see something similar to the following in the results:

Allow BUILTIN\Windows Authorization Access Group

SPECIAL ACCESS for tokenGroupsGlobalAndUniversal
READ PROPERTY

To correct this issue, you must enable TGGAU on the account used for the Analysis Services Windows service.
Another possibility for "The username or password is incorrect."
This error could also be caused if the Analysis Services server is in a different domain than the users and
there isn't a two-way trust established.
Work with your domain administrators to verify the trust relationship between domains.
Unable to see the data gateway data sources in the Get Data experience for Analysis Services from the Power BI service
Make sure that your account is listed in the Users tab of the data source within the gateway configuration. If
you don't have access to the gateway, check with the administrator of the gateway and ask them to verify.
Only accounts in the Users list can see the data source listed in the Analysis Services list.
Error: You don't have any gateway installed or configured for the data sources in this dataset.
Ensure that you've added one or more data sources to the gateway, as described in Add a data source. If the
gateway doesn't appear in the admin portal under Manage gateways , clear your browser cache or sign out
of the service and then sign back in.

Datasets
Error: There is not enough space for this row.
This error occurs if you have a single row greater than 4 MB in size. Determine what the row is from your
data source, and attempt to filter it out or reduce the size for that row.
Error: The server name provided doesn't match the server name on the SQL Server SSL certificate.
This error can occur when the certificate common name is for the server's fully qualified domain name
(FQDN), but you supplied only the NetBIOS name for the server. This situation causes a mismatch for the
certificate. To resolve this issue, make the server name within the gateway data source and the PBIX file use
the FQDN of the server.
Error: You don't see the on-premises data gateway present when you configure scheduled refresh.
A few different scenarios could be responsible for this error:
The server and database name don't match what was entered in Power BI Desktop and the data source
configured for the gateway. These names must be the same. They aren't case sensitive.
Your account isn't listed in the Users tab of the data source within the gateway configuration. You need to
be added to that list by the administrator of the gateway.
Your Power BI Desktop file has multiple data sources within it, and not all of those data sources are
configured with the gateway. You need to have each data source defined with the gateway for the gateway
to show up within scheduled refresh.
Error: The received uncompressed data on the gateway client has exceeded the limit.
The exact limitation is 10 GB of uncompressed data per table. If you're hitting this issue, there are good
options to optimize and avoid it. In particular, reduce the use of highly constant, long string values and
instead use a normalized key. Or, removing the column if it's not in use helps.

Reports
Error: Report could not access the data source because you do not have access to our data source via an
on-premises data gateway.
This error is usually caused by one of the following:
The data source information doesn't match what's in the underlying dataset. The server and database
name need to match between the data source defined for the on-premises data gateway and what you
supply within Power BI Desktop. If you use an IP address in Power BI Desktop, the data source for the on-
premises data gateway needs to use an IP address as well.
There's no data source available on any gateway within your organization. You can configure the data
source on a new or existing on-premises data gateway.
Error: Data source access error. Please contact the gateway administrator.
If this report makes use of a live Analysis Services connection, you could encounter an issue with a value
being passed to EffectiveUserName that either isn't valid or doesn't have permissions on the Analysis
Services machine. Typically, an authentication issue is due to the fact that the value being passed for
EffectiveUserName doesn't match a local user principal name (UPN).
To confirm the effective username, follow these steps.
1. Find the effective username within the gateway logs.
2. After you have the value being passed, validate that it's correct. If it's your user, you can use the
following command from a command prompt to see the UPN. The UPN looks like an email address.

whoami /upn

Optionally, you can see what Power BI gets from Azure Active Directory.
1. Browse to https://developer.microsoft.com/graph/graph-explorer.
2. Select Sign in in the upper-right corner.
3. Run the following query. You see a rather large JSON response.

https://graph.windows.net/me?api-version=1.5

4. Look for userPrincipalName .

If your Azure Active Directory UPN doesn't match your local Active Directory UPN, you can use the Map user
names feature to replace it with a valid value. Or, you can work with either your tenant admin or local Active
Directory admin to get your UPN changed.

Kerberos
If the underlying database server and on-premises data gateway aren't appropriately configured for Kerberos
constrained delegation, enable verbose logging on the gateway. Then, investigate based on the errors or
traces in the gateway’s log files as a starting point for troubleshooting. To collect the gateway logs for
viewing, see Collect logs from the on-premises data gateway app.
ImpersonationLevel
The ImpersonationLevel is related to the SPN setup or the local policy setting.

[DataMovement.PipeLine.GatewayDataAccess] About to impersonate user DOMAIN\User (IsAuthenticated: True,

ImpersonationLevel: Identification)

Solution
Follow these steps to solve the issue.
1. Set up an SPN for the on-premises gateway.
2. Set up constrained delegation in your Active Directory.
FailedToImpersonateUserException: Failed to create Windows identity for user userid
The FailedToImpersonateUserException happens if you're unable to impersonate on behalf of another user.
This error could also happen if the account you're trying to impersonate is from another domain than the one
the gateway service domain is on. This is a limitation.
Solution
Verify that the configuration is correct as per the steps in the previous "ImpersonationLevel" section.
Ensure that the user ID it's trying to impersonate is a valid Active Directory account.
General error: 1033 error while you parse the protocol
You get the 1033 error when your external ID that's configured in SAP HANA doesn't match the sign-in if the
user is impersonated by using the UPN ([email protected]). In the logs, you see "Original UPN
'[email protected]' replaced with a new UPN '[email protected]'" at the top of the error logs, as seen here:

[DM.GatewayCore] SingleSignOn Required. Original UPN '[email protected]' replaced with new UPN
'[email protected].'

Solution
SAP HANA requires the impersonated user to use the sAMAccountName attribute in Active Directory
(user alias). If this attribute isn't correct, you see the 1033 error.

In the logs, you see the sAMAccountName (alias) and not the UPN, which is the alias followed by the
domain ([email protected]).

<setting name="ADUserNameReplacementProperty" serializeAs="String">

<value>sAMAccount</value>
</setting>
<setting name="ADServerPath" serializeAs="String">
<value />
</setting>
<setting name="CustomASDataSource" serializeAs="String">
<value />
</setting>
<setting name="ADUserNameLookupProperty" serializeAs="String">
<value>AADEmail</value>

[SAP AG ][LIBODBCHDB DLL ][HDBODBC ] Communication link failure:-10709 Connection failed (RTE:[-1]
Kerberos error. Major: "Miscellaneous failure [851968]." Minor: "No credentials are available in the security
package."
You get the "-10709 Connection failed" error message if your delegation isn't configured correctly in Active
Directory.
Solution
Make sure that you have the SAP Hana server on the delegation tab in Active Directory for the
gateway service account.
Refresh history
When you use the gateway for a scheduled refresh, Refresh histor y can help you see what errors occurred.
It can also provide useful data if you need to create a support request. You can view scheduled and on-
demand refreshes. The following steps show how you can get to the refresh history.
1. In the Power BI nav pane, in Datasets , select a dataset. Open the menu, and select Schedule refresh .

2. In Settings for... > Schedule refresh , select Refresh histor y .

For more information about troubleshooting refresh scenarios, see Troubleshoot refresh scenarios.

Fiddler trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the back and forth with the Power BI
service from the client machine. This traffic list might show errors and other related information.

Next steps
Troubleshoot the on-premises data gateway
Configure proxy settings for the on-premises data gateway
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Import/scheduled refresh
More questions? Try the Power BI Community.
 Troubleshooting Power BI gateway (personal mode)
9/9/2020 • 7 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide
feedback on this article, or the overall gateway docs experience, scroll to the bottom of the article.

The following sections go through some common issues you might come across when you use the Power BI on-
premises data gateway (personal mode).

Update to the latest version

The current version of the gateway for personal use is the on-premises data gateway (personal mode). Update
your installation to use that version.
Many issues can surface when the gateway version is out of date. It's a good general practice to make sure you're
on the latest version. If you haven't updated the gateway for a month or longer, consider installing the latest
version of the gateway. Then see if you can reproduce the issue.

Installation
Gateway (personal mode) operates on 64-bit versions: If your machine is a 32-bit version, you can't
install the gateway (personal mode). Your operating system has to be a 64-bit version. Install a 64-bit version of
Windows or install the gateway (personal mode) on a 64-bit machine.
Gateway (personal mode) fails to install as a ser vice even though you're a local administrator for
the computer : Installation can fail if the user is in the computer’s local Administrator group, but Group Policy
doesn't allow that username to sign in as a service. Ensure that Group Policy lets a user sign in as a service. We’re
working on a fix for this issue. For more information, see Add the Log on as a service right to an account.
Operation timed out: This message is common if the computer (physical machine or VM) on which you’re
installing the gateway (personal mode) has a single core processor. Close any applications, turn off any non-
essential processes, and try installing again.
Data management gateway or Analysis Ser vices connector can't be installed on the same computer
as gateway (personal mode): If you already have an Analysis Servicesconnector or a data management
gateway installed, you must first uninstall the connector or the gateway. Then, try installing the gateway
(personal mode).

NOTE
If you encounter an issue during installation, the setup logs can provide information to help you resolve the issue. For
more information, see Setup logs.

Proxy configuration: You might see issues with configuring the gateway (personal mode) if your environment
needs the use of a proxy. To learn more about how to configure proxy information, see Configure proxy settings
for the on-premises data gateway.
Schedule refresh
Error : The credential stored in the cloud is missing.
You might get this error in settings for <dataset> if you have a scheduled refresh and then you uninstalled and
reinstalled the gateway (personal mode). When you uninstall a gateway (personal mode), the data source
credentials for a dataset that was configured for refresh are removed from the Power BI service.
Solution: In Power BI, go to the refresh settings for a dataset. In Manage Data Sources , for any data source
with an error, select Edit credentials . Then sign in to the data source again.
Error : The credentials provided for the dataset are invalid. Please update the credentials through a
refresh or in the Data Source Settings dialog to continue.
Solution: If you get a credentials message, it could mean:
The usernames and passwords that you used to sign in to data sources aren't up to date. In Power BI, go to
refresh settings for the dataset. In Manage Data Sources , select Edit credentials to update the
credentials for the data source.
Mashups between a cloud source and an on-premises source, in a single query, fail to refresh in the
gateway (personal mode) if one of the sources is using OAuth for authentication. An example of this issue
is a mashup between CRM Online and a local SQL Server instance. The mashup fails because CRM Online
requires OAuth.
This error is a known issue, and it's being looked at. To work around the problem, have a separate query
for the cloud source and the on-premises source. Then, use a merge or append query to combine them.
Error : Unsuppor ted data source.
Solution: If you get an unsupported data source message in Schedule Refresh settings, it could mean:
The data source isn't currently supported for refresh in Power BI.
The Excel workbook doesn't contain a data model, only worksheet data. Power BI currently only supports
refresh if the uploaded Excel workbook contains a data model. When you import data by using Power Query
in Excel, choose the Load option to load data to a data model. This option ensures that data is imported into a
data model.
Error : [Unable to combine data] <quer y par t>/<…>/<…> is accessing data sources that have
privacy levels, which cannot be used together. Please rebuild this data combination.
Solution: This error is because of the privacy-level restrictions and the types of data sources you're using.
Error : Data source error : We cannot conver t the value "[Table]" to type Table.
Solution: This error is because of the privacy-level restrictions and the types of data sources you're using.
Error : There is not enough space for this row.
Solution: This error occurs if you have a single row greater than 4 MB in size. Find the row from your data
source, and attempt to filter it out or reduce the size for that row.

Data sources
Missing data provider : The gateway (personal mode) operates on 64-bit versions only. It requires a 64-bit
version of the data providers to be installed on the same computer where the gateway (personal mode) is
installed. For example, if the data source in the dataset is Microsoft Access, you must install the 64-bit ACE
provider on the same computer where you installed the gateway (personal mode).
 NOTE
If you have a 32-bit version of Excel, you can't install a 64-bit version ACE provider on the same computer.

Windows authentication is not suppor ted for Access database: Power BI currently only supports
Anonymous authentication for the Access database.
Error : Sign-in error when you enter credentials for a data source: If you get an error like this one when
you enter Windows credentials for a data source:

You might still be on an older version of the gateway (personal mode).

Solution: For more information, see Install the latest version of Power BI gateway (personal mode).
Error : Sign-in error when you select Windows authentication for a data source using ACE OLEDB: If
you get the following error when you enter data source credentials for a data source using an ACE OLEDB
provider:

Power BI doesn't currently support Windows authentication for a data source using an ACE OLEDB provider.
Solution: To work around this error, select Anonymous authentication . For a legacy ACE OLEDB provider,
anonymous credentials are equal to Windows credentials.
Tile refresh
If you receive an error when dashboard tiles refresh, see Troubleshooting tile errors.

Tools for troubleshooting

Refresh history
With Refresh histor y , you can see what errors occurred and find useful data if you need to create a support
request. You can view both scheduled and on-demand refreshes. Here's how you get to Refresh histor y .
1. In the Power BI nav pane, in Datasets , select a dataset. Open the menu, and select Schedule Refresh .

2. In Settings for..., select Refresh histor y .

Event logs
Several event logs can provide information. The first two, Data Management Gateway and PowerBIGateway ,
are present if you're an admin on the machine. If you're not an admin, and you're using the data gateway
(personal mode), you'll see the log entries within the Application log.
The Data Management Gateway and PowerBIGateway logs are present under Application and Ser vices
Logs .
Fiddler trace
Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the communication with the Power BI
service from the client machine. This communication might show errors and other related information.

Setup logs
If the gateway (personal mode) fails to install, you'll see a link to show the setup log. The setup log can show you
details about the failure. These logs are Windows Install logs, also known as MSI logs. They can be fairly complex
and hard to read. Typically, the resulting error is at the bottom, but determining the cause of the error isn't trivial.
It could be a result of errors in a different log. It could also be a result of an error higher up in the log.

Or, you can go to your Temp folder (%temp%) and look for files that start with Power_BI_.

NOTE
Going to %temp% might take you to a subfolder of Temp. The Power_BI_ files are in the root of the Temp directory. You
might need to go up a level or two.
Next steps
Configure proxy settings for the on-premises data gateway- Data refresh
Power BI gateway - Personal
Troubleshooting tile errors
Troubleshooting the on-premises data gateway
More questions? Try asking the Power BI Community.
 Use custom data connectors with the on-premises
data gateway
9/9/2020 • 3 minutes to read • Edit Online

NOTE
We recently revised the on-premises data gateway docs. We split them into content that's specific to Power BI and general
content that applies to all services that the gateway supports. You're currently in the Power BI content. To provide feedback
on this article, or the overall gateway docs experience, scroll to the bottom of the article.

With data connectors for Power BI, you can connect to and access data from an application, service, or data source.
You can develop custom data connectors and use them in Power BI Desktop.
To learn more about how to develop custom data connectors for Power BI, see the Data connector SDK GitHub
page. This site includes information on how to get started and samples for Power BI and Power Query.
When you build reports in Power BI Desktop that use custom data connectors, you can use the on-premises data
gateway to refresh those reports from the Power BI service.

Enable and use this capability

When you install the July 2018 version of the on-premises data gateway or a later version, you see a Connectors
tab in the on-premises data gateway app. In the Load custom data connectors from folder box, select a folder
that can be accessed by the user running the gateway service. The default user is NT SERVICE\PBIEgwService. The
gateway automatically loads the custom connector files located in that folder. They appear in the list of data
connectors.
If you're using the on-premises data gateway (personal mode), you can upload your Power BI report to the Power BI
service and use the gateway to refresh it.
For the on-premises data gateway, you need to create a data source for your custom connector. On the gateway
settings page in the Power BI service, you should see an option when you select the gateway cluster to allow using
custom connectors with this cluster. Make sure all gateways in the cluster have the July 2018 update release or later
for this option to be available. Select that option to enable using custom connectors with this cluster.
When this option is enabled, you see your custom connectors as available data sources that you can create under
this gateway cluster. After you create a data source that uses your new custom connector, you can refresh Power BI
reports by using that custom connector in the Power BI service.

Considerations and limitations

 Make sure the folder you create is accessible to the background gateway service. Typically, folders under your
user’s Windows folder or system folders won’t be accessible. The on-premises data gateway app shows a
message if the folder isn't accessible. This instruction doesn't apply for the on-premises data gateway (personal
mode).
For custom connectors to work with the on-premises data gateway, they need to implement a “TestConnection”
section in the custom connector’s code. This section isn't required when you use custom connectors with Power
BI Desktop. For this reason, you can have a connector that works with Power BI Desktop, but not with the
gateway. For more information on how to implement a TestConnection section, see this documentation.
OAuth for custom connectors via gateways is currently supported only for gateway admins but not other data
source users.
If your custom connector is on a network drive, include the fully qualified path on the on-premises data gateway
app.

Next steps
Manage your data source - Analysis Services
Manage your data source - SAP HANA
Manage your data source - SQL Server
Manage your data source - Oracle
Manage your data source - Import/scheduled refresh
Configure proxy settings for the on-premises data gateway
Use Kerberos for single sign-on (SSO) from Power BI to on-premises data sources
More questions? Try asking the Power BI Community.
 Troubleshoot importing Access and Excel .xls files in
Power BI Desktop
9/9/2020 • 3 minutes to read • Edit Online

In Power BI Desktop, both Access databases and early versions of Excel workbooks (.XLS files of type Excel 97-2003)
use the Access Database Engine. There are three common situations that can prevent the Access Database Engine
from working properly.

Situation 1: No Access Database Engine is installed

If the Power BI Desktop error message indicates the Access Database Engine isn't installed, you must install the
Access Database Engine version, either 32-bit or 64-bit, that matches your Power BI Desktop version. You can install
the Access Database Engine from the downloads page.

NOTE
If the installed Access Database Engine bit-version is different from your Microsoft Office installation's bit-version, Office
applications won't be able to use the Access Database Engine.

Situation 2: The Access Database Engine bit-version (32-bit or 64-bit) is

different from your Power BI Desktop bit-version
This situation often occurs when the installed version of Microsoft Office is 32-bit, and the version of Power BI
Desktop installed is 64-bit. The opposite can occur as well and the bit-version mismatch will occur in either case. If
you're using a Microsoft 365 subscription, see Situation 3 for a different issue and resolution. Any of the following
solutions can remedy this bit-version mismatch error:
Solution 1
Change the version of Power BI Desktop to match the bit-version of your Microsoft Office installation.
1. To change the bit-version of Power BI Desktop, uninstall Power BI Desktop, and then install the version of
Power BI Desktop that matches your Office installation.
2. To select a version of Power BI Desktop, select Advanced download options on the Power BI Desktop
download page.

3. On the download page that appears, choose your language and then select the Download button.
4. On the screen that appears, select the checkbox beside PBIDesktop.msi for the 32-bit version, or
PBIDesktop_x64.msi for the 64-bit version.
 In the following screenshot, the 64-bit version is selected.

NOTE
If you use the 32-bit version of Power BI Desktop when creating very large data models, you might experience out-
of-memory issues.

Solution 2
Change the bit-version of Microsoft Office to match the bit-version of your Power BI Desktop installation:
1. Uninstall Microsoft Office
2. Install the version of Office that matches your Power BI Desktop installation.
Solution 3
If the error occurs when you attempt to open an .XLS file (an Excel 97-2003 workbook), you can avoid using the
Access Database Engine by opening the .XLS file in Excel, and saving it as an XLSX file.
Solution 4
If the previous three solutions are not feasible, it's possible to install both versions of the Access Database Engine.
However, this workaround isn't recommended. Although installing both versions will resolve this issue for Power
Query for Excel and Power BI Desktop, it will introduce errors and issues for any application that automatically (by
default) uses the bit-version of the Access Database Engine that was installed first.
To install both bit-versions of the Access Database Engine, follow these steps:
1. Install both bit-versions of the Access Database Engine from the download page.
2. Run each version of the Access Database Engine by using the /passive switch. For example:

c:\users\joe\downloads\AccessDatabaseEngine.exe /passive

c:\users\joe\downloads\AccessDatabaseEngine_x64.exe /passive

Situation 3: Trouble using Access or .XLS files with a Microsoft 365

subscription
If you're using a Microsoft 365 subscription, whether Office 2013 or Office 2016 , the Access Database Engine
provider is registered in a virtual registry location that's only accessible to Microsoft Office processes. As a result,
the Mashup Engine (which is responsible for running non-Office 365 Excel and Power BI Desktop, and isn't an
Office process), can't use the Access Database Engine provider.
To remedy this situation, download and install the Access Database Engine redistributable that matches the bit-
version of your Power BI Desktop installation. For more information about bit-versions, see the earlier sections in
this article.

Other situations that can cause import issues

We strive to cover as many issues that occur with Access or .XLS files as possible. If you encounter an issue that isn't
covered in this article, submit a question about the issue to Power BI Support. We regularly look at issues that may
be affecting many customers, and include them in our articles.
 Troubleshoot opening Power BI Desktop
9/9/2020 • 3 minutes to read • Edit Online

In Power BI Desktop, users who installed and are running previous versions of the Power BI On-premises data
gateway can be blocked from opening Power BI Desktop, because of administrative policy restrictions that the
Power BI on-premises gateway placed on named pipes on the local machine.

Resolve issues with the On-premises data gateway and Power BI

Desktop
You have three options to resolve the issue associated with the On-premises data gateway, and to enable Power BI
Desktop to open:
Resolution 1: Install the latest version of Power BI On-premises data gateway
The latest version of the Power BI On-premises data gateway doesn't place named pipe restrictions on the local
machine, and allows Power BI Desktop to open properly. If you need to continue using Power BI On-premises data
gateway, the recommended resolution is to update it. You can download the latest version of Power BI On-premises
data gateway. The link is a direct download link to the installation executable.
Resolution 2: Uninstall or stop the Power BI On-premises data gateway Microsoft service
You can uninstall the Power BI On-premises data gateway if you no longer need it. Or you can stop the Power BI
On-premises data gateway Microsoft service, which removes the policy restriction and allows Power BI Desktop to
open.
Resolution 3: Run Power BI Desktop with administrator privilege
You can instead successfully launch Power BI Desktop as administrator, which also allows Power BI Desktop to
successfully open. It's still recommended that you install the latest version of Power BI On-premises data gateway,
as described earlier.
Power BI Desktop is engineered as a multiprocess architecture, and several of these processes communicate using
Windows named pipes. There may be other processes that interfere with those named pipes. The most common
reason for such interference is security, including situations where antivirus software or firewalls may block the
pipes or redirect traffic to a specific port. Opening Power BI Desktop with administrator privilege may resolve that
issue. If you can't open with administrator privilege, ask your administrator to determine which security rules are
preventing named pipes from properly communicating. Then, add Power BI Desktop and its respective
subprocesses to allow lists.

Resolve issues when connecting to SQL Server

When you attempt to connect to a SQL Server database, you may come across an error message similar to the
following text:
"An error happened while reading data from the provider:
'Could not load file or assembly 'System.EnterpriseServices, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=xxxxxxxxxxxxx' or one of its dependencies.
Either a required impersonation level was not provided, or the provided impersonation level is invalid.
(Exception from HRESULT: 0x80070542)'"

You can often resolve the issue if you open Power BI Desktop as an administrator before you make the SQL Server
connection.
After you open Power BI Desktop as an administrator and establish the connection, the required DLLs are registered
properly. After that, opening Power BI Desktop as an administrator isn't necessary.

Get help with other launch issues

We strive to cover as many issues that occur with Power BI Desktop as possible. We regularly look at issues that
may be affecting many customers, and include them in our articles.
If the issue with opening Power BI Desktop isn't associated with the On-premises data gateway, or when the
previous resolutions don't work, you can submit a support incident to Power BI support
(https://support.powerbi.com) to help identify and solve your issue.
Should you come across other issues in the future with Power BI Desktop, it's helpful to turn on tracing and gather
log files. Log files may help to isolate and identify the issue. To turn on tracing, choose File > Options and
settings > Options , select Diagnostics , and then select Enable tracing . Power BI Desktop must be running to
set this option, but it's helpful for future issues associated with opening Power BI Desktop.
 Troubleshoot developing DirectQuery models in
Power BI Desktop
9/9/2020 • 6 minutes to read • Edit Online

This article targets data modelers developing Power BI DirectQuery models, developed by using either Power BI
Desktop or the Power BI service. It describes how to diagnose performance issues, and how to get more detailed
information to allow reports to be optimized.

Performance Analyzer
It's strongly recommended that any diagnosis of performance issues starts in Power BI Desktop, rather than in
Power BI (the service or Power BI Report Server). It's commonly the case that performance issues are simply based
on the level of performance of the underlying data source, and these are more easily identified and diagnosed in
the much more isolated environment of Power BI Desktop, and initially eliminates certain components (such as the
Power BI gateway). Only if the performance issues are found to not be present with Power BI Desktop should
investigation focus on the specifics of the report in Power BI. The Performance Analyzer is a useful tool for
identifying issues throughout this process.
Similarly, it is recommended to first try to isolate any issues to an individual visual, rather than many visuals on a
page.
Let's say those steps (in the previous paragraphs of this topic) have been taken—we now have a single visual on a
page in Power BI Desktop that is still sluggish. To determine what queries are being sent to the underlying source
by Power BI Desktop, you can use the Performance Analyzer. It's also possible to view traces/diagnostic information
that might be emitted by the underlying data source. Such traces might also contain useful information about the
details of how the query was executed, and how it can be improved.
Further, even in the absence of such traces from the source, it's possible to view the queries sent by Power BI, along
with their execution times, as described next.

Review trace files

By default, Power BI Desktop logs events during a given session to a trace file called FlightRecorderCurrent.trc .
For some DirectQuery sources, this log includes all queries sent to the underlying data source (the remaining
DirectQuery sources may be supported in the future). The sources that write queries to the log are the following:
SQL Server
Azure SQL Database
Azure SQL Data warehouse
Oracle
Teradata
SAP HANA
The trace file can be found in the AppData folder for the current user: \<User>\AppData\Local\Microsoft\Power BI
Desktop\AnalysisServicesWorkspaces
Here's an easy way to get to this folder: In Power BI Desktop select File > Options and settings > Options, and then
select the Diagnostics page. The following dialog window appears:
When you select the Open crash dump/traces folder link, under Crash Dump Collection, the following folder
opens: \<User>\AppData\Local\Microsoft\Power BI Desktop\Traces
Navigating to that folder's parent folder displays the folder containing AnalysisServicesWorkspaces, which will
contain one workspace subfolder for every open instance of Power BI Desktop. These subfolders are named with an
integer suffix, such as AnalysisServicesWorkspace2058279583.
Inside that folder is a \Data subfolder that contains the trace file FlightRecorderCurrent.trc for the current Power BI
session. The corresponding workspace folder is deleted when the associated Power BI Desktop session ends.
The trace files can be opened by using the SQL Server Profiler tool, which is available as a free download as part of
SQL Server Management Studio. You can get that from this location.
Once you download and install SQL Server Management Studio, run SQL Server Profiler.
To open the trace file, take the following steps:
1. In SQL Server Profiler, select File > Open > Trace file
2. Enter the path to the trace file for the currently open Power BI session, such as: \
<User>\AppData\Local\Microsoft\Power BI
Desktop\AnalysisServicesWorkspaces\AnalysisServicesWorkspace2058279583\Data
3. Open FlightRecorderCurrent.trc
All events from the current session are displayed. An annotated example is shown below, which highlights groups
of events. Each group has the following:
A Query Begin and Query End event, which represent the start and end of a DAX query generated by the UI (for
example, from a visual, or from populating a list of values in the filter UI)
One or more pairs of DirectQuery Begin and DirectQuery End events, which represent a query sent to the
underlying data source, as part of evaluating the DAX query
Note that multiple DAX queries can be executed in parallel, so events from different groups can be interleaved. The
value of the ActivityID can be used to determine which events belong to the same group.
Other columns of interest are as follows:
TextData: The textual detail of the event. For Query Begin/End events this will be the DAX query. For
DirectQuery Begin/End events, this will be the SQL query sent to the underlying source. The TextData value for
the currently selected event is also displayed in the region at the bottom.
EndTime: When the event completed.
Duration: The duration, in milliseconds, taken to execute the DAX or SQL query.
Error : Indicates if an error occurred, in which case the event is also displayed in red.
In the image above, some of the less interesting columns have been narrowed, to allow the interesting columns to
be seen more easily.
The recommended approach to capturing a trace to help diagnose a potential performance issue is the following:
Open a single Power BI Desktop session (to avoid the confusion of multiple workspace folders)
Perform the set of actions of interest in Power BI Desktop. Include a few additional actions beyond that, to
ensure that the events of interest are flushed into the trace file.
Open SQL Server Profiler and examine the trace, as described earlier. Remember that the trace file will be
deleted upon closing Power BI Desktop. Also, further actions in Power BI Desktop will not immediately appear—
the trace file should be closed and reopened to see the new events.
Keep individual sessions reasonably small (10 seconds of actions, not hundreds) to make it easier to interpret
the trace file (and because there is a limit on the size of the trace file, thus for long sessions there is a chance of
early events being dropped).

Understand queries sent to the source

The general format of queries generated and sent by Power BI Desktop use subqueries for each of the model tables
referenced, where the subquery is defined by the Power Query query. For example, assume the following TPC-DS
tables in a SQL Server relational database:
Consider the following visual and its configuration, noting that the SalesAmount measure is defined with the
following expression:

SalesAmount = SUMX(Web_Sales, [ws_sales_price] * [ws_quantity])

Refreshing that visual will result in the T-SQL query shown below the next paragraph. As you can tell, there are
three subqueries for the Web_Sales , Item , and Date_dim model tables. Each of these tables returns all the model
table columns, even though only four columns are actually referenced by the visual. These subqueries (they're
shaded) are exactly the definition of the Power Query queries. Use of subqueries in this manner has not been found
to impact performance, for the data sources so far supported for DirectQuery. Data sources like SQL Server
optimize away the references to unused columns.
One reason Power BI employs this pattern is because you can define a Power Query query to use a specific query
statement. So, it's used "as provided", without an attempt to rewrite it. Note that this patterns restricts using query
statements that use Common Table Expressions (CTEs) and stored procedures. These statements cannot be used in
subqueries.
Gateway performance
For information about troubleshooting gateway performance, read the Troubleshoot gateways - Power BI article.

Next steps
For more information about DirectQuery, check out the following resources:
Use DirectQuery in Power BI Desktop
DirectQuery models in Power BI Desktop
DirectQuery model guidance in Power BI Desktop
Questions? Try asking the Power BI Community
 Data types in Power BI Desktop
9/9/2020 • 10 minutes to read • Edit Online

This article describes data types supported in Power BI Desktop and Data Analysis Expressions (DAX).
When you load data into Power BI Desktop, it will attempt to convert the data type of the source column into a data
type that better supports more efficient storage, calculations, and data visualization. For example, if a column of
values you import from Excel has no fractional values, Power BI Desktop will convert the entire column of data to a
Whole Number data type, which is better suited for storing integers.
This concept is important because some DAX functions have special data type requirements. While in many cases
DAX will implicitly convert a data type for you, there are some cases where it will not. For instance, if a DAX
function requires a Date data type and the data type for your column is Text, the DAX function will not work
correctly. So, it’s both important and useful to get the correct data type for a column. Implicit conversions are
described later in this article.

Determine and specify a column’s data type

In Power BI Desktop, you can determine and specify a column’s data type in the Query Editor, or in Data View or
Report View:
Data types in Quer y Editor

Data types in Data View or Repor t View

The Data Type drop down in Query Editor has two data types not currently present in Data or Report View:
Date/Time/Timezone and Duration . When a column with these data types is loaded into the model and viewed
in Data or Report view, a column with a Date/Time/Timezone data type will be converted into a Date/Time, and a
column with a Duration data type is converted into a Decimal Number.
The Binar y data type is not currently supported outside of the Query Editor. Inside the Query Editor you can use it
when loading binary files if you convert it to other data types before loading it to the Power BI model. It exists in
the Data View and Report View menus for legacy reasons but if you try to load binary columns to the Power BI
model you may run into errors.
Number types
Power BI Desktop supports three number types:
Decimal Number – Represents a 64 bit (eight-byte) floating point number. It’s the most common number type
and corresponds to numbers as you usually think of them. Although designed to handle numbers with fractional
values, it also handles whole numbers. The Decimal Number type can handle negative values from -1.79E +308
through -2.23E -308, 0, and positive values from 2.23E -308 through 1.79E + 308. For example, numbers like 34,
34.01, and 34.000367063 are valid decimal numbers. The largest precision that can be represented in a Decimal
Number type is 15 digits long. The decimal separator can occur anywhere in the number. The Decimal Number
type corresponds to how Excel stores its numbers.
Fixed Decimal Number – Has a fixed location for the decimal separator. The decimal separator always has four
digits to its right and allows for 19 digits of significance. The largest value it can represent is
922,337,203,685,477.5807 (positive or negative). The Fixed Decimal Number type is useful in cases where
rounding might introduce errors. When you work with many numbers that have small fractional values, they can
sometimes accumulate and force a number to be slightly off. Since the values past the four digits to the right of
decimal separator are truncated, the Fixed Decimal type can help you avoid these kinds of errors. If you’re familiar
with SQL Server, this data type corresponds to SQL Server’s Decimal (19,4), or the Currency Data type in Power
Pivot.
Whole Number – Represents a 64 bit (eight-byte) integer value. Because it’s an integer, it has no digits to the right
of the decimal place. It allows for 19 digits; positive or negative whole numbers between -
9,223,372,036,854,775,807 (-2^63+1) and 9,223,372,036,854,775,806 (2^63-2). It can represent the largest
possible precision of the various numeric data types. As with the Fixed Decimal type, the Whole Number type can
be useful in cases where you need to control rounding.
 NOTE
The Power BI Desktop data model supports 64 bit integer values, but the largest number the visuals can safely express is
9,007,199,254,740,991 (2^53-1) due to JavaScript limitations. If you work with numbers in your data model above this, you
can reduce the size through calculations before adding them to a visual

Date/time types
Power BI Desktop supports five Date/Time data types in Query View. Both Date/Time/Timezone and Duration are
converted during load into the model. The Power BI Desktop data model only supports date/time, but they can be
formatted as dates or times independently.
Date/Time – Represents both a date and time value. Underneath the covers, the Date/Time value is stored as a
Decimal Number Type. So you can actually convert between the two. The time portion of a date is stored as a
fraction to whole multiples of 1/300 seconds (3.33 ms). Dates between years 1900 and 9999 are supported.
Date – Represents just a Date (no time portion). When converted into the model, a Date is the same as a
Date/Time value with zero for the fractional value.
Time – Represents just Time (no Date portion). When converted into the model, a Time value is the same as a
Date/Time value with no digits to the left of the decimal place.
Date/Time/Timezone – Represents a UTC Date/Time with a timezone offset. It’s converted into Date/Time when
loaded into the model. The Power BI model doesn't adjust the timezone based on a user's location or locale etc. If a
value of 09:00 is loaded into the model in the USA, it will display as 09:00 wherever the report is opened or
viewed.
Duration – Represents a length of time. It’s converted into a Decimal Number Type when loaded into the model.
As a Decimal Number type it can be added or subtracted from a Date/Time field with correct results. As a Decimal
Number type, you can easily use it in visualizations that show magnitude.
Text type
Text - A Unicode character data string. Can be strings, numbers, or dates represented in a text format. Maximum
string length is 268,435,456 Unicode characters (256 mega characters) or 536,870,912 bytes.
True/false type
True/False – A Boolean value of either a True or False.
Blanks/nulls type
Blank - Is a data type in DAX that represents and replaces SQL nulls. You can create a blank by using the BLANK
function, and test for blanks by using the ISBLANK logical function.
Binary data type
The Binary data type can be used to represent any other data with a binary format. Inside the Query Editor, you can
use it when loading binary files if you convert it to other data types before loading it to the Power BI model. Binary
columns aren't supported in the Power BI data model. It exists in the Data View and Report View menus for legacy
reasons but if you try to load binary columns to the Power BI model you may run into errors.

NOTE
If a binary column is in the output of the steps of a query, attempting to refresh the data through a gateway can cause
errors. It's recommended that you explicitly remove any binary columns as the last step in your queries.

Table data type

DAX uses a table data type in many functions, such as aggregations and time intelligence calculations. Some
functions require a reference to a table; other functions return a table that can then be used as input to other
functions. In some functions that require a table as input, you can specify an expression that evaluates to a table;
for some functions, a reference to a base table is required. For information about the requirements of specific
functions, see DAX Function Reference.

Implicit and explicit data type conversion in DAX formulas

Each DAX function has specific requirements as to the types of data that are used as inputs and outputs. For
example, some functions require integers for some arguments and dates for others; other functions require text or
tables.
If the data in the column you specify as an argument is incompatible with the data type required by the function,
DAX in many cases will return an error. However, wherever possible DAX will attempt to implicitly convert the data
to the required data type. For example:
You can type a date as a string, and DAX will parse the string and attempt to cast it as one of the Windows date
and time formats.
You can add TRUE + 1 and get the result 2, because TRUE is implicitly converted to the number 1 and the
operation 1+1 is performed.
If you add values in two columns, and one value happens to be represented as text ("12") and the other as a
number (12), DAX implicitly converts the string to a number and then does the addition for a numeric result.
The following expression returns 44: = "22" + 22.
If you attempt to concatenate two numbers, Excel will present them as strings and then concatenate. The
following expression returns "1234": = 12 & 34.
Table of implicit data conversions
The type of conversion that is performed is determined by the operator, which casts the values it requires before
performing the requested operation. These tables list the operators, and indicate the conversion that is performed
on each data type in the column when it is paired with the data type in the intersecting row.

NOTE
Text data types are not included in these tables. When a number is represented as in a text format, in some cases Power BI
will attempt to determine the number type and represent it as a number.

Addition (+)

O P ERATO R( +) IN T EGER C URREN C Y REA L DAT E/ T IM E

INTEGER INTEGER CURRENCY REAL Date/time

CURRENCY CURRENCY CURRENCY REAL Date/time

REAL REAL REAL REAL Date/time

Date/time Date/time Date/time Date/time Date/time

For example, if a real number is used in an addition operation in combination with currency data, both values are
converted to REAL, and the result is returned as REAL.
Subtraction (-)
In the following table, the row header is the minuend (left side) and the column header is the subtrahend (right
side).
 O P ERATO R( - ) IN T EGER C URREN C Y REA L DAT E/ T IM E

INTEGER INTEGER CURRENCY REAL REAL

CURRENCY CURRENCY CURRENCY REAL REAL

REAL REAL REAL REAL REAL

Date/time Date/time Date/time Date/time Date/time

For example, if a date is used in a subtraction operation with any other data type, both values are converted to
dates, and the return value is also a date.

NOTE
Data models also support the unary operator, - (negative), but this operator does not change the data type of the operand.

Multiplication (*)

O P ERATO R( *) IN T EGER C URREN C Y REA L DAT E/ T IM E

INTEGER INTEGER CURRENCY REAL INTEGER

CURRENCY CURRENCY REAL CURRENCY CURRENCY

REAL REAL CURRENCY REAL REAL

For example, if an integer is combined with a real number in a multiplication operation, both numbers are
converted to real numbers, and the return value is also REAL.
Division (/)
In the following table, the row header is the numerator and the column header is the denominator.

O P ERATO R( / )
( RO W / C O L UM N ) IN T EGER C URREN C Y REA L DAT E/ T IM E

INTEGER REAL CURRENCY REAL REAL

CURRENCY CURRENCY REAL CURRENCY REAL

REAL REAL REAL REAL REAL

Date/time REAL REAL REAL REAL

For example, if an integer is combined with a currency value in a division operation, both values are converted to
real numbers, and the result is also a real number.
Comparison operators
In comparison expressions, Boolean values are considered greater than string values and string values are
considered greater than numeric or date/time values; numbers and date/time values are considered to have the
same rank. No implicit conversions are performed for Boolean or string values; BLANK or a blank value is
converted to 0/""/false depending on the data type of the other compared value.
The following DAX expressions illustrate this behavior:
=IF(FALSE()>"true","Expression is true", "Expression is false"), returns "Expression is true"
=IF("12">12,"Expression is true", "Expression is false"), returns "Expression is true"
=IF("12"=12,"Expression is true", "Expression is false"), returns "Expression is false"
Conversions are performed implicitly for numeric or date/time types as described in the following table:

C O M PA RISO N
O P ERATO R IN T EGER C URREN C Y REA L DAT E/ T IM E

INTEGER INTEGER CURRENCY REAL REAL

CURRENCY CURRENCY CURRENCY REAL REAL

REAL REAL REAL REAL REAL

Date/time REAL REAL REAL Date/Time

Handling blanks, empty strings, and zero values

In DAX, a null, blank value, empty cell, or a missing value is all represented by the same new value type, a BLANK.
You can also generate blanks by using the BLANK function, or test for blanks by using the ISBLANK function.
How blanks are handled in operations such as addition or concatenation depends on the individual function. The
following table summarizes the differences between DAX and Microsoft Excel formulas, in the way that blanks are
handled.

EXP RESSIO N DA X EXC EL

BLANK + BLANK BLANK 0(zero)

BLANK + 5 5 5

BLANK * 5 BLANK 0(zero)

5/BLANK Infinity Error

0/BLANK NaN Error

BLANK/BLANK BLANK Error

FALSE OR BLANK FALSE FALSE

FALSE AND BLANK FALSE FALSE

TRUE OR BLANK TRUE TRUE

TRUE AND BLANK FALSE TRUE

BLANK OR BLANK BLANK Error

BLANK AND BLANK BLANK Error

 Connector extensibility in Power BI
5/13/2020 • 2 minutes to read • Edit Online

Power BI can connect to data by using existing connectors and generic data sources, like ODBC, OData, OLE DB,
Web, CSV, XML, and JSON. Or, developers can enable new data sources with custom data extensions called custom
connectors. Some custom connectors are certified and distributed by Microsoft as certified connectors.
To use non-certified custom connectors that you or a third party have developed, you must adjust the Power BI
Desktop security settings to allow extensions to load without validation or warning. Because this code can handle
credentials, including sending them over HTTP, and ignore privacy levels, you should only use this security setting if
you absolutely trust your custom connectors.
Another option is for the developer to sign the connector with a certificate, and provide the information you need
to use it without changing your security settings. For more information, see About trusted third-party connectors.

Custom connectors
Non-certified custom connectors can range from small business-critical APIs to large industry-specific services that
Microsoft hasn't released a connector for. Many connectors are distributed by vendors. If you need a specific data
connector, contact the vendor.
To use a non-certified custom connector, put the connector .pq, .pqx, .m, or .mez file in the [Documents]\Power BI
Desktop\Custom Connectors folder. If the folder doesn't exist, create it.
Adjust the data extension security settings as follows:
In Power BI Desktop, select File > Options and settings > Options > Security .
Under Data Extensions , select (Not Recommended) Allow any extension to load without validation or
warning . Select OK , and then restart Power BI Desktop.
The default Power BI Desktop data extension security setting is (Recommended) Only allow Microsoft
cer tified and other trusted third-par ty extensions to load . With this setting, if there are non-certified
custom connectors on your system, the Uncer tified Connectors dialog box appears at Power BI Desktop startup,
listing the connectors that can't securely load.
To resolve the error, you can either change your Data Extensions security setting, or remove the uncertified
connectors from your Custom Connectors folder.

Certified connectors
A limited subset of data extensions is considered certified. While Microsoft distributes the connectors, it's not
responsible for their performance or continued function. The third-party developer who created the connector is
responsible for its maintenance and support.
In Power BI Desktop, certified third-party connectors appear in the list in the Get Data dialog box, along with
generic and common connectors. You don't need to adjust security settings to use the certified connectors.
If you would like a custom connector to be certified, ask your vendor to contact [email protected].
 Trusted third-party connectors
5/13/2020 • 2 minutes to read • Edit Online

Why do you need trusted third-party connectors?

In Power BI, we generally recommend keeping your 'Data extension security' level at the higher level, which
prevents loading of code not certified by Microsoft. However, there may be many cases in which you want to load
specific connectors--ones you've written, or ones provided to you by a consultant or vendor outside the Microsoft
certification path.
The developer of a given connector can sign it with a certificate and provide you with the information you need to
securely load it without lowering your security settings.
If you want to know more about the security settings, you can read about them here.

Using the registry to trust third-party connectors

Trusting third-party connectors in Power BI is done by listing the thumbprint of the certificate you want to trust in a
specified registry value. If this thumbprint matches the thumbprint of the certificate on the connector you want to
load, you will be able to load it in the ‘Recommended’ security level of Power BI.
The registry path is HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Power BI Desktop. Make sure the path
exists, or create it. We chose this location due to it being primarily controlled by IT policy, as well as requiring local
machine administration access to edit.

Add a new value under the path specified above. The type should be “Multi-String Value” (REG_MULTI_SZ), and it
should be called “TrustedCertificateThumbprints”
Add the thumbprints of the certificates you want to trust. You can add multiple certificates by using “\0” as a
delimiter, or in the registry editor, right click -> modify and put each thumbprint on a new line. Example thumbprint
is taken from a self-signed certificate.

If you’ve followed the instructions properly, and have been given the proper thumbprint by your developer, you
should now be able to securely trust connectors signed with the associated certificate.

How to Sign Connectors

If you have a connector you or a developer need to sign, you can read about it in the Power Query docs here.