You're right. Thanks. I was thinking in the limited context of a simple save from a form. Strictly speaking, I believe that TR.<field> has a value any time a value is explicitly being set (whether it is being changed or not). From a normal form save, that will only happen when the value is actually "changed" on the form (perhaps anytime the change flag has been set on the field). In a push fields, API action, or other where a value is being specified for a field, TR.<field> will be non-null (unless null is what was specified).
Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Thad K Esser Sent: Tuesday, September 29, 2009 10:50 AM To: [email protected] Subject: Re: Stumped - Need some fresh eyes Lyle> "(TR.Billing_End_Date will always be NULL unless the value is being changed to something non-null)" Note: The TR value could be non-null, whether or not the value is different, if its used in a push fields from some other form. Thad Esser Remedy Developer "Now... Just where did I put that cheese...?" |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Lyle Taylor <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |[email protected] | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |09/28/2009 02:32 PM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: Stumped - Need some fresh eyes | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Sent by: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Action Request System discussion list(ARSList)" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| ** Actually, that would fire any time the Billing_End_Date didn’t change or was set to NULL (TR.Billing_End_Date will always be NULL unless the value is being changed to something non-null). He doesn’t need to determine when it’s null, just if it is being changed. In that case, since it does correctly fire in one case (where it’s null in the DB but no in the updated record), it should also fire the other way around as well. If it doesn’t, then that would probably be a bug and not be related to the NULL value relational Algebra. I think the relational Algebra discussion relates more to searches and may not apply here in this context. (I could be wrong on that point, but my first point above is correct.) Lyle *IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature. * NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
