Forum Discussion
Advocate IIOn-premises data gateway OData OAuth2
hi jeppesal,
Thanks for taking the time to walk thru the scenario and sorry to hear your frustration, hopefully we can get this resovled and get your dataset refreshing.
Few corrections to the statements made below:- Both the personal and enterprise gateway are PRO features and cannot be used with a free account. Are you seeing anything different?
- You can use the enterprise gateway to run your OData data source, but the limitation is the gateway doesn't support oAuth. So you will have to either use a different auth type, or seperate the 2 data sources into 2 datasets.
- The reason why the online data sources have to go thru the gateway is to keep your on-prem data secure, esp when you have mashup scenarios
Finally we acknowledge the auth types gap between the PBI desktop and using it in the service and we're working on addressing them soon in later releases.
Thanks,
Dimah
Advocate IIHi Lydia
I had a model that has a Project Online OData source using OAuth2. The customer would like to add on-prem SQL Server data to that model. I installed the on-prem gateway and that worked fine for the new SQL source but now my OData source didnt work. It kept saying that it couldnt fint the source in the gateway. After some research I found that I had to add the online sources under "Manage gateway" - see screenshot (sorry it is in Danish).
This is way have the impression that on-prem supports online sources.
But you are telling me that if I whant to combine online sources with on prem I have to use personal gateway (a PRO feature)?
It seems very backwards that the enterprise oriented gateway is free at doesnt support online sources with OAuth2, but the PRO personal gateway does?
Again, in my mind this is not af nice-to-have feature, this is a need-to-have for a enterprise tool. A lot if IT departments are not very kean on installing user dependant gateways without any deasent administration.
BR
Jeppe
Microsoft Employeehi jeppesal,
Thanks for taking the time to walk thru the scenario and sorry to hear your frustration, hopefully we can get this resovled and get your dataset refreshing.
Few corrections to the statements made below:
- Both the personal and enterprise gateway are PRO features and cannot be used with a free account. Are you seeing anything different?
- You can use the enterprise gateway to run your OData data source, but the limitation is the gateway doesn't support oAuth. So you will have to either use a different auth type, or seperate the 2 data sources into 2 datasets.
- The reason why the online data sources have to go thru the gateway is to keep your on-prem data secure, esp when you have mashup scenarios
Finally we acknowledge the auth types gap between the PBI desktop and using it in the service and we're working on addressing them soon in later releases.
Thanks,
Dimah
- jeppesal
Hi Dimah,
Thank you for your answer/comment.
I think mashup scenarios are very common and a feature where PBI shines (if the Gateway gap is fixed). For us consultants and PBI developers it’s the small gaps that causes frustration and makes implementation of PBI difficult.
In my case, I had a great project with some bye in from IT. Then the need for on-prem source came and I persuaded IT to create a VM and allow for Data Gateway. BUT the gap in features meant a long process of debugging, fixing (with the Personal Gateway) and new argumentation and approval for a second gateway (the name Personal isn’t the best for getting approved by IT).
I love PBI but you must focus on bridging the gaps and start thinking in real-life scenarios instead of what marketing wants. I don’t care about Apple-Watch support if my updates keep failing and I have to maneuver between the Desktop world and the Online world as two different worlds with different features.
Another topic is the collaboration part, again and again I find myself explaining how this works with multiple reports on the same dataset – yes you can create reports in Desktop (best experience) but only one etc. etc. I really hope the product team will rethink how the Desktop and Online PBI works together and bridge the gaps.
Regards
Jeppe
- dimazaid
Thanks, Jeppe for the great feedback.
As I mentioned we're working on bridging these gaps between PBI Desktop and PBI service. We appreciate your commitment to using Power BI and looking forward to getting you to a seemless experience with both collaberation and refresh.Thanks!
DimahWhat is the work around until this issue is fixed?
I'm connecting to a Dynamics 365 datasource (only OAUTH as far as I know) and some on premise ODATA sources.
I can't figure out how to get this working in the mean time.
Dimah,
this reply is by way of a vote up to get this issue resolved. We also have mashups between on premise SQL datasets and Sharepoint online lists (accessed via OData) and the mismatch between PBIDesktop authorisation versus PBI portal authorisation is a source of much frustration.
David
Is this going to be fixed soon. I cant do on premise gateway to odata due to organizational login and Azure data due to mashup. Please Fix ASAP unless Im missing something.
This was two years ago, any progress? The reason I ask is that whenever a SharePoint source is involved, we see "Edit Credentials" and when we do, it fails even if we put Domain\UserID. We use Windows Auth and have tried a Web Conector for Excel files, Excel (which doesn't exist on the Gateway list), SP Online List, and SharePoint Lists. These are in a Mash-up with DB sources like Hana. I suspect it is using the Email address to try an login to our Internal SharePoint instead of the Domain\UserID, how can I tell?
So, how does separating them into separate Datasets help?
Jon
