How can we improve WCF Data Services?

Add ability to specify more than 12 properties in the system query option $expand

We implemented a custom data service provider. Some entity types in our data model have quite a few navigation properties which should be specified in $expand at a time. Unfortunately that number exceeds 12 and for now we have to make workaround in the data model exposing additional properties (this leads to de-nomalizaiton and worsens API design). The backend for our WCF Data service is not a SQL DB and some entity sets in the service are just collections in memory which are part of navigation property associations. We want control our self that $expand limitation and the hardcoded assumption is to be removed from the Microsoft class libraries.

27 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Alex shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
completed  ·  Mark Stafford responded  · 

It’s possible to modify this setting in the static InitializeService method by setting a higher value for config.MaxExpandCount.

1 comment

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Alex commented  ·   ·  Flag as inappropriate

    Mark,

    did you ever try that? I tested on WCF Data Services 5.0 and it didn't work. Which version has it been fixed in?

Feedback and Knowledge Base