Support update from Odata Connected Service

[unchase]

Support update from Odata Connected Service

[unchase]

Did you create the file with Unchase Odata Connected Service or with Odata Connected Service by Microsoft?
Can you re-generate the specification file (by creating it again) and try to update it?

[marcioafoliveira]

OData Connected Service by Microsoft

[unchase]

My service cannot update the client-code created by the OData Connected Service by Microsoft, because they have different productId (providerId) of the Connected service.
Instead, you can re-generate the code from an existing json-specification URI using my service, and then update it when required.

But I will see if I can somehow to solve this issue.

[marciooliveiraprimaverabss]

updates?

[unchase]

Hi, @marcioafoliveira.

It will be ready in the next release.

[unchase]

Fixed in v1.3.0.

[unchase]

Why do you need the ability to update client code with an unsupported Connected Service by Microsoft when you can generate it using the Unchase OData Connected Service, and update it later when you like?
The generated code will not differ so much that compatibility is broken.

I added a button so that you can load similar data from a json-file to generate client code.

[HASSEN-MEDDEB-ATOS]

Hello,

I have issue OrgContext not generatd in reference.cs, can anyone help me please

Cordially