Get Items - Odata Filter - Lookup Field

[GuillaumeBD]

Hello, I'm looking to filter on a lookup field in the entry table I'm using, not to the source table. Here's what I mean:

The examples I found on the web are like this: State_Name/State eq 'Dynamic content of state' to filter to the source table.

I don't want to do that. I just want a regular filter on the entry table and get the PO Numbers for the different states.

Example: Filter on Alabama and get the results : 01,02,05.

I'm not able to filter since it is a lookup field. I tried State_Name, State_Name.Value, State.Name/Value. Nothing works!

Any Ideas

Thank you

[Nived_Nambiar · Accepted solution]

Hi @GuillaumeBD 

I think State column in Source table has been created by renaming Title column, so in that case try like this 

Hope it helps !

Thanks & Regards,

Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
Blog: Nived Nambiar's Blogs

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌

[GuillaumeBD]

Hello, as stated, I don't want to filter on the source table. I just gave the example so people understand that I don't want to that. I just want to filter on the Entry table alone.

Thank you

[Nived_Nambiar]

Hi @GuillaumeBD 

To make filter actions more independent of source table, i could not see any approach apart from using one which i shared via filter query.

Other way would be to use filter array like below

But i still did not understand why you need try that way as the column itself is derived from source table ?

Thanks & Regards,

Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
Blog: Nived Nambiar's Blogs

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌

[GuillaumeBD]

Hello, I didn't understand why you were referencing to the source table as it seems useless in my scenario. I tried it and you are right, it's working! A lot of stuff in Power Automate are not really logical...

Thank you!

[Nived_Nambiar]

Hi @GuillaumeBD 

But that column itself is coming from source table right ?

Thanks & Regards,

Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
Blog: Nived Nambiar's Blogs

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌

[GuillaumeBD]

Yes, lookup field.

[Nived_Nambiar]

Then we need to reference that source table , but u are saying it is useless to reference it as it has usage there ? i did not get why so ?

Thanks & Regards,

Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
Blog: Nived Nambiar's Blogs

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌

[GuillaumeBD]

I thought it was useless because I don't understand the logic of doing it since I just want to do a simple filter on the entry table and it has nothing to do with the source table. But as you showed, the logic of Microsoft is that if it is a lookup field, you need to reference the source table no matter what. 

Thank you