Hi Raj, Your understanding of field != DB.field is correct. It should not be capturing a change from NULL to NULL. You have something else going on here.
Maybe the way you are displaying the value isn't capturing the difference? I have used this condition on all versions of ARS from 4.5 to 8 and it always works the way i expect it to. Rod On 4 December 2012 08:26, Raj <[email protected]> wrote: > ** Hi, > I have gone through various discussions on 'field' != 'DB.field' on the > forum here but still little confused. > Currently, we have a code 'field' != 'DB.field' and looks like it tracks > all changes to the field. > It is even tracking null value change as well. > For Example, I am updating Audit log something like "value changed from A > to B". > But I do see entries of "value changed from to " > > Would this Run If qual in filter also tracks when a null is pushed to this > field from API. > My understanding is when a null is pushed, field has a transaction value > of null but which is = to DB.field, then why is this filter firing? > Did anyone encounter such a case? > As I would like to stop logging "value changed from to " in the audit, > as it is of no use. > Pl advise. > Thanks, > Raj > _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"
