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

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

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. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!    

Welcome to the Power Automate Community

You are now a part of a fast-growing vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun.   Now that you are a member, you can enjoy the following resources:   Welcome to the Community   News & Announcements: The is your place to get all the latest news around community events and announcements. This is where we share with the community what is going on and how to participate.  Be sure to subscribe to this board and not miss an announcement.   Get Help with Power Automate Forums: If you're looking for support with any part of Power Automate, our forums are the place to go. From General Power Automate forums to Using Connectors, Building Flows and Using Flows.  You will find thousands of technical professionals, and Super Users with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Automate community forums. Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered. Galleries: The galleries are full of content and can assist you with information on creating a flow in our Webinars and Video Gallery, and the ability to share the flows you have created in the Power Automate Cookbook.  Stay connected with the Community Connections & How-To Videos from the Microsoft Community Team. Check out the awesome content being shared there today.   Power Automate Community Blog: Over the years, more than 700 Power Automate Community Blog articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on the future of process automation. In the Power Automate Community Blog, you can read the latest Power Automate-related posts from our community blog authors around the world. Let us know if you'd like to become an author and contribute your own writing — everything Power Automate-related is welcome.   Community Support: Check out and learn more about Using the Community for tips & tricks. Let us know in the Community Feedback  board if you have any questions or comments about your community experience. Again, we are so excited to welcome you to the Microsoft Power Automate community family. Whether you are brand new to the world of process automation or you are a seasoned Power Automate veteran - our goal is to shape the community to be your 'go to' for support, networking, education, inspiration and encouragement as we enjoy this adventure together.     Power Automate Community Team

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Tuesday Tip | How to Report Spam in Our Community

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Users online (4,730)