Re: set fields behavior if no requests match filter

2010-11-08 Thread lisakemes
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

Re: set fields behavior if no requests match filter

2010-11-08 Thread Grooms, Frederick W
@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

Re: set fields behavior if no requests match filter

2010-11-08 Thread Kemes, Lisa
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

Re: set fields behavior if no requests match filter

2010-11-08 Thread Joe Martin D'Souza
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

Re: set fields behavior if no requests match filter

2010-11-08 Thread Grooms, Frederick W
-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

Re: set fields behavior if no requests match filter

2010-10-29 Thread Payne, George
: 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

Re: set fields behavior if no requests match filter

2010-10-29 Thread Brien Dieterle
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

Re: set fields behavior if no requests match filter

2010-10-29 Thread Thad Esser
[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

set fields behavior if no requests match filter

2010-10-28 Thread Brien Dieterle
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