Sign in
 
Home2012Previous VersionsLibraryForumsGallery
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
System Center TechCenter >
> 
> 
Importing Incidents from another ticket system - Fails on Classification

Answered Importing Incidents from another ticket system - Fails on Classification

  • Tuesday, May 18, 2010 11:03 PM
     
      Has Code
    Sign In to Vote
    0

    I've exported my incidents from Altiris and created my data and format files.  When I import the data file without the classification, it works fine.  I've customized my classification list and Infrastructure is new.

    When I add clasification to the mix, it fails with this error:

     

    Creating new CSVImporter 

     

    dataFileName: C:\Users\dsigmon\Desktop\Incident Import\AltirisExtract.csv

    formatFileName: C:\Users\dsigmon\Desktop\Incident Import\AltirisExtract.xml

     

    Validating against XSD schema...

    Validation completed.

    An item with the same key has already been added.


    Could not initialize a Management Object Creator from format file C:\Users\dsigmon\Desktop\Incident Import\AltirisExtract.xml. Import thread exiting.

     

    Format File code here

    <CSVImportFormat>
 <Projection Type="System.WorkItem.Incident.ProjectionType">
  <Seed>
   <Class Type="System.WorkItem.Incident">
    <Property ID="Id"/>
	<Property ID="Urgency" />
    <Property ID="Impact"/>
    <Property ID="ContactMethod"/>
	<Property ID="Title" />
	<Property ID="Status" />
	<Property ID="Classification" />

    </Class>
  </Seed>
  <Component Alias="AffectedUser">
   <Seed>
    <Class Type="System.Domain.User">
     <Property ID="Domain"/>
     <Property ID="UserName"/>
    </Class>
   </Seed>
  </Component>

  <Component Alias="AssignedUser">
   <Seed>
    <Class Type="System.Domain.User">
     <Property ID="Domain"/>
     <Property ID="UserName"/>
    </Class>
   </Seed>
  </Component>
 </Projection>
</CSVImportFormat>

    Data file here.

    ALT{0},System.WorkItem.TroubleTicket.UrgencyEnum.High,System.WorkItem.TroubleTicket.ImpactEnum.High,Import,SES IT Server Consolidation/Relocation to Stamford,IncidentStatusEnum.Active,System.WorkItem.TroubleTicket.IncidentClassificationEnum.Infrastructure,Dallas,bsmith,Dallas,tjones

     

     

All Replies

  • Wednesday, May 19, 2010 4:14 AM
    Answerer
     
     
    Sign In to Vote
    0
    Hi, do you use ID for classification? If you look at http://contoso.se/blog/?p=1285 I have some info there about the localization table and that I use ID instead of values when I configure different category and classification.
    Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
     
  • Wednesday, May 19, 2010 5:34 PM
     
     
    Sign In to Vote
    0

    Thanks Anders.  I'll dig out my ID's and let you know how it goes.  

     

    DS

     
  • Wednesday, May 19, 2010 10:52 PM
     
      Has Code
    Sign In to Vote
    0

    Anders, no luck.  We exported the info from the database:

     

     

    LTStringId						ElementName						LTValue
0152BFD1-FB23-E53D-5C14-82CC9833DEC1	Outage.Application.Allegro.Enum		Allegro
F85DA9C6-6CB7-0890-EC29-94D1910EF1C0	Outage.Application.Enum				Application
F46054C0-828C-3E31-7156-6E930555CCD2	Outage.Application.Excelergy.Enum		Excelergy
8D6D1523-0626-7C3E-FE99-26332A756031	Outage.Application.iAvenue.Enum		iAvenue
9D7C3AE6-43AD-3F0D-86EC-71A4AEA0A56C	Outage.Application.InData.Enum		InData
277DEC1E-3528-FA47-6020-BB03AEE77032	Outage.Application.Informatica.Enum		Informatica
977739C0-A43B-F2FD-2F45-6B37A8FFE8BC	Outage.Application.InPricing.Enum		InPricing
439C247C-B6F7-9B74-7105-EA11373CC540	Outage.Application.InRetail.Enum		InRetail
02738DF0-9B4B-05CE-8C87-214C3815D7D1	Outage.Application.LODESTAR.Enum		LODESTAR
AD510624-1BA4-4D0E-1FFB-0B102EF6C102	Outage.Application.MetrixIDR.Enum		MetrixIDR
37CFDC96-AF05-B27B-4651-14F7064874CB	Outage.Application.nMOSA.Enum			nMOSA
E24505A8-AB31-C802-5CAE-D77AD744DC60	Outage.Application.Panorama.Enum		Panorama
24D2E2F7-016F-1BB3-ADA9-D64735F28173	Outage.Application.PriceFeeds.Enum		Price Feeds
92D35382-D69A-3759-A371-3E5A235259CA	Outage.Application.PriceWarehouse.Enum	Price Warehouse
A3D71814-5CC9-9738-E485-3AB5AEDD7956	Outage.Application.RAM.Enum			RAM
E55848BB-BD0E-3489-B4B6-5E2D84694E09	Outage.Application.RevenueManager.Enum	RevenueManager
594EE478-A5DB-8E2F-B532-F3732B5A74EA	Outage.Application.SterlingGentran.Enum	Sterling Gentran
B97477D7-093C-4B91-1FCA-EF76AF78CC8E	Outage.BES.Enum					BES
D8D3AA29-F19F-5628-6F7B-334D0D914B6A	Outage.Enum						Outage
77329F6F-14E2-2E13-EDD0-DD503DD0630E	Outage.Facilities.Enum				Facilities
8F643122-E107-1901-30D8-D710ACDEDB8B	Outage.Infrastructure.Enum			Infrastructure
B3B841DC-C39B-1AFF-114B-7A3BE8B4E784	Outage.Infrastructure.Network.Enum		Network
940F77F7-BF39-C66E-AF97-3F1C0236AE71	Outage.Infrastructure.Server.Enum		Server

     

    Inserted it into the data file:

     

     

    {0},System.WorkItem.TroubleTicket.UrgencyEnum.High,System.WorkItem.TroubleTicket.ImpactEnum.High,Import,SES IT Server Consolidation Relocation to Stamford,IncidentStatusEnum.Active, D8D3AA29-F19F-5628-6F7B-334D0D914B6A

     

    Heres' the format file:

     

     

    <CSVImportFormat>
 <Projection Type="System.WorkItem.Incident.ProjectionType">
  <Seed>
   <Class Type="System.WorkItem.Incident">
    <Property ID="Id"/>
	<Property ID="Urgency" />
    <Property ID="Impact"/>
    <Property ID="ContactMethod"/>
	<Property ID="Title" />
	<Property ID="Status" />

	<Property ID="Classification" />
    </Class>
  </Seed>
  

 </Projection>
</CSVImportFormat>

     

     
  • Thursday, September 30, 2010 3:38 PM
    Owner
     
     Answered
    Sign In to Vote
    0
    Looks like you are trying to set it to the root enum value.  Try setting it to one of the actual values (basically any GUID above except the one you chose :))
    Travis Wright Senior Program Manager Lead Microsoft
     
  • Tuesday, October 05, 2010 8:47 PM
     
     Proposed
    Sign In to Vote
    0

    I have two different experiencies for this.
    In "domain A" it worked with CSV import if I used the EnumId, but in "domain B" I had the same error that you have.

    My solution was to import all incidents without specifying classification and then add classification to all imported incidents with Powershell.
    I created a ps1 file with one row for every incident that looked like this:

    Set-SCSMIncident -ID IR10 -Classification 806D96A9-7EDC-3646-0069-FEE2A89B2043
    Set-SCSMIncident -ID IR11 -Classification 806D96A9-7EDC-3646-0069-FEE2A89B2043

    Stefan Allansson, Lumagate. www.lumagate.com
    • Proposed As Answer by Stefan Allansson Wednesday, October 06, 2010 10:46 AM
    •