Have three-state fields been considered for InfoQube?
I use yes/no fields to track various kinds of work and I often find that I need it to track three conditions, not just two =
1) Yes
2) No
3) Not checked yet (ie unknown if item's condition is a yes or no)
So I end having to use two columns to track one set of conditions, which seems inefficient.
I have no idea if it'd be worthwhile to consider them. I had a list program that had them and I found them useful (I thought it was ListPro but I just downloaded the current version and I don't see them).
Wayne
Suggestions
Comments
Hi Wayne, Yes/No fields are…
Hi Wayne,
Yes/No fields are just that, 2 states. I can think of 2 ways to achieve this:
HTH !
Pierre_Admin
IQ Designer
@Wayne, I have a similar…
@Wayne,
I have a similar situation with a date field. Sometimes the date is unknown, so I needed to two fields: Date & Unknown (a Yes/No Field)
I wish that the date field had an "unknown" option. I don't like to use a text field for dates, cause I often mistype the date in a text field....(I am a terrible typist)...
For dates, why leaving it…
For dates, why leaving it blank doesn't it work for you. It should be the equivalent of "unknown"
If I leave it blank, I don't…
If I leave it blank, I don't know if I forgot to add it (or I didn't enter the due date yet and I need to add it later).
If the unknown yes/no field is checked, I know that item truly doesn't have a due date or it is unknown.
it is easy enough to add a…
it is easy enough to add a note to the item w.r.t. the state (can use the built-in Notes field). Let's not make things overly complicated when there are simple ways to handle special cases