Unless you are doing some other work the $NULL$ will look like “” to a human (but not to a system)
‘field’ != ‘DB.field’ should produce the following results: Field DB.Field Result of ‘Field’ != ‘DB.field’ NULL NULL TRUE “” NULL FALSE SomeText NULL FALSE As data is stored in the database the ARS system converts strings of 0 length (empty strings, aka “” ) to NULL. Off the top of my head … Since you want to treat “” the same as NULL you may want to use a Run-If something like ( ‘field’ != ‘DB.field’ ) AND (NOT (( ‘field’ = “” ) AND ( ‘DB.field’ = $NULL$ ))) Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Raj Sent: Tuesday, December 04, 2012 9:42 AM To: [email protected] Subject: Re: 'field' != 'DB.field' ** Thanks Jiri, so from your reply. Then I should see in my Audit log something like this(API pushing ""-zero length character):- "Value changed from to "" " but I do not that, I only see "Value changed from to ". -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jiri Pospisil Sent: Tuesday, December 04, 2012 3:50 AM To: [email protected] Subject: Re: 'field' != 'DB.field' ** Raj, You mentioned API update and from the condition you suggested below, it looks like the update in fact sets the field value to zero length character, i.e. “”. That in my experience is different from NULL value, which would explain why your filter is firing. Also looking at your logic in the filter, to me it seems that the second set field will always result in saying value changes from “new value” to “new value” as I cannot see where the old value would come from. Hope this helps Jiri Pospisil Remedy specialist LCH Clearnet _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
