-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Adding OData Connected Service to the project failed: Unable to cast object of type 'Microsoft.OData.Edm.Library.AmbiguousTypeBinding' to type 'Microsoft.OData.Edm.IEdmCollectionType'." #75
Comments
I am experiencing exactly the same problem. Has anyone found a solution for this? |
Any news? -- This is kind of a blocking bug that is preventing folks from using the tool. |
Any updates on this? it is affecting us to generate proxy for consuming D365 for operation Odata endpoints. |
I also have same problem. |
Is there any solution for this error.? As one of the way to create a file and reference to that file doesn't work. there is reference among the entities so we cannot identify what to remove and what to keep. |
Hi All, Even I`m getting the same error message. Please provide a solution for this. Regards, |
There is a code delta between the Connected Services extension and the actively developed Client Code Gen extension; the state of the Connected Services extension is under review. A workaround for now is to use the Client Code Gen extension to help generate the proxy code against https://graph.microsoft.com/beta/$metadata. One can accomplish this by installing the extension from above and then
Also attached my generated file. |
Now it works great in Unchase OData ConnectedService v.1.1.2. Check it. |
Using the Add-in with VS2017 -- trying to add a connected OData service for the beta version of Microsoft Graph (https://graph.microsoft.com/beta/$metadata), and I end up with this:
Trying to do it with T4 templates gives the same error.
The text was updated successfully, but these errors were encountered: