Depending on the potential values that are in Y & Z (maybe a record exists but Y & Z are NULL), I would probably set a temp field to the Request ID and then check the temp field in AL2. That way you know if its null, a record wasn't found.
Thad "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "LAU, DARREN (ASI)" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 11/29/2006 03:05 PM Please respond to [email protected] To [email protected] cc Subject Re: Set Fields to $NULL$ setting field to SPACE character ** Thanks Thad. I never saw it that way before. Now it all makes sense. Looks like I just need to adjust my workflow here then to look for the space character and then clear it out if necessary. Thanks again. I submitted an issue to Remedy so I?ll see what they say first and will post back. Darren Lau From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thad Esser Sent: Wednesday, November 29, 2006 2:57 PM To: [email protected] Subject: Re: Set Fields to $NULL$ setting field to SPACE character ** Darren, I'm not sure if it is a bug or not, but it is a subtlety that has existed for awhile. I interpreted the issue that the word "Fields" in "Set Fields to $NULL$" refers to the fields that are being read (Y & Z in your example), not the fields that are being set (X in your example). To demonstrate this in your example 'Set Fields', add another field and set it with a constant: FieldW = "any fixed text". Regardless if a match is found or not, FieldW will get set with "any fixed text". I hope that helps. Thad "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "LAU, DARREN (ASI)" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 11/29/2006 02:43 PM Please respond to [email protected] To [email protected] cc Subject Set Fields to $NULL$ setting field to SPACE character ** Listers, ARS 7.0 Patch 1 Oracle 9.2.0.8.0/ 10gR2 Client Win 2K3 Got a strange one on hand that might be a bug. Here?s the situation. I have two active links, AL1 and AL2. AL1 will run first and do a set fields action on Field X by looking up against some form. If no requests match set fields to $NULL$. If one requests match set Field X to ($Field Y$ + ? ? + $Field Z$). AL2 will run second if Field X is $NULL$. My problem is when the set fields action in AL1 does not match any requests. Instead of setting field X to $NULL$ it sets it to a SPACE character. Thus my actions in AL2 will never run when it should. Now if I change the set fields action in AL1 from ?Field X? = ($Field Y$ + ? ? + $Field Z$) to something without the space like ?Field X? = $Field Y$ then the AL?s work as expected. I?m very sure the ? ? (SPACE character) in the concatenation of Field Y and Z is part of the problem even though it should not. This behavior happens in the User Tool and Mid-Tier. I?m very sure this a bug. Has someone encountered this before and if so is there a fix? TIA. Darren Lau __20060125_______________________This posting was submitted with HTML in it___ ***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.*** __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ***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.*** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
