For OData $filter/$sort queries, our output could potentially different casings vs. the model. In this scenario the query parsing will fail.
For example, if my model has a "Name" property but my JSON outputs the property as "name" I cannot use $filter=startswith(name,'Joe') which consumers would expect.
Discussion reference: http://aspnetwebstack.codeplex.com/discussions/391903
Comments: Are there any updates on this?
For example, if my model has a "Name" property but my JSON outputs the property as "name" I cannot use $filter=startswith(name,'Joe') which consumers would expect.
Discussion reference: http://aspnetwebstack.codeplex.com/discussions/391903
Comments: Are there any updates on this?