How can I put 2 conditions (text and numeric) as independent conditions, and then combined?

Ie, for an example Record which is not working.

I started to get closer. I changed to this, but now the blue is overriding the green:
If(
not IsNull([Time Complete]), "",
(Trim([Van Driver]))<>"" and ([ETA:])>Now() or (([ETA:])<Now() and ToDays([ETA:]-Now())>-1) or ToDays([ETA:]-Now())<0,"#00f6ff",
([ETA:])>Now(),"#08ef08",
([ETA:])<Now() and ToDays([ETA:]-Now())>-1, "#f9fc03",
ToDays([ETA:]-Now())<0,"#fd3110",
IsNull([ETA:]),"#00f6ff")

The line that was not triggering until I moved everything into one string was this one:
(Trim([Van Driver]))<>"" and ([ETA:])>Now() 

I was going to create a separate line for each, but then I decided to string it all together with 'or'. I am trying to make the rows green, red, or yellow based on the time in the 'ETA' field. However, I need the row to display blue if there is no ETA or if the van driver has not been assigned. I can't get the part to work to show blue when the van driver has not been assigned.

i suggest not using the ORs, as for debugging, its best to just list the conditions and results separately.

For the blue when the van driver is blank, is there also an eta condition too? Or is it enough to be blue when the van driver is blank. Right now you have an additional test for the eta.

The ETA should be blank for all of the cases. Here is the formula that works before I add the condition regarding the van driver.


If(
not IsNull([Time Complete]), "",
([ETA:])>Now(),"#08ef08",
([ETA:])<Now() and ToDays([ETA:]-Now())>-1, "#f9fc03",
ToDays([ETA:]-Now())<0,"#fd3110",
IsNull([ETA:]),"#00f6ff")

Here is how it looks. The row in blue shows that the eta is missing. I also need the blue to override the other colors if the van driver is missing.



This is the code that I attempted to add at both the beginning and end of the script. 

(Trim([Van Driver]))<>"" and ([ETA:])>Now() 

Needless to say... It didn't work :(

What field type is Van Driver? If it is a User field type, it needs to be tested with IsNull.

Also, if Van Driver is a text field,  why not just use

Trim([Van Driver])<>"","#00f6ff",

Then I get this:


Not only is the field with no Van Driver not blue, but everything else that shouldn't be - is!

I figured it out!

If(
not IsNull([Time Complete]), "",
(Trim([Van Driver])="" and ([ETA:])>Now()), "#00f6ff",
(Trim([Van Driver])="" and ([ETA:])<Now() and ToDays([ETA:]-Now())>-1),"#00f6ff",
(Trim([Van Driver])="" and ToDays([ETA:]-Now())<0),"#00f6ff",
([ETA:])>Now(),"#08ef08", 
([ETA:])<Now() and ToDays([ETA:]-Now())>-1, "#f9fc03",
ToDays([ETA:]-Now())<0,"#fd3110",
IsNull([ETA:]),"#00f6ff")

Congratulations.
What I often do when using those hex color codes is to add a comment

(Trim([Van Driver])="" and ([ETA:])>Now()), "#00f6ff", // blue

You can add a comment by starting a line with // or even suffixing a line with //, like I did above.

That way when you go back to look at your formula you will remember what those color codes mean.

Great idea! Thank You!