Showing results for 
Search instead for 
Did you mean: 

Odata Filters & nested objects with Microsoft Flow


Last week, Kent Weare from the Microsoft Flow team illustrated the usage of the very convenient and elegant oData Filter in Microsoft Flow. Read his blog post to have a good background on OData and Flow.


As a follow-up of this blog post I would like to get a little bit deeper with a more specific example that I had to solve last year : filtering on a nested field like the e-mail address of a SharePoint Person column.

If you have the following SharePoint list with 2 columns of type Person or Group : Managee and Manager




…and your flow needs to retrieve the Manager of ‘serge luca’ (


The oData filter query will be the following :




How did I know this ?


Use the Get items action in your flow without using any filter, debug it and check the output JSON : we get something like this :




so Managee/Email is the good filter syntax : indeed Email  is the nested field and its  path is Managee/Email.

…and yes the Eq operator is very case sensitive : Managee/email won’t work ...


Thanks for your post, this is something that I've been trying to work out for ages.

However, I have tried to replicate this, but everytime the Flow runs I get a "BadGateway" error:




The Body of the error is:


My "Cascade Child 1" list has a (single value) Person column in it called "Person".


Can you see what I'm doing wrong?

Thanks for any assistance,



*** Update ***

I have worked this out myself, it was the case of "Email" causing the issue.  In your notes it mentions "EMail" and "Email", and in the screenshot of JSON output it shows as "Email".  I thought the case in the JSON output would have been correct and your references to "EMail" in your notes maybe a typo.  However, changing my filter query to "EMail" worked!



I'm having a different issue with this.


When I use the filter, I'm able to get the item "Managee" which matches the criteria, but I'm not able to get the info from the "Manager" column beside it. What was the next step?


(The "Manager" email / department / etc. options all vanish from the dynamic content options for following steps).

Wow... so in JSON summary one can find "Email" but you still need to put "EMail" in the query. So logical... thanks Microsoft

Super User

Like it mentioned in the update EMail (Case sensitive) works. To filter by DisplayName it doesn't work either. Not sure where we can get this schema name similar to EMail.

Helper II

so Managee/Email is the good filter syntax : indeed Email  is the nested field and its  path is Managee/Email.

…and yes the Eq operator is very case sensitive : Managee/email won’t work ...


Should be Managee/EMail  because Managee/Email doesn't work. Use a capital M when searching an emailaddress in Person fields. Your screenshot was correct but the text below wasnt. 

About the Author
  • Experienced Consultant with a demonstrated history of working in the information technology and services industry. Skilled in Office 365, Azure, SharePoint Online, PowerShell, Nintex, K2, SharePoint Designer workflow automation, PowerApps, Microsoft Flow, PowerShell, Active Directory, Operating Systems, Networking, and JavaScript. Strong consulting professional with a Bachelor of Engineering (B.E.) focused in Information Technology from Mumbai University.
  • I am a Microsoft Business Applications MVP and a Senior Manager at EY. I am a technology enthusiast and problem solver. I work/speak/blog/Vlog on Microsoft technology, including Office 365, Power Apps, Power Automate, SharePoint, and Teams Etc. I am helping global clients on Power Platform adoption and empowering them with Power Platform possibilities, capabilities, and easiness. I am a leader of the Houston Power Platform User Group and Power Automate community superuser. I love traveling , exploring new places, and meeting people from different cultures.
  • Read more about me and my achievements at: MCT | SharePoint, Microsoft 365 and Power Platform Consultant | Contributor on SharePoint StackExchange, MSFT Techcommunity
  • Encodian Owner / Founder - Ex Microsoft Consulting Services - Architect / Developer - 20 years in SharePoint - PowerPlatform Fan
  • Founder of SKILLFUL SARDINE, a company focused on productivity and the Power Platform. You can find me on LinkedIn: and twitter I also write at, so if you want some Power Automate, SharePoint or Power Apps content I'm your guy 🙂
  • I am the Owner/Principal Architect at Don't Pa..Panic Consulting. I've been working in the information technology industry for over 30 years, and have played key roles in several enterprise SharePoint architectural design review, Intranet deployment, application development, and migration projects. I've been a Microsoft Most Valuable Professional (MVP) 15 consecutive years and am also a Microsoft Certified SharePoint Masters (MCSM) since 2013.
  • Big fan of Power Platform technologies and implemented many solutions.
  • Passionate #Programmer #SharePoint #SPFx #M365 #Power Platform| Microsoft MVP | SharePoint StackOverflow, Github, PnP contributor
  • Web site – Youtube channel -