OData
Create and consume RESTful APIs in a simple and standard way
Latest posts
![[Tutorial & Sample] How to Use Open Type in OData](https://devblogs.microsoft.com/odata/wp-content/uploads/sites/23/2019/02/ODataLogo-150.png)
[Tutorial & Sample] How to Use Open Type in OData
![Liang Wang [MSFT]](https://devblogs.microsoft.com/odata/wp-content/uploads/sites/23/letter-avatar/5fd98d070a18b3b602dbeb464baf78ed.svg){kind=avatar}
OData protocol introduces conception of open type which allows clients to add properties dynamically to instances of the type by specifying uniquely named values in the payload used to insert or update an instance of the type. This makes definition of entity type or complex type more flexible. Developers do not have to define everything which is probably used in the edm model. Server Side 1. Model Definition It is quite easy to define an open entity type or open complex type in server side. If a server uses CSDL file to define the data model, only adding an attribute OpenType="true" to the node of the...
[Announcement] ODataLib 6.2.0 release
We are happy to announce that the ODL 6.2.0 is released and available on nuget along with the source code on codeplex (please read the git history for the v6.2.0 code info and allprevious version). Detailed release notes are listed below. Bug fixes Fixed a bug for parsing $it in UriParser. Improved the JSON serialization performance for unindented format. New Features Known Issues 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 t...
[Tutorial & Sample] Client Property Tracking for PATCH
In OData Client for .NET 6.2.0, we enabled the top level property tracking on client side when sending a PATCH. This feature allows client to send only updated properties, instead of the entire object to server. The top level property tracking means the client will only track the highest level properties in the class hierarchy. In other words, if customer is updating a property under a complex type property, or an item in a collection property under an entity, the client will send the entire complex type property (including unchanged properties under the complex property) or the entire collection (in...
[Discussion] Future Direction of WCF Data Services
WCF Data Services Microsoft initially released WCF Data Services as an easy way to implement an OData service over queryable data sources. This made it very easy to expose a model backed by the Entity Framework as an OData Service, and included a data provider model for plugging in other types of queryable data sources. WCF Data Services abstracted away all of the details of HTTP, OData, and the various payload formats, and the data provider was responsible for executing the underlying queries and returning the raw results to be serialized in the appropriate format. This framework worked well for exposing a ...
[Announcement] ODataLib 6.1.0 release
Hi all, As our commitment in rolling out new functionality in the OData V4 protocol continuously, we are excited to announce that OData Core Libraries 6.1 has been released to NuGet. This release contains four packages, Core, EDM, Spatial and the .Net client. Call to Action If your team has an existing OData service or is considering adding an OData service, now is an excellent time to engage with us. In addition to building OData stacks, part of our charter is to help Microsoft align behind the OData protocol. If you need input on whether OData can do what your service needs to do, or input on wh...
[Announcement] OData core libraries now support OData v4
Hi all, We are tremendously excited to announce that we have released version 6.0.0 of the OData core libraries to NuGet on Jan 27th. This release is particularly noteworthy as it is the first production-ready releasewith support for OData v4, the newest version of the OData protocol. We had two primary goals for this release: We have achieved both of these goals and are now well positioned to continue adding support for v4 features. Stack Prioritization & Strategy Adjustment As you are probably aware, our team aligns with many teams inside and outside of Microsoft who are building OData services. T...
[Announcement] The ASP.NET Web API 2.2 for OData release and the OData Client Code Generator release
We are very excited to announce the availability of nightly builds on MyGet for ASP.NET Web API 2.2 for OData v4.0 along with OData Client Code Generator for writing OData v4 clients. The Web API 2.2 release is particularly noteworthy as it is the first Web API release with support for OData v4 with selected highly demanded features. For a summary of what’s new in OData v4.0, please visit What’s New in OData v4. What’s New in ASP.NET Web API 2.2 for OData v4.0 New features Where to get it It is now available at ASP.NET Web API 2.2 for OData v4.0 on MyGet. We recommend ve...
[Tutorial & Sample] Use Enumeration types in OData
Enumeration is a very common data type in various data models. Enumeration types are useful means to represent data that needs to support certain programmatic options (such as the ability to detect one or more options are selected). OData v4 now supports Enumeration types, along with Primitive types, Complex types, and Entity types. And we expect there will be heavy usage of them. Let’s look at an example. Suppose we have an entity type called Product, and we want to have a property member that stores the color of the product. We could use a string type property, but an enumeration type property would look bet...
[Tutorial & Sample] Using Parameter Alias to simplify the OData URL
Are you suffering from typing complex parameter values in URL? Or even make it worse you need to type it more than once? To solve this problem, now Microsoft.OData.Core.dll 6.0 supports parameter alias in request URL， such as: ~/People?$filter=LastName eq @name and contains(Description, @name)&@name=’Bob’ It is implemented by introducing a new class: ParameterAliasNode and its base class is SingleValueNode. The alias (@name) is parsed into a ParameterAliasNode. Note: This blog assumes that you have writing ODL server side code experience. But how to leverage this feature? Just 3 steps: 1. Creat...