Yup, that should lead right the problem. We had an odd issue upgrading AR 7.5 to 7.6.04. I don't remember if it was an unique index error but it was a SQL error that was thrown during the install. The installer was erroring on a view form and we couldn't delete with Dev Studio. I tried the Admin Tool and was able to remove the form. SQL logging was the hero in unraveling that mystery during the install and I also watched the SQL log when I deleted the form via the Admin Tool (in test first) to make sure it was not causing any further harm.
In that same upgrade we had a few filters that also were triggering unique index errors. 7.6.04 was adding a unique index to the meta data tables. Somehow in the past we were able to create filters with duplicate references that are no longer allowed at the db level. On Fri, Aug 9, 2013 at 2:19 PM, Longwing, Lj <[email protected]> wrote: > ** > were you saving a Form or an Active Link?...I still recommend turning on > SQL logging to figure out what form has the unique index it's complaining > about. I have personally come across this when saving a form, on the > unique index on schema_index on overlaid forms.. > > > On Fri, Aug 9, 2013 at 3:16 PM, gjjmss <[email protected]> wrote: > >> ** >> >> We got this just renaming a button >> >> >> >> Gordon >> >> >> **Sent from my Verizon Wireless 4G LTE Smartphone.** >> >> >> >> ------ Original message ------ >> >> If you don't see that active link name in the list of active links, there >> could be a cache problem. I've had similar things happen where I had to >> remove the cache in the Dev Studio workspace and then log back into the >> server and bring the list back up. >> >> ----- Original Message ----- >> From: "Rick Cook" ** >> >> To: [email protected] >> Sent: Friday, August 9, 2013 3:30:08 PM >> Subject: Re: The value(s) for this entry violate a unique index that has >> been defined for this form, 382 when saving an Active Link (UNCLASSIFIED) >> >> ** >> Like LJ said, it's not Java. There is, in the metadata, an Active Link with >> the same name as the one you're saving. I did think about the possibility >> that an action in the Active Link might cause that error, but I don't think >> so. Only adding a Unique attribute to an index would give you that if it >> were anything but a duplicate AL name. >> >> Rick >> >> >> >> >> On Fri, Aug 9, 2013 at 12:23 PM, Gordon Frank < [email protected] > wrote: >> >> >> ** >> >> >> Sorry, I forgot to change the subject line on the original >> >> -----Original Message----- >> From: [email protected] [mailto: [email protected] ] >> Sent: Friday, August 09, 2013 3:18 PM >> To: [email protected] >> Cc: Frank, Gordon M CTR (US) >> Subject: Re: SLM 7.6.04 Service Target Milestones not appearing on Incident >> >> Has anybody seen this: >> >> >> >> The value(s) for this entry violate a unique index that has been defined for >> this form, 382, >> >> >> >> When trying to save an Active Link within Developer Studio 7.6.4? >> >> >> >> I get a feeling its a Java issue. >> >> >> >> If you know the correction, I would appreciate the feedback. >> >> >> >> Thanks >> >> >> >> Gordon Frank >> >> >> Classification: UNCLASSIFIED >> Caveats: NONE >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> _______________________________________________________________________________ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> "Where the Answers Are, and have been for 20 years" >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
