Hi Doug,  This sounds like a very familiar ask that I seem to be hearing lately. Not sure if it's the power of WF or the zeitgeist of marketing teams these days. I'd be happy to share my experiences with you. I do advise, often the approach is not to solve but to get it to a livable state.  -Joaquin

If you can see use cases where more than one is filled, then you may want to consider creating a column for each. Depending on your report, it might be best to group so you don't have 12 separate columns. Just one with 12 potential answers. 

Yes, N/A will show when none of the fields are filled out (zero filled). If more than one is filled, it will grab the first one it finds and add that as your return. 

It should work. I tested to make sure there weren't any other surprises.  Here's a couple steps I take when I know an expression should work but some how doesn't....1) Double check the spelling on your custom fields.2) Double check that the fields are filled out. You may need to do a spot check with...

Hi Amoreena,  Wow! Firstly, congrats to your account manager's desire to really get into WF and use it for their overall work management. Brings a tear of joy to my eye.  Secondly, what you're touching on is a bit of work management philosophy and prioritization. Two questions to answer before looki...

Hi Omaha, This is a tricky one. If I recall (and I may be mistaken on this) typeahead fields act a little different than most fillable/selection custom fields. Rather than have the separator "." you should combine the expression field with ":". See my clean up below.  IF(ISBLANK({DE:Typeahead Field ...