Forum Discussion
Can't connect to Power Apps Common Data Service??
Advocate IIStill no availability and it's a year later since they said "they are proud to announce availability". The latest Power BI update also has Common Data Service for Apps as a beta connector but zero information on how to use it. Any and all server URL's I tried end up saying the address does not point to a database.
The standard Common Data Service connector has gone back to the "Not available in your Region" (USA) message.
This is getting very frustrating because it's been a year since they announced it first and we have multiple CDS datasets behind Apps that we are currently in parallel maintaining in a seperate DB since we can't just use that data in Power BI.
I successfully managed to connect to that Service Yesterday and, it did exposes all the entities within the CDS Model. In the Server URL, I used the dynamic.crm URL.
- sxt173
edit: I should note we're not running Dynamics 365 yet so I'm unclear what the dynamics.crm would be if I just have a Entity in a CDS and an App running on top of it.
How? As in where do you get the Server Url? When I try something like https://web.powerapps.com/environments/_____________/entities (with the _____ being the identifier) I get the following view:
"OData: The given URL neither points to an OData service or a feed:". Do I use the actual App url which also didn't work?
Note I'm trying to use the "Common Data Service for Apps (Beta)" connector since the "Common Data Service (Beta)" is giving me the not availabe in region message.
On that front I do not have a "Enable" button that some other were seeing a year ago:
- tommy_g
Helper V
I suspect they made significant changes to the product / service, and then abandoned the early 2017 promise. With the recent big splash on the new, expanded CDM with two distinct CDS channels (one for apps, one for analytics) that we are just going to have to wait until the Analytics branch becomes available. Based on the latest updates, it looks like Q3 2018 as the earliest.
I my case this is a moot issue, while CDM is an appealing simplification of data access and integration, it's reallly most useful in the context of D365. We have already made strategic product plans to use plain-old SQL, in this case Azure SQL DB + Azure Analysis Services. At scale, this is far more flexible and economical than what CDM provides.
Overall, the Power BI team has done so many wonders at such a rapid cadence, with almost NO regresssions, I have no complaint. Nobody's perfect.
The 'Common Data Service for Apps Connection' links to the Dynamics Instance If you are using CDS 2 and Model Apps. That does not mean that you have Dynmics 365 Deployed.
I believe the 'Common Data Service' connection only now links to your default Instance of CDS which in my case has not been updated to CDS 2.
Any of my new Environments using CDS 2 can be linked to using the Apps Connection Model.
- sxt173
Solved: (I'm not certain this is the same across all deployments) the Server Url is https://xxxxxxxxx.crm.dynamics.com/ where the "xxx" is the unique Environment ID that you are given in a CDS v2 environment.
Thanks for the info. I spent (what seemed way too long) to transfer my entities and apps to a new CDS v2 environment. It seems the import/export is not fully functional but that is to be expected.
So I'm still lost as to what Url I input in Power BI when on this screen. The App URL does not give me anything so is there a server address that I'm totally missing?
