John Gathogo

Thanks @hakanaltindis for reporting the issue. I believe the model that EF is exposing is inconsistent, and that it's a known issue, and that there's no one-size-fits-all solution to the...

@hakanaltindis Maybe @mikepizzo could chime in to clarify the OData TC committee's thinking around ignoring `$expand` query option but let's think about it for a sec. Should the following 2...

Gentle ping @KwizaKaneria. Could you please share a repro or more detailed repro steps to help us understand the issue better?

@KwizaKaneria Please confirm whether `counties` is a contained navigation property

@KwizaKaneria Please confirm whether you have implementing the relevant controller action in support of navigation property routing. In your case you'd need to implement a controller action named `GetCounties` as...

@KwizaKaneria I don't understand your statement about separate container. Can you confirm whether you implemented the *required* controller method?

Hi @KwizaKaneria. Do you need further help with this? Did you try the suggested solutions?

@Molinware Seems that this error is observed when making synchronous calls. As a workaround, the alternative is to call ExecuteAsync as opposed to calling the LINQ methods like `FirstOrDefault()` and...

@cloudsere Partial support for collection of collections is the form of collection of untyped or just untyped. We do not support a collection of primitive collections, i.e. (`IEnumerable`). You'd need...

Because untyped provides limited support both in materialization and query options it's recommended to use a collection of complex types as suggested by @xuzhg above.