Unanswered

Filter Array and Dynamic Content

(0) Share

Report

Posted on by LD-09040901-0

Hello everyone,

I'm currently setting up an email workflow that triggers based on certain conditions.

Here is a screenshot of my flow. I created it a while ago, and at that time, after the filter arrays, I could select dynamic content from the output of those filter arrays.
Except that now, I can no longer do that; I can no longer select dynamic fields from those filter arrays, except for the general body. Here is also the raw outputs of the filter array

On the second screen, the value "etat" comes from the first time I edited this flow, that was working well with dynamic fields.

I’ve tried creating new, different flows, even pretty simple ones, and the behavior remains the same, so it’s not due to the nature of my file, neither my flow itself I guess ?

Has the behavior of filter arrays changed with a recent update? Do you have any idea on how to fix it ?

Thank you in advance for your help!

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

David_MA 14,499 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
I am not 100 percent sure on this, as I don't use filters too often, but try this while you wait for someone else to reply:

Go to a run of the flow and copy the body in the outputs of your first filter:

Add a Parse JSON action after your first filter and use the body of the first filter to generate the Scheme for the Parse JSON action.

Then point your second filter to the body of the Parse JSON action, and use the values from the Parse JSON action in the second filter.

Although, someone who is really good at this will probably be able to do both filters in on filter array action.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,084 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @LD-09040901-0,

Are you able to fix this issue as suggested by @David_MA?

What you’re seeing is expected with the new Power Automate designer. The behavior of Filter array outputs has not changed at runtime, but the designer no longer infers and surfaces individual fields as dynamic content. You can restore dynamic fields after a Filter array by using Parse JSON as a schema definition step.

How to fix it

1) Add Parse JSON right after your Filter array
Set Content to:
first(body('Filter_array_1'))

Click Use sample payload to generate schema and paste this sample (based on your screenshot):
{
"@odata.etag": "",
"ItemInternalId": "12345",
"ID": "3",
"Date": "2026-04-08T07:58:17Z",
"Sender_Name": "Sample Sender",
"Sender_Email": "sender@example.com",
"Contact_Person_Name": "Sample Contact",
"Contact_Person_email": "contact@example.com",
"Command_Info": "Bonjour ceci est un test",
"Explanation": "et je veux qu'il soit done, mais pas notified",
"Department": "International",
"Adress": "Sample address",
"Etat": "Done",
"Notified": "",
"Date_Done": ""
}

After this, fields like Etat, Notified, Sender_Email, etc. will reappear in the Dynamic content picker for the next actions.

OR

If you prefer expressions instead of Parse JSON, use:
item()?['Etat']

The ? avoids flow failures if a field is missing.

Was this reply helpful? Yes No