cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
efialttes
Community Champion
Community Champion

ODATA Filter queries on LookUp columns from a SP List

Hi again!

So, I have implemented a flow that executes a SP Get Items. I am trying to include an ODATA filter; the way I compose it is working fine, but it gives me an empty array as a result. ODATA filters are working fine for me so far if the ODATA expression targets a SP list String column...but do ODATA filters support queries agains a SP list LookUp columns?

 

The filter query expression I am using is:

AppPreloadSlotID eq 'Test | xxxxxx | xxxxx | xxxxxxxxxx | 20180119033416359'

 

ODATA_SearchColumns.png

 

UPDATE: I have found a thread in Flow Forums adressing this same issue https://powerusers.microsoft.com/t5/Building-Flows/OData-Filter-Query-on-SharePoint-Lookup-Site-Colu...

The thread was started in May 2017, just wondering if there is some new functionality covering this topic since then. I have tried also with the following ODATA filter expression, but I am getting a Bad Gateway error:

 

AppPreloadSlotID/Value eq 'Test | xxxxxx | xxxxx | xxxxxxxxxx | 20180119033416359'

 

Thank you in advance!

Did I make your day? If so, mark my response as 'Solution' !!!

También escribo sobre Power Automate en este Blog y en Twitter

1 ACCEPTED SOLUTION

Accepted Solutions
v-yuazh-msft
Community Support
Community Support

Hi @ efialttes,

 

Using OData query to filter items based on Lookup column of SharePoint list is not supported in Microsoft Flow now, if you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

In condition, you could consider take a try to filter items based on Lookup column of SharePoint list using "Filter array" action.

I have made a test on my side and please take a try with the following workaround as an alternative way:

 1.jpg

 

The “repairshop” column is a Lookup column of my SharePoint list, you could use the “Filter array” action to filter which “AppPreloadSlotID Value” is equal to “Test | xxxxxx | xxxxx | xxxxxxxxxx | 20180119033416359“.

 

The flow works successfully as below:

 

 2.jpg

 


Regards,
Alice Zhang

View solution in original post

17 REPLIES 17
v-yuazh-msft
Community Support
Community Support

Hi @ efialttes,

 

Using OData query to filter items based on Lookup column of SharePoint list is not supported in Microsoft Flow now, if you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

In condition, you could consider take a try to filter items based on Lookup column of SharePoint list using "Filter array" action.

I have made a test on my side and please take a try with the following workaround as an alternative way:

 1.jpg

 

The “repairshop” column is a Lookup column of my SharePoint list, you could use the “Filter array” action to filter which “AppPreloadSlotID Value” is equal to “Test | xxxxxx | xxxxx | xxxxxxxxxx | 20180119033416359“.

 

The flow works successfully as below:

 

 2.jpg

 


Regards,
Alice Zhang

joshnystrom
Kudo Collector
Kudo Collector

@JackWert clarified in this thread/post https://powerusers.microsoft.com/t5/Building-Flows/OData-Filter-Query-on-SharePoint-Lookup-Site-Colu... that this is a feature (and possibly always was, as I can't find any references to it as a new feature). The syntax is, as quoted from his post:

Super simple solution to this:

InternalFieldName/Title eq 'Lookup Value'

or

internalFieldName/Id eq 'Lookup Id'

Hope this helps someone!
Josh

Network-iQ
Frequent Visitor

I have a similar issue, however, my lookup items are on a dropdown list.

 

I created a seperate list item that did not include a lookup but does have the items in a drop down. I cannot filter them, nor does the array filter return any result.

 

Is this something that is not possible?

 

Thanks

Hey @Network-iQ,

I just did a bit of testing for this and from what I can tell, dropdowns (Choice columns) are treated a little differently. That is, they're actually simpler to filter because they're treated less like a set of attributes, despite their appearance in a JSON payload.

You haven't given a lot of detail around your specific situation, but from the generalities, I'd recommend just giving the ODATA filter a try using the simple syntax:

ChoiceField eq 'Desired value'

While the Choice fields in SharePoint are given Key-value pairs for ID and Value, those IDs and Values don't seem targetable from ODATA as they are with LookUp fields. Notably, Choice IDs are re-assigned according to the list order, making it difficult to gain anything by trying to stick to IDs anyway.

Hope this helps!

Josh

 

Howdy -

 

Thanks for the reply.

 

Let me give you some specifics.

 

I want to be able to send a report that includes only the previous week's data on a specific customer. The Customer column is a lookup to a seperate list with customer contact info in it. I want to be able to output it to an email in table form. The HTML output array is perfect, and that does the job. Presently, however, if I use the ODATA filter, it gives me nothing. If I leave it blank, I get everything in the list.

I have two challenges. Number 1, the ODATA filter will not give me any output. I have it set up to look like this:

Customer eq 'ABC 123'

 

When I run it, the output is just [ ]

 

Secondly, I have been trying to figure out how to get nothing but the previous week's data. I think I can tinker that together, but so far it also pulls everything.

 

Any help you could offer is greatly appreciated.

 

Thanks!

Hey @Network-iQ, that's a big help, especially as it clarifies which type of column you're looking to filter. In this case, an unfiltered Flow will bring back each of your data records with a Customer attribute that looks like this:

"Customer: {
"@odata.type": "#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference",
"Id": 6,
"Value": "ABC 123"
}

 

As a LookUp field, ODATA needs to be told which sub-attribute you want filtered. The important thing here is that if you're looking to filter by whatever populates "Value", then you actually need to provide the "True name" of the field targeted in the "Get information from:" section of the LookUp column's configuration.

So, if I have CustomerName selected as my target here:

LookUp Column - In this column.JPG

then I need to go check what that Fields "True name" is on the Community Flow Outputs lookup list (viewable in the address bar when editing the target column)

Column TrueName.JPG

and use that "True name" in my ODATA filter.

Give it a try with your CustomerName field called out specifically using the syntax from earlier in the thread. In my example I'd be using:

OutputLookup/Customer_x0020_Name eq 'ABC 123'

 

I've had mixed results filtering SharePoint list items based on date fields, so I'm not able to speak to it with confidence. If I dig into it anytime soon, I'll try to remember to funnel any insights your way.

Hope this helps!

Josh

 

 

HI Josh -

 

Thanks for the reply.

 

The true name is actually 'Company'. I have to wonder if that causes an issue, however. List A is the customer contact info. List B uses a lookup for 'Company'. The name of both the field on list A and on list B is 'Company'. I am going to see if I can filter it using a different parameter. Otherwise, no change.

 

I shall post my results shortly.

Well, if I use a non-lookup column, no problem. It works.

But that is not going to work. Haha.

 

Any ideas would be greatly appreciated.

 

Thanks

Hey @Network-iQ

Yeah, non-lookups are way easier to use here (but much less useful, as you've noted!). While we go through this, if you could provide even more detail as to what specifically you're trying, I, or anyone else reading, may more easily notice anything not quite right. Simple screenshots of your filter and any error message you receive in the Flow action failure goes a long way (though typing it out helps make sure you're not sharing private information).

That being said, you've called out that the arrangement is perhaps a bit confusing, and the detail you've given already does help. I'm going to go out on a limb and guess that you're still just trying it as "Company eq" rather than the less intuitive (but correct):

Company/Company eq 'ABC 123'

Can you please confirm whether you're trying it exactly as above?

Thanks,

Josh

Good lord...I was entering the information in the format you had suggested, but I had missed the fact  that your example used a slightly different term since you did not have all of the information. Company/Company worked perfectly. Thank you so much!

Hey great, I'm glad it worked!
Cheers!
Josh

Is this possible yet? Looking to filter by a Lookup column.

Thanks


@joshnystrom wrote:

@JackWert clarified in this thread/post https://powerusers.microsoft.com/t5/Building-Flows/OData-Filter-Query-on-SharePoint-Lookup-Site-Colu... that this is a feature (and possibly always was, as I can't find any references to it as a new feature). The syntax is, as quoted from his post:

Super simple solution to this:

InternalFieldName/Title eq 'Lookup Value'

or

internalFieldName/Id eq 'Lookup Id'

Hope this helps someone!
Josh


This post should be marked as Answer to the question instead of the one from @v-yuazh-msft . It is clearly a direct solution to the original question and not a workaround. The number of "thumbs up" on this post confirms this.

Also, I think it's a shame that the OP never even bothered to reply to the topic they started, not even a simple "thank you".

Thanks @joshnystrom for mentioning this, it works perfectly.

Thank you, @joshnystrom - this worked perfectly for me!

This should be the answer. Thanks a lot for sharing

This is perfect tip, I was trying to write proper filter code for days.

It worked for me!

Helpful resources

Announcements

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!    

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!           Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

Microsoft Power Platform | 2024 Release Wave 1 Plan

Check out the latest Microsoft Power Platform release plans for 2024!   We have a whole host of exciting new features to help you be more productive, enhance delegation, run automated testing, build responsive pages, and so much more.    Click the links below to see not only our forthcoming releases, but to also try out some of the new features that have recently been released to market across:     Power Apps  Power Automate  Copilot Studio   We can’t wait to share with you all the upcoming releases that will help take your Power Platform experience to the next level!    Check out the entire Release Wave: Power Platform Complete Release Planner 

Users online (5,516)