[Announcement] ODataLib 6.8.1 Release

We are happy to announce that the ODataLib 6.8.1 is released. Detailed release notes are listed below.

Bug Fix

  • [Github issues #3] Fix a bug that string function parameters containing specific characters were handled incorrectly by URI parser.

  • Fix a bug that OData Client for .NET failed to serialize and materialize null value in collection of complex type, primitive type.

New Features

  • OData Client for .NET now supports Edm.TimeOfDay/Edm.Date.

  • OData Client for .NET now can take entity or collection of entity as parameter of action.


Call to Action

You and your team are highly welcomed to try out this new version if you are interested in the new features and fixes above. For any feature request, issue or idea please feel free to reach out to us atodatafeedback@microsoft.com.


Comments (9)

  1. Raffaele Rialdi [MVP] says:

    the feedback email is broken

  2. yep its broken ! says:

    Your message can't be delivered because delivery to this address is restricted to authenticated Sender.

    For more information about this issue see DSN code 5.7.12 in Exchange Online.

  3. Hi Raffaele and "yep its broken",

    You are right. It's broken. I noticed that we haven't received anything since 10/10 two days ago and I thought it's because an internal distribution list wrapped by this email is broken so I made some adjustment accordingly. Now it seems that the problem lays more than that. I'll try to find out the fix soon.



  4. Vagif Abilov says:

    I guess you are aware of this, but this version still fails reading metadata with Enum annotations, as can be demonstrated with sample TripPin service: http://services.odata.org/V4/(S(qhpkrsgkpu3kgvye04smnpah))/TripPinServiceRW/$metadata

    This failure causes other packages that depends on ODataLib to explicitly restrict the version of ODataLib to 6.7.0 (that works fine). Quite unconvenient.

  5. Hi Raffaele and "yep its broken",

    The feedback mail is fixed.



  6. @Vagif

    Very glad that you give such quick feedback. I'll forward this report to the team. Besides, I'd recommend you open a Github issue at our issue tracker next time you find any bug: github.com/…/issues. We'll start monitoring this issue tracker and regard it as the major bug report channel. In fact, I'd recommend you also open an issue for this problem you report, so that you can monitor our fixing progress easily.



  7. @Vagif

    The problem you reported is an issue of the TripPin service implementation. The 6.8.0 library fixed the support for the constant expression edm:EnumMember. The version lower than 6.8.0 produces edm:EnumMemberReference on the server side, which is specified in V3. V4 changed the name of it to edm:EnumMember. The TripPin sample service, on the other hand, hasn't been upgraded to use 6.8.0 or above. Thus it still produce edm:EnumMemberReference as Enum annotations. We'll fix this problem in the TripPin service so that you can use it to test ODataLib version 6.8.0 and beyond.

  8. Vagif Abilov says:


    Thank you very much for the response. It explains the problem with TripPin service and ODataLib. I'd love to see this service updated ASAP, because it is published as a reference service on the odata.org site and developers like myself use it to better understand and test our code. So it is really misleading if it fails on the client side due to the incorrect server side code.

  9. Khiraling says:

    I'm getting below error

    Running transformation: System.Net.WebException: Failed to access the metadata document. The OData service requires authentication for accessing it. Please download the metadata, store it into a local file, and set the value of “MetadataDocumentUri” in the .odata.config file to the file path. After that, run custom tool again to generate the OData Client code

    also *.odata.config is not getting generated.

    Can someone point me what could be the issue.



Skip to main content