Well it is coming from the system so it was saved. Certainly this can happen if you created the workflow and then deleted the field. I believe it will be recognized as NULL as well and can be looked at that way to see if it will be used or how it will be used. But I was worried that there might be some strange twist to it. It wouldn't be the first time in my experiences that things didn't act the way I expected.
Thanks, Brian Goralczyk On Tue, Dec 3, 2013 at 10:01 AM, Misi Mladoniczky <[email protected]> wrote: > Hi, > > Definitely an error in the old admin tool. > > Best Regards - Misi, RRR AB, http://rrr.se > > > Pretty sure you'll get an error trying to save it in dev studio. Not sure > > about old admin tool! > > > > Sent from my iPhone > > > >> On Dec 3, 2013, at 10:38 AM, Brian Goralczyk <[email protected] > > > >> wrote: > >> > >> ** > >> Again, I am trying to be lazy and not do the research myself to figure > out > >> what happens, but what if I use a qualification of : > >> Field != non-existent field > >> > >> Would this fire every time? Never? Or sometimes? > >> > >> My instincts tell me that in this case it would fire everytime, but I am > >> looking for some consensus. > >> > >> Thanks. > >> > >> Brian Goralczyk > >> _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > > _______________________________________________________________________________ > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > "Where the Answers Are, and have been for 20 years" > > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
