Changing "and" to "or" in a Condition - Now Need to Re-Enter Condition

[antony]

Hey folks… I used to be able to have a complex condition such as

ShowForm = Yes and Search:count>0

Then copy and change the condition so that it reads

ShowForm = No or Search:count=0

and I could click on the “and” and change it to “or” without the search going away.

That has just changed, and now I have to re-enter the search… which is pretty tedious… especially as some of those conditions have many parts to them.

Not quite a bug, but a rather annoying removal of a useful feature.

Is anyone else finding this too?

Best wishes,
Antony.

[JonL]

To be honest I can’t remember very well.

What I know is that there are 4 different type of behaviours depending on where the condition is set. Workflow condition, conditional tab, property editor and advanced filters.

It would be great to have the same behaviour in all of them. And if possible that the behaviour implies less rework as possible.

[keith]

It was noted by @josh that doing this trick (copying an expression and pasting it to a place that would NOT let you construct that same expression) is unsupported behavior and subject to breakage.

I had mused about this here:

Memory Issues: What Data is Loaded when a Page Element has a Type?

Yeah: couple of observations: The issue with page level privacy is the interface simply isn’t designed to enable that. You can craft these expressions (somewhere else) and paste them, but then ANY condition that passes unlocks a permitted value so you wind up with some very wonky expressions (and lots of them to cover all the cases). Implicit OR having to be worked around! Not a good approach. (Though it DOES prohibit data loading… so it’s an option, but a fragile one.) it’s fairly easy to tes…

And Josh explains why this is a no-no here:

Memory Issues: What Data is Loaded when a Page Element has a Type?

Yes, anything that involves working around our UI via copy / paste or similar tricks is a bug and cannot be relied on. If something doesn’t appear in a drop down, it’s almost always because we need to do work on the backend for it to function properly. Occasionally you might find things that look like they work, but in practice there’s usually some kind of issue that will either cause you unexpected problems or lead to us unexpectedly changing it. Sorry to be a buzzkill, I like Easter eggs too…

I know this isn’t helpful to you now, @antony , but wanted to point this out to other intermediate to advanced Bubblers as a warning.

[JonL]

I think he is referring to the fact that if you have Expr1 and1 Expr2 and2 Expr3 and3 …ExprN if you change and1 to or1 it Bubble will delete Expr2…ExprN from the condition builder. Making it a pain in the ass having to build again the whole condition.

Or at least that is what I understood.

[emmanuel]

We fixed this. Thanks for flagging this.

[antony]

It’s a pleasure @emmanuel… thanks for the quick fix!

[antony]

@emmanuel… while on the subject of losing an important editing feature…

For about 6 months now it has not been possible to copy and paste an expression which is of type text, which at times is very inconvenient.

For example, right now I am having to re-create an entry which assigns a text field followed by six search and replaces, each of which I’m re-entering manually.

Is there any chance of a quick fix to this?

Thanks!
Antony.