Raj, You mention "pushing". Is your 3rd action a set fields on the same form, or a push to another (audit) form? If its a push, could there be phasing issues in play?
Thad On Tue, Dec 4, 2012 at 7:42 AM, Raj <[email protected]> wrote: > ** 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 ". > > > On Tuesday, December 4, 2012 1:50:21 AM UTC-8, Jiri Pospisil wrote: >> >> ** >> >> 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 >> >> _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"
