Odata expand with where clause

Question

0.00/5 (No votes)

See more: (untagged)

Hi Gents,

I have an OData service which is being used in an application.

In that Application I try to:

C#

DataFromService = ODataStore.MarinGlobalService.Instance.Service.Users
                    .Expand(x => x.ApplicationUsers.Where(y => !y.IsDeleted));

It leads to an error:
The expression 'x => x.ApplicationUsers.Where(y => Not(y.IsDeleted))' is not a valid expression for navigation path. The only supported operations inside the lambda expression body are MemberAccess and TypeAs. The expression must contain at least one MemberAccess and it cannot end with TypeAs.

How can I check only the IsDeleted = false are incuded in the expand result?

What I have tried:

My services has for usergroups the .Where(x => !x.IsDeleted)

C#

[EnableQuery(MaxExpansionDepth=8)]
        public IQueryable<UserGroup> GetUserGroups()
        {
            return db.UserGroups.Where(x => !x.IsDeleted);
                
        }

Still the Expand function gives me the rows of data that has IsDeleted = true.

Posted 12-Mar-20 4:03am

Herman<T>.Instance

Add a Solution

Comments

Richard Deeming 12-Mar-20 10:39am

Have you enabled nested filters on the server?
Nested $filter in $expand - OData | Microsoft Docs[^]

Which OData client library are you using?

Herman<T>.Instance 12-Mar-20 11:18am

I use OData connected services

Richard Deeming 12-Mar-20 11:38am

Based on the error message, I suspect you're using:
GitHub - OData/odata.net: ODataLib: Open Data Protocol - .NET Libraries and Frameworks[^]

(Either directly or indirectly.)

It looks like there are various issues logged on that project regarding filtered "expand" operations. I can't see anything that directly relates to your error message. It might be worth logging an issue there.

Herman<T>.Instance 12-Mar-20 11:39am

I use a V3 protocol. I just started upgrading to v4 and retry the issue. Have the
config.Filter().Expand().Select().OrderBy().MaxTop(null).Count();
added

Herman<T>.Instance 12-Mar-20 12:12pm

Library = Microsoft.aspnet.Odata.

Upgrading to V4 and adding the nested $filter in $expand did not help.

Any other options?

Richard Deeming 12-Mar-20 12:14pm

As I said, you might need to log an issue on the GitHub project to see if they can fix it.

Herman<T>.Instance 12-Mar-20 12:33pm

Are you OK with routes?

I have function and Odata client creates
http://wrk2198:80/marinservices/ProjectUsedModels(modelNumber='10000')
Where my service says

[EnableQuery]
[ODataRoute("ProjectUsedModels?modelNumber={modelNumber}")]
public IEnumerable<projectusedmodels_result> Get([FromODataUri]string modelNumber = "")

Why the route in the service is not used by the client?

Richard Deeming 12-Mar-20 12:38pm

I don't know how the client would know anything about the server's routes?

All of the examples in the documentation seem to use a similar convention to the URL your client is creating:
Attribute Routing - OData | Microsoft Docs[^]

Herman<T>.Instance 13-Mar-20 5:35am

Have you seen my other question about this issue?
https://www.codeproject.com/Questions/5259132/Odata-v3-v4-issue-on-userdefined-controllers

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)