[Date Prev] [Date Next] [Prev in Thread] [Next in Thread] [Date Index] [Thread Index]

Re: SLM Import/Export


If you have already imported ANY data in the past, you could easily be conflicting with it—not just SLAs or OLAs, but actions, milestones, templates, and all the little extra forms.  Removing everything is exceeding difficult.  Also, we use multi-tenancy and let the companies build their own targets and samples.  Because of this some build directly in production others use UAT, so the numbers/record IDs that are used in UAT NEVER match what they will be in production.  Because the import just imports the records from UAT exactly how they are, including the indexes, etc. instead of pushing the relevant info and making the system assign the appropriate values, we can never use the import/export for SLM.  They made some improvements to this tool between 7.0 and 7.1—but not enough.  I don’t know about 7.5, since we aren’t there quite yet.


Anne Ramey


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 only by an authorized State Official.


From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mike Buck
Sent: Thursday, August 12, 2010 7:18 AM
To: arslist@ARSLIST.ORG
Subject: Re: SLM Import/Export


** Thank you Mahendra for responding.  I should perhaps have mentioned that I have deleted all the sample SLM data including templates.

On Thu, Aug 12, 2010 at 11:49 AM, Mahendra Mahalkar <mahendra.mahalkar@gmail.com> wrote:


Hi Mike,

The index violation error may be for the sample data & the few templates which are already there. At one of client, I had to delete the SLM sample data & carried the export/import successfully.



Mahendra Mahalkar            

On Thu, Aug 12, 2010 at 4:03 PM, Mike Buck <beingmikeb@gmail.com> wrote:

** Hi Everyone,

I would be interested in hearing about your experiences in this area.  I am struggling to import SLAs using BMCs Import/Export facility in the Aplication Administration Console in ITSM7.5 with the latest patch.
1.  Measurement & Milestone Templates import ok - great!
2.  Action Templates never get imported
3.  Some SLAs import, but none have any Actions (due to 2)
4.  No SLAs get imported
In all cases the logs say "The value(s) for this entry violate a unique index that has been defined for this form".
Analysing the logs there are numerous forms involved:
The problem seems to originate from association records not getting deleted when a SLM  deletes an SLA, but to identify these records and susequently delete them is a nightmare!!!
It seems this problem has been around since 7.1 (perhaps before?) according to earlier ARSLIST submisisons.  I have so far resisted logging this with BMC as this can be a time consuming process, but find it difficult to imagine that this has not already been submitted.  If this has been around for so long, then why hasn't it been fixed - Perhaps BMC would like to comment on this?
Based on you experiences I would like make an informed decision as to whether I am waisting my time using the BMC Import/Export tool, and move onto something that actually works.  One alternative is to copy & paste, but this is going to burn up the hours/days/months as the number of SLAs could run into thousands.  Another alternative is to spend time analysing and fixing BMC's OOTB application, as this would be faster than a copy & paste solution in the long term, but perhaps someone out there has done this already and is prepared to share the patch?
Thank you for your time & warm regards

Mike _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_