Franks approach is not only clean but you could allow null values in that field if that is the requirement.. with unique index defined on a field you cannot have null values on a field as the second null value will violate the unique index...
And as Frank pointed out its always nicer to have the end user see a message that says "The value you have entered for field Login Name" already exists as opposed to "The unique index on this form has been violated"..
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.
----- Original Message ----
From: Frank Caruso <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 22, 2006 11:06:49 AM
Subject: Re: help, help, help
** 1. You could also do this with work flow to that you can provide a cleaner error message to your end users. Create a filter that does a set fields against the current form looking for the value entered. Set a temp field from the current form if the record is found, NULL if its not. A second filter can check the temp field and if it is not NULL then the value exists and pop up a message to your user.
2. Depends on the type of database. I know with Oracle you can create a SEQUENCE which will give you a new unique value.
--
Frank Caruso
Specific Integration, Inc.
Senior Remedy Engineer
www.specificintegration.com
703-376-1249 __20060125_______________________This posting was submitted with HTML in it___
From: Frank Caruso <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 22, 2006 11:06:49 AM
Subject: Re: help, help, help
** 1. You could also do this with work flow to that you can provide a cleaner error message to your end users. Create a filter that does a set fields against the current form looking for the value entered. Set a temp field from the current form if the record is found, NULL if its not. A second filter can check the temp field and if it is not NULL then the value exists and pop up a message to your user.
2. Depends on the type of database. I know with Oracle you can create a SEQUENCE which will give you a new unique value.
On 8/22/06, Scott Ames <[EMAIL PROTECTED]> wrote:
** Wow you are quick on the draw. I was composing a similar message when yours came in. lol.
"Nall, Roger" < [EMAIL PROTECTED]> wrote:**__20060125_______________________This posting was submitted with HTML in it___Sara,To enforce unique values in a field I would suggest a unique index. As to a 'Request ID' type field you may need some sort of a stored procedure for that.HTH,Roger A. NallOSSNMS Sr. Remedy Administrator/DeveloperT-Mobile USADesk: 973-644-3963Cell: 973-652-6723FAX: 973-267-6628sf49fanv AIM IMRogerNall Yahoo IM
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of sara abate
Sent: Tuesday, August 22, 2006 10:46 AM
To: [email protected]
Subject: help, help, help** I am a new remedy developer and I need help on two of the following things,
1. I want a field to have unique value. How can I restrict the
field from having duplicate values? In other words, Is there any way I can block if the current value entered is already in the database?
2. I want to create an auto generated field. Anytime a ticket is
submitted, the field should be populated automaticlly in increments. In
other word, I want a 'Request ID' kind of field on the form.
Anybody can help me with this please email me at [EMAIL PROTECTED].
I will appreciate it.
Thanks!
Sara
Do you Yahoo!?
Next-gen email? Have it all with the all-new Yahoo! Mail. __20060125_______________________This posting was submitted with HTML in it___
__20060125_______________________This posting was submitted with HTML in it___
--
Frank Caruso
Specific Integration, Inc.
Senior Remedy Engineer
www.specificintegration.com
703-376-1249 __20060125_______________________This posting was submitted with HTML in it___
