By planning your import jobs, you can reduce the number of reimport attempts that you have to make. Choose a method for importing your data based on the following questions: Is the data in csv format? Is the data in a SQL Server database? Does the data originate from an LDAP (Lightweight Directory Access Protocol) source, such as Active Directory? Do you expect imports to occur on a scheduled basis? Scheduled imports are performed with the PowerShell cmdlet.
Familiarize yourself with the data being imported so that you can make the right decisions when mapping your data to properties. Are there any missing columns that are required? Are the headers missing? You will need to either add missing fields or skip them during the import. Do you need to change the data to make it valid? Are you going to create new records, update existing records, or do both?
Any import into Service Manager should be performed by someone who belongs to the Service Manager Administrators role. Ensure that your account has the Administrators role before performing an import. Alternatively, if it does not have this role and you attempt an import, a Run As Account (Data Management Administration Account) is automatically substituted. The Run As Account may perform an import, providing it too is configured with a user who has the Administrators role. Refer to the Deployment Guide for more details and instructions on using a Run As Account.
Importing a csv file
Importing SQL Server data
Importing through PowerShell
To import data from a csv file:
To import data from a SQL Server query:
Creating and configuring objects
Error handling options