Thanks for the help everyone,
The problem was the "Record Object Relationships" parameter. This is a development\test server and I had turned this parameter on to trace workflow on another object. The relationships worked great but it apparently takes some load on the system and causes the "unique index" error I got when saving the Active Link. Once I turned off "Record Object Relationships" I was able to save again. I had Development Cache Mode turned on as well. I will probably open a BMC Tech Support ticket on this just to see what they say. Does anyone know if this has been fixed in 8.1? We are at 7.6.4 and will soon migrate to 8.1. I can live with doing "Record Object Relationships" on demand and restart the server, but it is ackward. Thanks again and if I hear anything else, I'll let you know Gordon Frank ----- Original Message ----- From: "Frederick W Grooms" <[email protected]> To: [email protected] Sent: Friday, August 9, 2013 5:58:27 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) ** If you have “mucked” about in the object relationships at the database you need to bounce your system For some reason BMC chose not to use the same logic as next entry id for a form and instead reads the last relationship ID at startup. The server then uses an internal counter to increment the entry ID for the relationships. I suspect they do the same for the other meta data. Fred From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Longwing, Lj Sent: Friday, August 09, 2013 4:19 PM To: [email protected] 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) ** 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 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_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
