public class UmbrellaController : ODataControllerĬategory = Compan圜ategory.Communication, Like the EntitySet controller, the singleton controller inherits from ODataController, and the singleton controller name should be Controller. If there is any ambiguity in the model, you can use HasSingletonBinding to explicitly bind a navigation property to a singleton HasSingletonBinding has the same effect as using the Singleton attribute in the CLR type definition: EntitySetConfiguration employeesConfiguration =ĮmployeesConfiguration.HasSingletonBinding(c => c.Company, 'Umbrella') The binding is done automatically by ODataConventionModelBuilder, since only Umbrella has the Company type. The generated metadata will look like the following: įrom the metadata we can see that the navigation property Company in the Employees entity set is bound to the singleton Umbrella. Here, builder.Singleton('Umbrella') tells the model builder to create a singleton named Umbrella in the EDM model. ODataConventionModelBuilder builder = new ODataConventionModelBuilder() īuilder.EntitySet('Employees') builder.Singleton('Umbrella') īuilder.Namespace = typeof(Company).Namespace Generate the EDM model based on the CLR types. / Present company category, which is an enum type We'll create a singleton in your Web API project using the following data model:Ī singleton named Umbrella will be defined based on type Company, and an entity set named Employees will be defined based on type Employee.

To create an OData V4 endpoint in Web API, see Create an OData v4 Endpoint Using ASP.NET Web API 2.2. For information on what a singleton is and how you can benefit from using it, see Using a singleton to define your special entity.

This article shows how to define a singleton in an OData endpoint in Web API 2.2. But OData v4 provides two additional options, Singleton and Containment, both of which WebAPI 2.2 supports. Traditionally, an entity could only be accessed if it were encapsulated inside an entity set.

Mww web api