Many thanks to all - and sorry for the slow thank you -

I ended up doing what Guillaume suggested - one filter to check to see if
the record exists, then a set fields to set a hidden field with the value,
then another filter to throw the error message. Problem solved. :-)

Thanks,

Jase :-)

On Fri, Nov 4, 2011 at 2:11 PM, Joe Martin D'Souza <[email protected]>wrote:

> **
>
> I don’t think it will be an issue as such in this particular case. The
> object he is creating in the base mode is an object that did not already
> exist on the form. So it’s a new object altogether, and not a customization
> of an existing object as such.
>
> This is my theory about how it could work..
>
> Create that field in the base mode and create that unique index necessary
> for it.
> Take it out of all views.
> Return to Best Practice mode.
> Overlay the views you want to add that field to, and add that field to
> those views..
>
> This way it should not technically bugger up an upgrade..
>
> I may be wrong, but its something that sounds right theoretically. You
> could try in a test environment, on lets say ITSM 7.6.04 on a form that’s
> changed on SP1, and then upgrade to SP1 and check out the impact of an
> upgrade..
>
> Joe
>
>  *From:* Guillaume Rheault <[email protected]>
> *Sent:* Friday, November 04, 2011 11:21 AM
> *Newsgroups:* public.remedy.arsystem.general
> *To:* [email protected]
> *Subject:* Re: Adding a Unique Index to COM:Company
>
> **
> I would not recommend that... next time he upgrades, he may run into
> issues, since that is an "invalid" customization.
>
> Guillaume
>
>  ------------------------------
> *From:* Action Request System discussion list(ARSList) [
> [email protected]] on behalf of Melissa reed [[email protected]]
> *Sent:* Thursday, November 03, 2011 4:57 PM
> *To:* [email protected]
> *Subject:* Re: Adding a Unique Index to COM:Company
>
>  ** You can create the unique index on the base form, when you take it
> out of best practice mode.
>
>
>
> From:        "Cecil, Ken" <[email protected]>
> To:        [email protected]
> Date:        11/03/2011 03:55 PM
> Subject:        Re: Adding a Unique Index to COM:Company
> Sent by:        "Action Request System discussion list(ARSList)" <
> [email protected]>
> ------------------------------
>
>
>
> **
> Just to confirm I checked and creating more than one unique index on
> COM:Company in 7.5.x was no problem.  So yeah, must be an overlay
> limitation as Guillaume reported.
>
> Ken.
>
> *From:* Action Request System discussion list(ARSList) [
> mailto:[email protected] <[email protected]>] *On Behalf Of *Guillaume
> Rheault*
> Sent:* Thursday, November 03, 2011 4:15 PM*
> To:* [email protected]*
> Subject:* Re: Adding a Unique Index to COM:Company
>
> **
> Hi Jase,
>
> I am 99.9999% sure you cannot create a unique index on an overlaid form,
> that is a known limitation... You can only create unique indexes on custom
> forms.
> So the only thing you can do is create two filters that fire on submit and
> modify:
> 1st one checks whether the value is already present in another record in
> teh same form
> 2nd props the error message
>
> cheers
>
> Guillaume
>
> ------------------------------
>
> *From:* Action Request System discussion list(ARSList) [
> [email protected]] on behalf of Jase Brandon [[email protected]]*
> Sent:* Thursday, November 03, 2011 4:08 PM*
> To:* [email protected]*
> Subject:* Adding a Unique Index to COM:Company
> ** Hello All,
> I need to add a unique index to the COM:Company form to ensure that a
> custom field maintains a distinct value on submit. But.... there is already
> a unique index on the Request ID field on COM:Company, and dev studio won't
> give me the option to add another unique index on the field I want.
> I thought "oh yeah - only one unique index per form", then for jokes n'
> grins - I checked HPD:HelpDesk - which has two unique indexes, both
> character indexes. So that proves more than one unique index is available
> per form. What am I doing wrong? Any suggestions from the gang? :-)
> FYI... COM:Company is already overlaid as well as the view I'm working
> with.
>
> Thanks in Advance,
>
> Jase Brandon
> 7.6.04 SP1
> Windows 2008
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>
> *******************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom
> they are addressed. If you have received this email in error please
> notify the system manager. This footnote also confirms that this
> email message has been swept for the presence of computer viruses.
> www.Hubbell.com - Hubbell Incorporated**
>
>
> _attend WWRUG12 www.wwrug.com  ARSlist: "Where the Answers Are"_
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to