[null, {"document_url": "https://blog.gbrueckl.at/2014/03/", "unformatted_src": "http://files.gbrueckl.at/blog/6e2cb36d40fb_EA3B/MultipleRoles_multidimensional_thumb.jpg", "src": "http://files.gbrueckl.at/blog/6e2cb36d40fb_EA3B/MultipleRoles_multidimensional_thumb.jpg", "formatted_filename": "MultipleRoles multidimensional thumb", "alt_text": "MultipleRoles_multidimensional", "rendered_width": 609, "rendered_height": 100}, null, null, {"document_url": "https://blog.gbrueckl.at/2014/03/", "unformatted_src": "http://files.gbrueckl.at/blog/6e2cb36d40fb_EA3B/MultipleRoles_tabular_thumb.jpg", "src": "http://files.gbrueckl.at/blog/6e2cb36d40fb_EA3B/MultipleRoles_tabular_thumb.jpg", "formatted_filename": "MultipleRoles tabular thumb", "alt_text": "MultipleRoles_tabular", "rendered_width": 609, "rendered_height": 100}, null, {"document_url": "https://blog.gbrueckl.at/2014/03/", "unformatted_src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/Refresh_Error_thumb.jpg", "src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/Refresh_Error_thumb.jpg", "formatted_filename": "Refresh Error thumb", "alt_text": "Refresh_Error", "rendered_width": 1028, "rendered_height": 208}, null, null, {"document_url": "https://blog.gbrueckl.at/2014/03/", "unformatted_src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/OData_Authentication_thumb.jpg", "src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/OData_Authentication_thumb.jpg", "formatted_filename": "OData Authentication thumb", "alt_text": "OData_Authentication", "rendered_width": 506, "rendered_height": 560}, null, {"document_url": "https://blog.gbrueckl.at/2014/03/", "unformatted_src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/Refresh_Success_thumb.jpg", "src": "http://files.gbrueckl.at/blog/Scheduled-Data-Refresh-of-OData-Sources-_91F0/Refresh_Success_thumb.jpg", "formatted_filename": "Refresh Success thumb", "alt_text": "Refresh_Success", "rendered_width": 1028, "rendered_height": 156}, null, null, null, null, null]


UPDATE: Part 2 can be found here




With the recent public release of Power BI it is finally possible to refresh Power Pivot workbooks online.Once a workbook is uploaded to SharePoint online and “Enabled” for Power BI you can schedule an automatic data refresh for the Power Pivot model. Though, at the moment only a very limit number of data sources are supported:

Especially for public available data OData feeds are very popular, for example from Wikipedia. Those public data feeds usually do not require any authentication so one would expect these data sources to work flawless with a scheduled data refresh of Power BI. Well, you are wrong here!
When you create a simple Power Pivot model with one OData source to e.g. Wikipedia, publish it and setup scheduled data refresh you will receive the following error: The error message itself does not reveal any insights on the actual error. If you are in the (more or less) lucky situation that you are also owner of that site you can go to the Power BI Admin Center to get some further details on the error: By downloading the CSV or hovering over a single Message you can see the details:

It says that for my user no corresponding data source exists or I do not have permissions to access it.

In our case the reason is that our user is unauthorized – the actually data source that was used must not necessarily exist in the user’s data sources (Those can be found via “My Power BI”) for scheduled data refresh to work.

So you will ask yourself what could go possibly wrong here as you are just accessing a public OData feed?!?
The reason is that in the connection string the “Integrated Security”-property is set to SSPI by default. In your local Excel/Power Pivot model this works just fine as the SSPI context can be resolved and sent to the OData feed. Sure the OData feed actually ignores this information as it is public but from an authentication point of view everything works correctly!

The problem with Scheduled Data Refresh is that SSPI simply does not work as it cannot be resolved and Power BI cannot use any service user for your request if SSPI is defined. The first thing that comes to your mind would be to simply set the authentication method to “Anonymous” which would be perfectly fine for a public data feed. However, Power Pivot does not support Anonymous authentication for OData sources: As SSPI does not work we need to use “Basic” here and provide “User ID” and “Password”. Which UserID/Password you may ask? – and the simple answer is: “It does not matter!”
You can provide any values here, in my case I used “random” for both, User ID and Password! Another thing you need to ensure is that “Persist Securtiy Info” is set to True so your “Password” is stored in the final connection string making Power BI think that authentication is defined correctly within the connection string and Power BI does not have to do anything.

Once you changes those settings your data refresh will work like a charm: On last thing you may realize is the “Running Time”. It takes significantly longer when doing the refresh in Power BI opposed to doing the refresh locally. Just keep that in mind, especially for bigger data feeds.

In the future I hope that Microsoft will introduce some kind of “Anonymous” authentication within the dropdown of Power Pivot or simply check at some point if the OData feed requires any authentication at all hence overwriting the authentication mode specified in the connection string when refreshing.




 Gerhard Brueckl

Data professional
SSAS Maestro Follow via LinkedIn





