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

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS Carousel

Sign up for our May 4th event!

May the fourth be with you, join us online!


Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (67,002)