I believe if you type in the name over again, even if it matches the old
value, it will still push data. Which is why you usually check to see if
it matches the db as well as the transaction value.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Atul Vohra
Sent: Tuesday, October 02, 2007 4:55 PM
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
**
What would happen if someone typed the same value in the field
(or select the same value) will TR value be NULL in that case?
----- Original Message -----
From: YHK
To: arslist@ARSLIST.ORG
Subject: Re: Filter Problem
Date: Tue, 2 Oct 2007 19:41:44 -0400
** Just ( 'TR.AssignedConfigTech' != $NULL$ ) would
work, right?
On 10/2/07, Atul Vohra <[EMAIL PROTECTED]>
wrote:
**
( 'AssignedConfigTech' != $NULL$ ) AND (
'DB.AssignedConfigTech' != 'TR.AssignedConfigTech')
When that field is not changed then '
TR.AssignedConfigTech' = $NULL$ while 'DB.AssignedConfigTech' != $NULL$
thus the filter fires.
This qual should work
( 'AssignedConfigTech' != $NULL$ ) AND (
'DB.AssignedConfigTech' != 'AssignedConfigTech')
Regards
Atul
----- Original Message -----
From: "Mayfield, Andy L."
To: arslist@ARSLIST.ORG
Subject: Filter Problem
Date: Tue, 2 Oct 2007 18:04:16 -0500
**
OK, I am stumped. I have a filter firing
that should not be.
I have a filter that sends a
notification based on the qualification statement:
( 'AssignedConfigTech' != $NULL$ ) AND
( 'DB.AssignedConfigTech' != 'TR.AssignedConfigTech')
If I am reading the statement correctly,
the filter should not fire unless the 'AssignedConfigTech' is changed.
This filter is firing when the form is
saved without a change being made the 'AssignedConfigTech' field.
There is a value in the field, so it's
!= $NULL$, but no change is being made to the field so it should not
meet the criteria.
Andy L. Mayfield
Sr. System Operation Specialist
Alabama Power Company
Office: 8-226-1805
Cell: 288-9140
SoLinc: 19140
__20060125_______________________This
posting was submitted with HTML in it___
__20060125_______________________This posting
was submitted with HTML in it___
__20060125_______________________This posting was
submitted with HTML in it___
__20060125_______________________This posting was submitted with
HTML in it___
This message and any attachments are for the intended recipient(s) only and may
contain privileged, confidential and/or proprietary information about Downey
Savings or its customers, which Downey Savings does not intend to disclose to
the public. If you received this message by mistake, please notify the sender
by reply e-mail and delete the message and attachments.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
