Hi Charlie, Guessing a little here but...
It may be that the value is only set to null if you are setting the field based on the results of the query. You may need to make sure that you retrieve a field value from the query. Setting a field to a constant based on their being a row returned in a query is not supported the way you are expecting. Here's an excerpt from the workflow objects guide Set Fields to $NULL$—Assigns a NULL value to all of the fields that you are setting (except for fields with static values and keywords). Rod On 7 October 2010 12:03, Charlie Wilson <[email protected]> wrote: > ** 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"
