----- Original Message -----
From: Ann McCarthy
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Tuesday, September 28, 1999 4:57 PM
Subject: Filter set fields

Hi all,

ARS 4.0.2
Solaris 7
Oracle 8.1.5

I have two fields

Duplicate Email Address, 536870993 ,Radio Button field
&
Duplicate Email address, 536870994, character field

These fields behave normally in the user tool, however,

I have created a filter that runs on submit and modify, that sets the radio button field to "Yes" and the character field to the $request id$ of the first matching entry with the same email address.

when I select the field name in the set fields action and set the value for the first field, lets say the radio button and "Yes", this is fine. When I select the character field and set the value to $Request ID$ it displays it fine. but when I modify action, it sets both fields to "yes", and even if I set them in the other order, it sets them both to $Request ID$.

I rang Remedy support, and they suggest it is because of database insensitivity, but as I am running Oracle, my database is case sensitive.

Has anyone else come across anything like this

Thanks

Ann McCarthy

different in the field properties.

----- Original Message -----
From: Ann McCarthy
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Tuesday, September 28, 1999 4:57 PM
Subject: Filter set fields

Hi all,

ARS 4.0.2
Solaris 7
Oracle 8.1.5

I have two fields

Duplicate Email Address, 536870993 ,Radio Button field
&
Duplicate Email address, 536870994, character field

These fields behave normally in the user tool, however,

I have created a filter that runs on submit and modify, that sets the radio button field to "Yes" and the character field to the $request id$ of the first matching entry with the same email address.

when I select the field name in the set fields action and set the value for the first field, lets say the radio button and "Yes", this is fine. When I select the character field and set the value to $Request ID$ it displays it fine. but when I modify action, it sets both fields to "yes", and even if I set them in the other order, it sets them both to $Request ID$.

I rang Remedy support, and they suggest it is because of database insensitivity, but as I am running Oracle, my database is case sensitive.

Has anyone else come across anything like this

Thanks

Ann McCarthy