Anyone successfully add a connection to Microsoft Dynamics AX (7)?

I am not sure that Dynamics AX exposed OData endpoints include the required ...\svc endpoint. All I can find are the endpoints they talk about, including the data entity endpoint: ...\data. However, the resulting description looks like:
<img src="null" /><ODataServiceDocument xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Microsoft.OData.Core">
<EntitySets>
<ODataEntitySetInfo>
<Name>MCRSearchParameters</Name>
<Title i:nil="true"/>
<Url>MCRSearchParameters</Url>
</ODataEntitySetInfo>
<ODataEntitySetInfo>
<Name>ExciseTaxRegistrationNumbers</Name>
<Title i:nil="true"/>
<Url>ExciseTaxRegistrationNumbers</Url>
</ODataEntitySetInfo>
...
The header indicates "ODataServiceDocument" not "ODataService". It appears to try to process the file, but then I get the error:
https://.../data (Error: Exception - Cannot compile typed context: Unexpected error writing metadata to file 'c:\Users\rsonntag\AppData\Local\Temp\LINQPad5\_dodgbqgi\TypedDataContext_cqzmqc.dll' -- 'No logical space left to create more user strings.' (line 0))

Since AX OData is a LARGE result, I have no idea if LINQPad is just simply running out of memory, or, what?

I also tested using the OData 3 driver and it just has a 'Relationship missing' error so I figured AX was OData 4.

Comments

  • what is the fix you did for this error "No logical space left to create more user strings." i am also facing same, while consuming odata entity from .net client
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!