Question: In workflow automation, what does "is more than" mean for a single-option csutom field?
![Ted Youn](https://usericons.pipedrive.com/profile_120x120_8824885_dd6d47a3e34f1d971d4ff120aacb94bc.jpg)
![Fourth Anniversary](https://us.v-cdn.net/6037014/uploads/badges/XDSA1HLKHQGB.png)
![10 Comments](https://us.v-cdn.net/6037014/uploads/badges/XZU7P3QWS9EW.png)
![5 Likes](https://us.v-cdn.net/6037014/uploads/badges/7J49JRQT5YMB.png)
![5 Up Votes](https://us.v-cdn.net/6037014/uploads/badges/T5KOU269BZVN.png)
Greetings,
I have a question on workflow automation, especially on a condition about single-option custom fields.
In my account, each deal has a single-option custom field membership
which can have one of these three values.
- Bronze
- Silver
- Gold
![image](https://us.v-cdn.net/6037014/uploads/5da57ad6db7f757e793ebe1a/posts/618de0ffecd1f8cbbdeb0a1f/618de0ffecd1f8cbbdeb0a1f_46012.png)
This is a sample workflow that is supposed to be initiated when a deal is updated, especially when its custom field membership
is updated.
![image](https://us.v-cdn.net/6037014/uploads/5da57ad6db7f757e793ebe1a/posts/618de06f312a07b0997ed0a4/618de06f312a07b0997ed0a4_98275.png)
But Pipedrive shows that a single-option custom field can have many comparion-based operators such as 'is more than'
or 'was lower than'
.
I don't think we can apply 'is more than'
on a single-option custom field such as the membership
field, but maybe it's because I missed something about workflow automation. What do all these comparison-based operations mean?
![618de0ffecd1f8cbbdeb0a1f_46012.png](https://us.v-cdn.net/6037014/uploads/5da57ad6db7f757e793ebe1a/posts/618de0ffecd1f8cbbdeb0a1f/618de0ffecd1f8cbbdeb0a1f_46012.png)
![618de06f312a07b0997ed0a4_98275.png](https://us.v-cdn.net/6037014/uploads/5da57ad6db7f757e793ebe1a/posts/618de06f312a07b0997ed0a4/618de06f312a07b0997ed0a4_98275.png)
Comments
-
Hi Ted!
Yes, in this case, these "more than" options are not usable for a single-option field. Our system just shows all the available is/was etc options for all the fields, not dependant on the field type itself. Here, you would need to just select what is usable for your specific field and workflow.0 -
Kreete K said:
Hi Ted!
Yes, in this case, these "more than" options are not usable for a single-option field. Our system just shows all the available is/was etc options for all the fields, not dependant on the field type itself. Here, you would need to just select what is usable for your specific field and workflow.Hi, @Kreete K.
"Some of them may not work, so it's up to you. Use them at your own risk" sounds irresponsible.
I believe every user expects to see the usable options only with the unusable options hidden.0