Forum Discussion
OData authentication to Power BI Report Server shared dataset
Anonymous wrote:
Has anyone found a fix to this problem? I am running into an exact same issue while using OData feel to access Azure DevOps data. The connection works from Power BI Desktop but doesn't when I publish this report to Power BI Report Server (on-premise) and update the same credentials on Data Source tab of the Power BI Report.
Unfortunately this is not the same issue. Power BI Report Server does not currently support doing scheduled refresh against any sources which require OAuth for authentication (like DevOps or Sharepoint Online). These sources work in Desktop (which knows how to handle OAuth) but not for scheduled refresh. The only options are to either manually refresh the data using Desktop - which is not great. Or to use a script or process to copy the data to some location that Power BI Report Server supports for scheduled refresh (like a local SQL instance or a network file share).
Agree it is not an exact same issue. Please read my text as "exact same error message".
This link (https://docs.microsoft.com/en-us/power-bi/report-server/data-sources) says:
Power BI reports can connect to a number of data sources. Depending on how data is used, different data sources are available. Data can be imported or data can be queried directly using DirectQuery or a live connection to SQL Server Analysis Services. Some data sources are available in Power BI Desktop optimized for Power BI Report Server, but aren't supported when published to Power BI Report Server.
These data sources are specific to Power BI reports used within Power BI Report Server. For information about data sources supported with paginated reports (.rdl), see Data Sources Supported by Reporting Services.
List of supported data sources
Data sourceCached dataScheduled refreshLive/DirectQuery
...
...
| OData Feed | Yes | Yes | No |
This documentation clearly mentions that Scheduled Refreshes are supported for OData Feed and that is what I am using with-in a PBIX files (not an RDL file). More over, the "Data sources" tab of this report, published to PBIRS, is enabled (in contrast with using a Azure DevOps Connector (Beta), where this tab was disabled on PBIRS) and it correctly lists the "Type" of the data source as OData in "Type" dropdown (a non-functional dropdown). That makes me think that it is implied that OData is supported on PBIRS.
So, not sure where the problem lies.
- d_gosbell5 years ago
Super User
Anonymous wrote:
These data sources are specific to Power BI reports used within Power BI Report Server. For information about data sources supported with paginated reports (.rdl), see Data Sources Supported by Reporting Services.
of the data source as OData in "Type" dropdown (a non-functional dropdown). That makes me think that it is implied that OData is supported on PBIRS.
Yep, I'm more than familiar with that page, it's the one you linked in your initial response so I did not bother re-linking to it. Unfortunately it does not list the authentication types supported by PBIRS
Anonymous wrote:
This documentation clearly mentions that Scheduled Refreshes are supported for OData Feed and that is what I am using with-in a PBIX files (not an RDL file).
The problem is that OData is a protocol not a specific source. It can be implemented in different ways and the spec does not mandate any specific authentication method. You will find that OData sources that use anonymous or windows auth work fine (http basic auth may work too but I have not tried that).
Sharepoint Online Lists for example use OData as their underlying protocol, but like DevOps they use OAuth for authentication (which Power BI shows as "Organizational Accout").
However I just had a look at the DevOps documentation here https://docs.microsoft.com/en-us/azure/devops/report/powerbi/client-authentication-options?view=azure-devops and it talks about the fact that you can use basic authentication or a personal access token - have you tried using either of those options for authentication or are you using the "Organizational Account" option? You may find that setting up basic auth (which I think you will have to change in Desktop) might allow this to work.
- Anonymous5 years agoNot applicable
Giving Basic Authentication a try is on my list. And yes, as you pointed out, and as remembered from Azure DevOps Connector, it requires an Organizational Account option for authentication. However, this option does not show-up as an available authentication method for OData.
Will let the thread know if Basic Authentication worked or not (subject to my Org Security Team being fine enable it.)