Answered

Bug with editor for filter action changing where clause to @notcontains()

(2) Share

Report

Posted on by MichelH

401

Power automate editor messes with my code.
Filter action now has this code in where '@notcontains(body('SelectSP2'),item())' that I cannot enter myself.

I need to go to the settings and change to 'contains', and then change it back to 'not contains'.
I'm getting tired of doing that.
Wonder how many times more I need to do this.

Anyone else seeing this?

Thanks for any feedback.

Categories:

Building flows

I have the same question (0)

All responses (10)

Answers (1)

VictorIvanidze 13,073 on at

Like (0)

Report

Just use the old editor,

Was this reply helpful? Yes No
MichelH 401 on at

Like (0)

Report

@VictorIvanidze

Catch22,...

The old editor messes with with Select actions,...

Sometimes wish I could just edit a JSON text instead of using these editors.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (1)

Report

I am seeing this bug, too, MicheleH!

What's worse ... I am seeing it in Logic Apps, too! (and it is breaking business critical infrastructure)

Also ... You *can* edit the JSON of your flow, if you like ... if you export the flow and ensure that it is set to update (not add as new) then you can unzip that ... edit the definition file ... then zip it all back up and upload.

( just gotta be careful on the json editing ... but ... it can be super powerful ... like ... I use the Power Automate flows to edit my flows to make them even betterer with cool stuffs )

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (1)

Report

I have raised this, here:

https://github.com/Azure/LogicAppsUX/issues/6851

Feel free to second it. :-)

If you wanna signal boost my LinkedIn on this, too ... that's here:

https://www.linkedin.com/posts/eliot-cole_logicapp-powerautomate-activity-7308902285802164224-7qDC

---

Edited to add:

I think you are VERY right to question how many more flows could be affected by this ...

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (1)

Report
I have a work around for you ... ( not a fix, but this can at least help sort it out short term ) ... which I have confirmed to work twice in Logic Apps, would be good if you can test it in Power Automate on your broken flow, though!

For each Filter that has this issue perform the following:

Tap 'Edit in advanced mode'

Tap ANYWHERE in the 'Filter Query' text

Tap 'Edit in basic mode'

Save the flow/workflow

This then triggers the workflow to be savable (flow in your case) and you should be able to get it back to a working state.

I tested this by performing the actions on two disparate occurrences of this, with separate saves, so it need not all be captured at once.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

This is still occurring.

Another user has picked this up on the LA thread in the UX GitHub, here:

https://github.com/Azure/LogicAppsUX/issues/6851#issuecomment-2759713924

Was this reply helpful? Yes No
Verified answer

eliotcole 4,363 Moderator on at

Like (0)

Report

This has been flagged as apparently fixed in Logic Apps, but since Power Automate split, and there is no way to speak to them about issues ... ... well ... errrr.

Was this reply helpful? Yes No
MichelH 401 on at

Like (0)

Report

Thanks @eliotcole

I guess I should better use Logic Apps then. :-)

I will see if it still occurs on my side and open a ticket with support if it does.

Br,
Michel

Was this reply helpful? Yes No
Suggested answer

David_MA 12,982 Super User 2025 Season 2 on at

Like (0)

Report

I believe the correct expression should be @not(contains(body('SelectSP2'), item()))

Not and contains are two separate expressions.

Was this reply helpful? Yes No
eliotcole 4,363 Moderator on at

Like (0)

Report

@MichelH ... I don't think that you should need to switch to Logic Apps ... they both have their use cases! Although they have apparently got the notcontains() fixed there, they think. :-)

--------

@David_MA I think that you have maybe missed the point, mate!

Was this reply helpful? Yes No