This one that probably often trips people up; if you set the field to null, the TR value will be null.
The TR value represent the current transactions value, if no change occurred in the transaction, then the TR value is null The DB value represents what was last committed to the database; prior to the current transaction The value represents the current value, regardless of the TR or DB values Axton Grams On 10/3/07, Mayfield, Andy L. <[EMAIL PROTECTED]> wrote: > ** > > > > OK, I thought I had this figured. So if while modifying a ticket, you > change a field that previously had a value, to NULL (blank) then the TR > value is NOT NULL. > > > > I need more coffee. > > > > > Andy L. Mayfield > Sr. System Operation Specialist > Alabama Power Company > Office: 8-226-1805 > > ________________________________ > > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza > Sent: Tuesday, October 02, 2007 10:57 PM > > To: [email protected] > Subject: Re: Filter Problem > > > > > > Yes the TR value is NULL if there is no modification even if there is a DB > value to that field.. > > > > > > This is how it works.. when you are submitting a new record, and if there is > a value in the field, then the TR value is not NULL (obviously). The DB > value is always NULL at the time of submission of a ticket (again > obviously). > > > > > > However when you are modifying a ticket, if the DB value is NOT NULL, but > you haven't changed that value, then the TR value is NULL (although that > doesn't look that obvious). > > > > > > When you are modifying the ticket, and the DB value is NOT NULL, and you > change the DB value to a NON NULL value, then the TR value is NOT NULL. > > > > > > Another case is when you are modifying the ticket and the DB value is NOT > NULL, but you change that to a NULL value, then the TR value again is NOT > NULL. > > > > > > > Joe D'Souza > > > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] Behalf Of Mayfield, Andy L. > Sent: Tuesday, October 02, 2007 9:57 PM > To: [email protected] > Subject: Re: Filter Problem > > > I did not realize that the TR. value would = $NULL$ just because it was not > being modified, when it already contained a value. It makes sense now that I > think about it. > > The 'AssignedConfigTech' can possibly be set to $NULL$, but in that case I > do not want the filter to fire. > > Andy L. Mayfield > Sr. System Operation Specialist > Alabama Power Company > Office: 8-226-1805 > > ________________________________ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David > Sent: Tuesday, October 02, 2007 8:04 PM > To: [email protected] > Subject: Re: Filter Problem > > > > > > You need to be careful that the AssignedConfigTech can't be set to NULL. > If it is the TR.AssignedConfigTech will resolve to NULL. > > Dave > -------------------------- > [EMAIL PROTECTED] (Wireless) > __20060125_______________________This posting was submitted > with HTML in it___ __20060125_______________________This > posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
