this message in context:
http://ars-action-request-system.1093659.n2.nabble.com/set-fields-behavior-if-no-requests-match-filter-tp5684874p5718896.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com
@ARSLIST.ORG
Subject: Re: set fields behavior if no requests match filter
I'm having a hard time even getting to stage one where you are looking for a
duplicate value on the same field on the same form. When I create my
Filter, I have one Action as well - Set Fields. The Server Name is the
correct
Sent: Monday, November 08, 2010 5:25 PM
To: arslist@ARSLIST.ORG
Subject: Re: set fields behavior if no requests match filter
And the another field is being set with a value from the form like requestid
(and not static text)?
Fred
-Original Message-
From: Action Request System discussion
message..
Joe
-Original Message-
From: lisakemes
Sent: Monday, November 08, 2010 5:13 PM Newsgroups:
public.remedy.arsystem.general
To: arslist@ARSLIST.ORG
Subject: Re: set fields behavior if no requests match filter
I'm having a hard time even getting to stage one where you are looking
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Joe Martin D'Souza
Sent: Monday, November 08, 2010 4:29 PM
To: arslist@ARSLIST.ORG
Subject: Re: set fields behavior if no requests match filter
Looks like what you are trying to do
: Thursday, October 28, 2010 7:58 PM
To: arslist@ARSLIST.ORG
Subject: set fields behavior if no requests match filter
Is it normal for a set fields operation, which is set to Set Fields to
$NULL$ if no records match, to actually set the fields anyway if no
records match? I didn't think so. Here
Request System discussion list(ARSList) [arsl...@arslist.org] On
Behalf Of Brien Dieterle [brien.diete...@cgcmail.maricopa.edu]
Sent: Thursday, October 28, 2010 7:58 PM
To: arslist@ARSLIST.ORG
Subject: set fields behavior if no requests match filter
Is it normal for a set fields operation, which
[brien.diete...@cgcmail.maricopa.edu]
Sent: Thursday, October 28, 2010 7:58 PM
To: arslist@ARSLIST.ORG
Subject: set fields behavior if no requests match filter
Is it normal for a set fields operation, which is set to Set Fields to
$NULL$ if no records match, to actually set the fields anyway
Is it normal for a set fields operation, which is set to Set Fields to
$NULL$ if no records match, to actually set the fields anyway if no
records match? I didn't think so. Here is the scenario:
I have Form A with a 'Field 1' character field and a 'NotUnique'
character field. I want a set
9 matches
Mail list logo