We actually did this, put in the filters to require a unique CI Name per Data Set. It worked, but we ended up taking it out. It just ended up being troublesome. There are other unique identifiers of the CI and trying to force a unique CI name caused undo hardship--particularly with discovery integrations. They match things based on CI Name and/or expect/place particular things in the CI Name and it couldn't use the values we had decided to use in that field.
Hope that made sense, Anne -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Charles Baldi Sent: Monday, August 02, 2010 10:50 AM To: arslist@ARSLIST.ORG Subject: Re: CI Name* should Unique in Asset Manag The CMDB doesn't use NAME as a unique index because you can have multiple records for the same CI (with the same name) in different Data Sets. If you want to prevent a user from entering a duplicate name then you have to do it in workflow. Regards, Chuck Baldi On Mon, Aug 2, 2010 at 10:08 AM, Lammey, Peter A. <peter.a.lam...@espn.com> wrote: > ** > > I agree. The Atrium CMDB application should have made the ID field unique. > It wouldn't be a true ID of an asset if it was not unique and because this > was not enforced in the system, we have had a rash of a number of assets > that were duplicated in the system. > > I don't think Name can be unique. Many times you may just want to > generically give a name to an Asset CI and I should note that this would be > a problem with the Purchase Module workflow since I believe it will stage > the initial CI Names for received assets with the Purchase Line Item > description. > > If you setup filters to produce errors when CI Name is already used the > Receiving workflow from Purchasing would cease to work properly. > > Thanks > Peter Lammey > ESPN IT Packaging and Automation > 860-766-4761 > > > > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Pierson, Shawn > Sent: Monday, August 02, 2010 9:58 AM > To: arslist@ARSLIST.ORG > Subject: Re: CI Name* should Unique in Asset Manag > > > > ** > > I could come up with some quick reasons why it's a bad idea. The most basic > one is that while unique CI Names would be good from the perspective of > managing physical assets, it gets tricky when you talk about things like > software, databases, etc. You could make up a naming convention to populate > it with, such as Visio 2...@pc123456 to indicate that it's a copy of Visio > 2007 on PC123456, but why force yourself to do that? > > > > The Token ID field is good for a unique ID if you need one you can set, > otherwise there is always the Instance ID if you just need it within Asset > Management / CMDB. > > > > Thanks, > > > > Shawn Pierson > > Remedy Developer | Southern Union > > > > From: Action Request System discussion list(ARSList) > [mailto:arsl...@arslist.org] On Behalf Of Rick Cook > Sent: Saturday, July 31, 2010 6:57 AM > To: arslist@ARSLIST.ORG > Subject: Re: CI Name* should Unique in Asset Manag > > > > ** > > Try looking in the AR System Configuration manual. But if you don't know how > to do this basic thing, my guess is that you don't understand WHY you should > or should not do so. Someone with that level of knowledge is likely to do > unintended harm by messing with the CMDB. > > Rick > > ________________________________ > > From: "IT (Amanullah Bashir Ahmed)" <ahmed...@emiratesnbd.com> > > Sender: "Action Request System discussion list(ARSList)" > <arslist@ARSLIST.ORG> > > Date: Sat, 31 Jul 2010 15:00:14 +0400 > > To: <arslist@ARSLIST.ORG> > > ReplyTo: arslist@ARSLIST.ORG > > Subject: CI Name* should Unique in Asset Manag > > > > Hi there, > > Version 7.1 > > > > In Asset Management CI Name* would be unique, how is it possible? > > I want to make CI Name* Unique in Asset Management. Is there any > possibility? > > > > > > > > Thanks & Regards > > > > Amanullah > > > > DISCLAIMER:"This e-mail message including any of its attachments is intended > solely for the addressee(s) and may contain privileged information. If you > are not the addressee or you have received this email message in error, > please notify the sender who will remove your details from its database. You > are not authorized to read, copy, disseminate, distribute or use this e-mail > message or any attachment to it in any manner and must delete the email and > destroy any hard copies of it. This e-mail message does not contain > financial instructions or commitments of any kind. Any views expressed in > this message are those of the individual sender and do not necessarily > reflect the views of Emirates NBD PJSC, or any other related subsidiaries, > entities or persons." > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ > > Private and confidential as detailed here. If you cannot access hyperlink, > please e-mail sender. _attend WWRUG10 www.wwrug.com ARSlist: "Where the > Answers Are"_ > > ________________________________ > > Please consider the environment before printing this e-mail. > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
