This project is read-only.

Roadmap of OData

Topics: ASP.NET Web API
Oct 18, 2013 at 8:26 PM
From the roeadmap of OData:
We will allow user to define model without a real CLR type as well as modify a property name on the model easily.

Is this released with the current 5.0?

I think, this could be the solution for my problem with dynamic data objects.

Best regards
Oct 18, 2013 at 8:32 PM
You can return an IEdmObject in ASP.NET Web API 2, which doesn't require a CLR type. Property name aliasing is coming later, but we are working on it.

Daniel Roth
Oct 18, 2013 at 8:43 PM
Hi Daniel
Do you know an example with IEdmObject?
I have no Entity Data Model and load the data with SQL-Querys from the database(SQL Server). The WebAPI should be dynamic, because some SQL-Server-Tables are created by the customers. I have a table Products with ProductID, Name, BaseUnit and a table ProductAttributes. Customers can create columns e.g. LastPurchase, Prototype,...
As result, the WebAPI should return a Product-Data with ProductID, Name, BaseUnit, LastPurchase, Prototyp as like the last 2 Values are fix properties.

What means later? 1 Month, next year,...?

Christoph Schmid
Nov 18, 2013 at 10:03 PM
With this posting, I could create first examples with reading data in excel.

Very nice functions, big thanks to the odata-team.
I hope, there well be shortly more examples(relation between PrimaryKey and ForeignKey)

Does some know, how I can tell Excel, that it should load data step by step(paged) and not all data.