If you turn on DB logging, and issue the exact same query as Remedy, what are your results?
From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Charlie Wilson Sent: Wednesday, October 06, 2010 10:04 PM To: arslist@ARSLIST.ORG Subject: Filter Set Fields If No Requests Match null ** ARS 7.5 p6 I am having trouble with a filter. Any tips would be greatly appreciated. 1. Filter fires, qualifies as expected. 2. If action, set fields, source=server/other form I am certain the record(s) do not exist on the source form. However, I get two different results when.. If No Request Match: Set Fields to $NULL$ If Multiple Request Match: Set Fields to $NULL$ The set filter action completes and the field is set to a value. This should not happen. It should be set to NULL. When I make this one change... If No Request Match: Display No Match Error If Multiple Requests Match: Display Multiple Match Error The "no match error" is raised. This helps confirm for me that the set fields action does not qualify. Does this sound like some type of bug? Or, do I not properly understand the "Set Fields to $NULL$"? It seems plain as day what should happen. Thanks, Charlie _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
