Thanks Chintan for your reply. Yup, I already tried that but I do not see any other workflow firing after this filter and setting the field to NULL.
On Monday, December 3, 2012 8:03:40 PM UTC-8, Chintan Shah wrote: > > ** Hi Raj, > > Can you turn on filter logging to see if there is any other workflow > firing after that audit filter has fired which then sets that field to NULL? > > Thanks > Chintan. > > --- On *Mon, 12/3/12, Raj <[email protected] <javascript:>>* wrote: > > > From: Raj <[email protected] <javascript:>> > Subject: 'field' != 'DB.field' > To: [email protected] <javascript:> > Date: Monday, December 3, 2012, 4:26 PM > > ** 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_ > > _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"
