Odata Error: The Feed's metadata document appears to be invalid

[rstov3r]

I am having this issue using both Power BI and Power Query in Excel. I am not getting this error with a similar connection using a regular connection in excel 

[Anonymous]

Hi rstov3r,

I just got it to work:

old = OData.Feed("https://d365_instance.api.crm3.dynamics.com/api/data/v8.2")
new = OData.Feed("https://d365_instance.api.crm3.dynamics.com/api/data/v9.0", null, [Implementation="2.0"])

this is what you need:

, null, [Implementation="2.0"]

8.2 or 9.0 seem to work after getting lots of metadata error messages! 🙂

[Anonymous]

Hi rstov3r,

I just got it to work:

old = OData.Feed("https://d365_instance.api.crm3.dynamics.com/api/data/v8.2")
new = OData.Feed("https://d365_instance.api.crm3.dynamics.com/api/data/v9.0", null, [Implementation="2.0"])

this is what you need:

, null, [Implementation="2.0"]

8.2 or 9.0 seem to work after getting lots of metadata error messages! 🙂

[pqian]

What's the OData endpoint?

[rstov3r]

I am sorry. I am new to this. You mean the URL? 

https://odata.enersight.net/Version1311e201-9f9b-4afa-9e97-20ef72c15026

[pqian]

I mean the URL you entered when you grab the feed.

That URL is guarded behind basic auth. So I'm not able to test it out. I wonder what happens when you do this in the browser:

https://odata.enersight.net/Version1311e201-9f9b-4afa-9e97-20ef72c15026/$metadata

If it's a valid end point, it needs to respond to this query with its CSDL. Similar to this:

http://services.odata.org/northwind/northwind.svc/$metadata

If it doesn't, then you may not have the right end point address. 

[rstov3r]

Nothing happens when I add /$metadata to the end of that URL nothing happens. When I remove that tag and put in my basic auth, I get the following:

[pqian]

Can you post the response of the following URL

 https://odata.enersight.net/Version1311e201-9f9b-4afa-9e97-20ef72c15026/?$format=json
 

[rstov3r]

Same as the above response

[pqian]

@rstov3r, the response should be a JSON format string.

Looks like your target end point uses a custom OData implementation, and they did not follow the contract fully. Can you contact them and ask them about their $metadata implementation?