[Closed] WCF Data Services Feature Suggestions

This web site is planned to be retired in July 31, 2019. This web site is no longer being monitored by the Microsoft OData team. Visit http://odata.github.io/odata.net/ for current information on the Microsoft OData Stack for .NET and where to submit feedback.

Welcome to the WCF Data Services feature suggestion list. Find out more information about Data Services at our MSDN page.

If you have questions, need help or find a bug in Data Services, visit our forums.

How can we improve WCF Data Services?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Change the parent id for an entity

    If I save an entity that contains a single owner - has a column containing a parent id in the DB - there appears to be no way to change it using DataServiceContext directly. There are 2 scenarios that fail with this message:

    The closed type xxx does not have a corresponding xxx settable property

    1. Save an entity to the DB that has a navigation property (List) that is empty. Add items to this saved entity later and try to save - fails with message.

    2.Save an entity that contains a property (subtype is a single instance not a…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. client

    Provide a set of client hooks to allow interception/modification of WCF data service requests; to prevent or redirect requests based of client side code.

    example use case:
    I would like to encapsulate a 3rd party web service (non odata) into an odata type service without the need to deploy a web service proxy; ie. write a client side odata proxy.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support primitive types and their collections as result of ServiceOperations

    If you just need to get a list of strings, you have to define an entity with one property. It would be much easier, if one can receive IList<string> or IList<int> direct from ServiceOperation, without going all Model->Entity->Refresh Proxies cycle.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add Velocity Support and

    Add Velocity(AppFabCaching) Support for DataService .Also add Claim Support for Security.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Access

    Support Microsoft Access Database.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Build EntityFramework Client over WCF

    Build EntityFramework Client over WCF

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. WeakReference entity tracking

    The ability to configure the EntityContext to not hold onto hard references to Entities would be useful. My WPF client application uses a single long-lived EntityContext for the duration of it's life as it provides a great way to ensure that I have a unique reference for the duration of the application by which to key windows, and view model instances, from.

    However, since EntityContext holds onto tracked entities they can never be garbage collected.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. improve CommunicationException

    Give us the possibility to differentiate between different exception !

    What I'd like to do is to catch an WCF exception with typical TRY & CATCH, and with a numeric code distinguish between an Message size exceeded and a Timeout errors.

    My suggestion is to add new properties to the exception base class containing a integer number. One for error code and one for suberror code.

    And then when an CommunicationException will be generated is possible to fill the two properties above.

    So i can create different catches based on exception type and, internally, verify which error code has been…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Should be able to project entity type or complex type objects

    Instead of creating anonymous types we should be able to project the LINQ to entity type or complex type.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Result set shaping or styling

    Be able to intercept the output easily to shape the data - hiding columns per role for example, or shaping using xslt. A [DataMember(Roles="Admin)] attribute in Code First, and some form of equivalent method in edmx and designer.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide (better) support for distributed transactions

    Of course it is already possible to handle distributed transaction e.g. by using MSDTC. But compared to what's possible in the Java world, this method feels a little 'outdated'.

    Additionally, because EF7 will get Support for non-relational data providers there will be a strong need to handle distributed transactions that involve relational databases and non-relational datastores within the same transaction. Think of scenarios where a document, image, movie clip is stored in NoSQL datastore but its index fields, metadata and so on may have to be stored in a SQL database.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Implement the top ideas in this list

    Instead of arbitrary improvements that are unrelated to customer demand (according to the content of this forum), pay attention to what people are actually requesting

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Provide a way to set $top for inner feeds

    If I have a uri that has an $expand in it, the $top applies to the outer Entries but not to the feeds inside each entry due to the $expand.

    There are many cases where a $top1 is wanted to provide just 1 entry at each level, the outer level, and for each feed. At present that outer 1 entry can have feeds with hundreds of entries each.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support Count(predicate) and other similar LINQ methods

    Currently even WCF DS 5.0 throws: 'The method 'Count' is not supported.'
    Please support it and other similar LINQ methods.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Adopt strongly typed hierarchy-supporting Expand statement

    ctx.Businesses.Where(i => i.Id == 123).ExpandMany(i => i.Persons).ThenExpand(i => i.Name).Expand(i => i.Foo);

    This syntax is adopted from NHibernate. Collections can be navigated by using the ExpandMany form. It operates exactly as OrderBy, ThenBy.

    When expanding hierarchies, we're currently forced to resort to non-type safe constructs.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

[Closed] WCF Data Services Feature Suggestions

Feedback and Knowledge Base