Excel 2016 connect fails: InvalidVersionNumber: The EDMX version specified in the Version attribute does not match the version corresponding to the namespace of the Edmx element

[algo-web]

Excel 2016 connect fails: InvalidVersionNumber: The EDMX version specified in the Version attribute does not match the version corresponding to the namespace of the Edmx element

[kirill533]

Power BI was complaining about metadata:

InvalidVersionNumber : The EDMX version specified in the 'Version' attribute does not match the version corre sponding to the namespace of the 'Edmx' element. : (0, 0)

The problem was fixed after I modified the Version number in the edmx:Edmx tag from 3.0 to 1.0.

As it may be seen from examples, all samples below Odata 4.0 have edmx:Edmx tag with version 1.0:

• https://services.odata.org/V3/Northwind/Northwind.svc/$metadata
• https://services.odata.org/V3/OData/OData.svc/$metadata

Only sample of Odata v4 have it differently, but it also references different xmlns:edmx file:

• https://services.odata.org/V4/(S(ihhk0nudwyawubjpy1iucu5q))/TripPinServiceRW/$metadata

Same in ms docs: https://docs.microsoft.com/en-us/openspecs/windows_protocols/mc-edmx/44c78852-dd32-457b-a1ba-4f179bb00242

The fix needs to be applied in /src/MetadataV3/edmx/Edmx.php of ODataMetadata project:
Replacing
$this->setVersion($version);
with
$this->setVersion('4.0' == $version ? '4.0' : '1.0');

[c-harris]

With regards issues with json writers any help will be appricheated I have been meaning to make some major changes there

[kirill533]

With regards issues with json writers any help will be appricheated I have been meaning to make some major changes there

Yes, Json Writers are still not perfect. I have hard time to make integration with Power BI fully working for me. And it is super hard to figure out, why that does not work. Would be good to have some means to automatically test that, maybe, some kind of integration tests involving OData libraries from Microsoft (C#). Do you know maybe some OData clients that might be used for proper testing of the API?

P.S. Not sure about the right spot for such communication.

[c-harris]

I think that is a good idea, we could probably build a c# integration test lib against the Northwood examples and test from there. Would be happy to work towards it.

What so you mean right stop for such communication?

[kirill533]

What so you mean right stop for such communication?

Right "spot", sorry. "The right place".

[c-harris]

I probably agree I think the three simple options for us would be

1. you could create a new issue on podata?
2. you could shot me an email?
3. we use discord.

Any of those suite you? A 4th might be I have an old skype account