Hi,
('AssignedToTech' != 'DB.AssignedToTech') will allways detect a change.
('AssignedToTech' != 'DB.AssignedToTech' AND 'AssignedToTech' != $NULL$)
when you want to check for a change to a non-null-value.
The execution order of your filters, and filter phasing, may play tricks
with you. A value can be changed by another filter after your check was
done.
I suggest that you turn on both API/FLTR/SQL-logging to track this down.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia:
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Oops. I typed the email wrong. I've tried the Run If as been both
> 'TR.AssignedToTech' != 'DB.AssignedToTech' and without the TR in the first
> instance. I'm running a Notify action. I do get inconsistent results.
>
> drew
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
>
> --
> This message was scanned by ESVA and is believed to be clean.
>
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
