Create data maps for import
To import data into Common Data Service, you must provide the appropriate data maps.
You can download examples of data maps from Microsoft Downloads: DataImportMaps.zip.
You use data maps to map the data contained in the source file to the Common Data Service entity attributes. You must map every column in the source file to an appropriate attribute. The data in the unmapped columns is not imported during the data import operation.
The data map is represented by the import map (data map) entity. You can create a new map by using the CreateRequest message or update an existing map by using the IOrganizationService.Update method. The map has a unique name that is contained in the
ImportMap.Name attribute. You can specify the name of the import source for which this data map is created by using the
Column, list value, and lookup mappings
To map a column, a list value, or lookup value in the source file to a Common Data Service attribute, use the following mappings:
Maps a column in a source file to a Common Data Service entity attribute. For column mapping, use the column mapping (
ColumnMapping) entity. You can use 1:1 (one-to-one) or 1:N (one-to-many) relationships between source and target attributes. For example, you can map account address information to the billing and shipping addresses in an order.
List Value Mapping
Maps a list value in a source file to a Common Data Service attribute of the OptionSetValue type. For list value mapping, use the picklist mapping (
If a value specified in the source file column is a list value, such as an OptionSetValue, Status, State, and Boolean, you must provide a list value mapping additionally to a column mapping. For example, map the "bill" and "ship" list values in the source file to the bill and ship values of the OptionSetValue type.
Maps a lookup value in a source file to a Common Data Service attribute of the EntityReference type. For lookup mapping, use the lookup mapping (
If the value specified in the source file references an entity, you must provide a lookup mapping for this value. Use the
LookupMapping.LookupSourceCode attribute to specify whether to search for the referenced entity inside the source file or inside Common Data Service. If you are using early bound types, you can use the
LookupSourceType enumeration to set the lookup values. To search inside the source file, use the
LookupSourceType.Source value. To search inside Common Data Service, use the
LookupSourceType.System value. For a list of the LookupSourceCode values, see the picklist values for this entity. To view the entity metadata for your organization, install the Metadata Browser solution described in Browse the metadata for your organization. You can also browse the reference documentation for entities in the Entity Reference. You can provide multiple lookup mappings. The asynchronous transformation job processes all available mappings. It finds the referenced records and updates the parse table with the record unique identifiers. For more information, see Run Data Import.
Use owner mapping to map a user specified in the source file to a user in Common Data Service. For logging information, use the Common Data Service user logon name. For owner mapping, use the owner mapping (
Notes and attachments
Mapping for notes and attachments is handled differently from other entities. Notes and attachments are used to append additional information to a record in Common Data Service. Notes are stored as text and attachments are stored as files in the Common Data Service database.
To create a note in Common Data Service, set the
Annotation.IsDocument attribute in the annotation (note) entity to
false. To create an attachment, set
Use the following settings for mapping notes and attachments:
ColumnMapping.SourceAttributeNameattribute to “
true” or “
false”. The “
true” value indicates an attachment. The “
false” value indicates a note.
ColumnMapping.ProcessCodeattribute to the
ImportProcessCode.Internalvalue of the
ImportProcessCodeenumeration, if you are using early bound types. For a list of the ProcessCode values, see the picklist values for this entity.
If the source data represents a note, map the text of the note to the
Annotation.NoteTextattribute. If you are working with Salesforce files, they are usually stored on the disk under unique identification numbers. To import an attachment, you must map a file identification number that is contained in the source file to the
DocumentBodyattribute stores the contents of the attachment.
The import asynchronous job checks for mappings that have the source attribute name set to “
true” and “
false” to discover notes and attachments. If it finds an attachment mapping, it looks for the specified files on the disk and uploads the file contents as attachments into Common Data Service. If a file is not found, an error is returned.
If you do not provide mapping for an annotation (note) entity, the import job generates a default mapping for the note.
The maximum size of files that can be uploaded is determined by the Organization.MaxUploadFileSize property. This property is set in the Email tab of the System Settings in the Common Data Service application. This setting limits the size of files that can be attached to email messages, notes, and web resources. The default setting is 5 MB. However, an attachment size cannot exceed the maximum HTTP request size (the default is 16MB). For the change to take effect, reset Internet Information Services. To do this, click Start, click Run, type
iisreset, and then click OK.
Import and export data maps
You can export an existing data map to an XML file and import XML data mappings into Common Data Service. To export a data map from Common Data Service, use the ExportMappingsImportMapRequest message. To import XML data mappings and create a data map in Common Data Service, use the ImportMappingsImportMapRequest message.
Prepare source files for import
Add transformation mappings for import
Configure data import
Run data import
Data import entities
Sample: Export and import a data map
Sample: Import data using complex data map