Common Data Service (CDS) Error

[Anonymous]

Hi,

Trying to connect Power BI to Dynamics 365 Online via the CDS connector. When I navigate to the entity that I want (Opportunities) the data is correctly loaded into Power BI. However, when I go to Edit Queries -> Power Query Editor I am getting the following error:

DataSource.Error: Cds: Request failed: Unable to connect to the remote server

Details:

DataSourceKind=Cds

DataSourcePath=https://MYCRMXXXX.dynamics.com 

Other smaller entities are loading fine & I can edit them in Power Query.

Does anyone have any ideas how to get around this?

Thanks, RM1234

[v-piga-msft]

Hi @Anonymous ,

By my tests with the latest version of power bi desktop, I could get data from Dynamics 365 Online via the CDS connector successfully.

Based on the error message, you'd better have a check of the data source again and if the remote server works well.

Best Regards,

Cherry

[Anonymous]

Hi @v-piga-msft , 

Thanks for that. However, I can get the connection to work on smaller tables & edit the data. When I try to edit my main (larger) tables the errors are occuring and I cannot edit/transform the data in the Power Query editor. 

Any help would be appreciated!

Thanks 

[v-piga-msft]

Hi @Anonymous ,

Do you get the error when get data or load the data in query editor?

If it is convenient, could you share the screenshot of your error message?

Best  Regards,

Cherry

[Anonymous]

Hi @v-piga-msft, 

I can successfully load the entities data into Power BI from the Dynamics CRM via CDS. 

The error occurs when I try to open the data in the query editor. 

Unfortunately, I cant upload a screenshot of the error because it is happening on a system that is locked down. 

However, this is what it says: 

DataSource.Error: Cds: Request failed: Unable to connect to the remote server

Details: 

    DataSourceKind=Cds

    DataSourcePath=https://CRMSite

When I open smaller entities the data can be opened in the query editor. It is the larger entities that are causing the errors.

Do you think it could be something to do with a timeout? 

Thanks

[Anonymous]

Hi, has anyone seen this error before? 

Thanks