# Multiple conditions are met at the same time / Minor condition

**URL:** <https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580>\
**Category:** Ask for Help\
**Created:** [March 22, 2021, 9:57am UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580 "2021-03-22T09:57:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_hien](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/michael_hien/32/18864_2.png) [@Michael\_hien](https://community.glideapps.com/u/Michael_hien)\
**Post date:** [March 22, 2021, 9:57am UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580/1 "2021-03-22T09:57:07Z")

</div>

As far as I have tested and done some digging, Glide’s conditions in Custom action are designed to trigger the first-met one

Wouldn’t it be nice if we could have **an option to trigger all met-conditions**? In that case, there is one issue that I could so far think of, which is the sequence of actions to be triggered.

For example, in this case, what I want is to trigger both of these conditions, as both of the fields are empty. The sequence doesn’t really matter here.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/b/eb084a78b9b8b48a710eba08e94b7bf16c50232b.png)

Otherwise, wouldn’t it be even better if we could have **minor condtions**? It’s like you have your first condition met, then actions implemented, then next condition to judge if following actions should be executed or not.

It’s basically the similar idea. I’m not sure if we have had these or not, I’m just getting tired of having to set 3+ conditions, each includes 3 actions least, all in 1 Custom Action.

Please advise if you have better ideas 😍

---

<div class="post-metadata">

**Author:** ![Mark\_Turrell](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark_turrell/32/26605_2.png) [@Mark\_Turrell](https://community.glideapps.com/u/Mark_Turrell)\
**Post date:** [March 22, 2021, 10:55am UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580/2 "2021-03-22T10:55:13Z")

</div>

The way I handle conditions which need to all be set (e.g. filling in a form and all fields need to be completed before a ‘Save’ button appears) is to kind of cheat - using if-then-esle and template columns that combine the entries and then use that for my final condition. For instance:

name  
address  
phone

so the IFE (if-then-else) ift-name = if name is not empty, then Y

and then TP (template) tp\_complete = nameaddressphone  
— would give me YYY is all complete

Then I check to see if YYY is there in tp\_complete

---

<div class="post-metadata">

**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\
**Post date:** [March 22, 2021, 11:57am UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580/3 "2021-03-22T11:57:52Z")

</div>

I do something similar, but I’m not quite so generous with the columns. In that scenario, I’d use just one column…

- if name is empty, then false
- else if address is empty, then false
- else if phone is empty, then false
- else true

😉

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [March 22, 2021, 12:00pm UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580/4 "2021-03-22T12:00:14Z")

</div>

It is standard in all programming languages to always stop processing once the first true condition has been met and processed.

In your case I would add a third condition in front of the other two. The first condition would check if Phone AND Address are empty, then set all necessary columns. Else, let it run through the other conditions. It’s all about the correct heirarchy.

I absolutely agree that the If Then logic needs work in glide.

@Robert_Petitto created a feature request that asks for exactly what you want.

> [@Action Editor \> Connect/Add branching actions and conditions](https://community.glideapps.com/t/action-editor-nodes-connect-actions/24544):
>
> The action editor is the most powerful feature of glide. It’s one limitation is that conditions are only allowed at the root level. Would love the feature to check one condition, make one change (like an increment or set column) and then continue the workflow/path contained in a separate condition. Kind of hard to explain in words. Watch the video below to see what I mean. Image uploaded by @Lucas_Pires@tristan @jason

I have a feature request that’s a little more generic and asks for better and more consistent IF Then logic throughout all of glide.

> [@Better and more consistent IF THEN logic](https://community.glideapps.com/t/better-and-more-consistent-if-then-logic/24317):
>
> I’ve spent the past few days trying to work out some IF/THEN logic for a side project. The problem is that this is something I could have worked out in a matter of a few minutes with actual code. I’m running into several limitations with the current IF/THEN logic we currently have in Glide. First of all there inconsistencies between what’s possible with an IF/THEN column, and what’s possible with If/Then logic in visibility conditions or actions. Most importantly, an IF/THEN column only all…

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [January 17, 2024, 4:52pm UTC](https://community.glideapps.com/t/multiple-conditions-are-met-at-the-same-time-minor-condition/24580/5 "2024-01-17T16:52:51Z")

</div>


