WHAT’S HAPPENING When you select a field from dynamic content inside a List Rows action, Power Automate wraps your next step in an Apply to Each automatically. You didn’t add it. You didn’t ask for it. It just appears, which is Power Automate being helpful in the most annoying way possible. If you know only one row will ever come back, you don’t need it. SET THE ROW COUNT TO 1 On your List Rows action, set the Row Count to 1. This tells Power Automate to stop after the first match rather than pulling everything back. Less data, faster flow, less to go wrong. USE AN EXPRESSION INSTEAD Rather than picking the field from dynamic content, type this into an expression instead: body(‘List_Accounts’)?[‘Value’]?[0]?[‘pphub_status’] Here’s what each part means: body(‘List_Accounts’) is the name of your List Rows step. Swap it for whatever yours is called. ?[‘Value’]?[0] grabs the first item in the returned array. Index 0 is always first. ?[‘pphub_status’] is the internal name of the field you want. Swap for yours. WHY BOTHER For a single result, skipping the Apply to Each makes your flow easier to read and debug. It’s overhead your flow simply doesn’t need. Have you been caught out by an unwanted Apply to Each before? Drop a comment below.

We'd love for everyone to get to know each other. Drop a comment below and tell us a bit about yourself. Where are you based, what do you work with day to day, and how long have you been in the Microsoft ecosystem? We'll kick things off first. We're The Power Platform Hub team. We've been working in the Power Platform and Dynamics 365 space for a collective 15 years across a range of industries and project sizes. We built the Hub because we kept seeing the same problem: nowhere decent to get a straight answer when you needed one, and no single place to get important Microsoft updates without wading through noise. That's what this place is for. And this is very much an evolving community. If there's something you'd like to see here, let us know. Now over to you.