Showing results for 
Search instead for 
Did you mean: 
Resolver I
Resolver I

List Records - Why are these required??

I've used XML in my flows for a long time.  I've never had this warning pop up before.

The XML already determines the filtering & field selection - why would I need to fill out those fields.  This seems like a bug.  If the xml section is filled out, these sections should NOT be required.  That defeats the whole purpose of having Fetch XML.


Screen Shot 2020-10-26 at 2.32.07 PM.png

Community Support
Community Support

Hi @Connor551 ,


Thank you for the feedback. Please do open a ticket with us if you would like to track this issue.

However, It only appears to be a warning and shouldn't be a blocker for running the flow.


Thanks and Regards,



Helpful resources

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

MPA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

Power Automate Designer Feedback_carousel.jpg

Help make Flow Design easier

Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!

Top Solution Authors
Top Kudoed Authors
Users online (2,174)