Understanding the Import Job Data

Article
06/03/2015
2 minutes to read

[Applies to: Microsoft Dynamics CRM 4.0]

Find the latest SDK documentation: CRM 2015 SDK

You can track the progress of an import by looking at the content of the importjob.data property that is updated every time that a component is processed.

In this example, you import the following customizations:

Entities
Nodes
Global settings
Security roles
Workflow

Initially, the importjob.data property contains the following data:

<importexportxml>
  <entities>
    <entity>lead</entity>
    <entity>salesorder</entity>
    <entity>phonecall</entity>
  </entities>
  <nodes>
    <node>isvconfig</node>
    <node>sitemap</node>
    <node>templates</node>
  </nodes>
  <settings>
    <setting>email</setting>
    <setting>general</setting>
  </settings>
  <securityroles>
    <securityrole>{d9d602db-2761-4170-877f-983494567c08}</securityrole>
    <securityrole>{a4be89ff-7c35-4d69-9900-999c3f603e6f}</securityrole>
  </securityroles>
  <workflows>
    <workflow>{3e893809-5f6b-44cd-8982-458eb0abb1a4}</workflow>
  </workflows>
  <languages>
    <language />
  </languages>
</importexportxml>

After the first entity has been successfully imported, the importjob.data property is updated with the following information:

<importexportxml>
  <entities>
    <entity result="success" errorcode="0" errortext="">lead</entity>
    <entity>salesorder</entity>
    <entity>phonecall</entity>
  </entities>
…
</importexportxml>

If an error occurs during an entity import, the importjob.data property is updated with the error information:

<importexportxml>
  <entities>
    <entity result="failure" errorcode="0x80044150" errortext="Invalid column name 'Address1_AddressIdxxxx'.">lead</entity>
    <entity>salesorder</entity>
    <entity>phonecall</entity>
  </entities>
…
</importexportxml>

If there is a warning, the importjob.data property is updated with the warning information:

  <workflows>
    <workflow result="warning" errorcode="0x80048028" errortext="Workflow MyWorkflow cannot be imported because a workflow with the same unique identifier is published on the target system. Unpublish the workflow on the target system before you try to import this workflow again.">{3e893809-5f6b-44cd-8982-458eb0abb1a4}</workflow>
  </workflows>

Here is an example of the importjob.data property content after the import job is finished:

<importexportxml>
  <entities>
    <entity result="success" errorcode="0" errortext="">lead</entity>
    <entity result="success" errorcode="0" errortext="">salesorder</entity>
    <entity result="success" errorcode="0" errortext="">phonecall</entity>
  </entities>
  <nodes>
    <node result="success" errorcode="0" errortext="">isvconfig</node>
    <node result="success" errorcode="0" errortext="">sitemap</node>
    <node result="success" errorcode="0" errortext="">templates</node>
  </nodes>
  <settings>
    <setting result="success" errorcode="0" errortext="">email</setting>
    <setting result="success" errorcode="0" errortext="">general</setting>
  </settings>
  <securityroles>
    <securityrole result="success" errorcode="0" errortext="">{d9d602db-2761-4170-877f-983494567c08}</securityrole>
    <securityrole result="success" errorcode="0" errortext="">{a4be89ff-7c35-4d69-9900-999c3f603e6f}</securityrole>
  </securityroles>
  <workflows>
    <workflow result="warning" errorcode="0x80048028" errortext="Workflow MyWorkflow cannot be imported because a workflow with the same unique identifier is published on the target system. Unpublish the workflow on the target system before you try to import this workflow again.">{3e893809-5f6b-44cd-8982-458eb0abb1a4}</workflow>
  </workflows>
  <languages>
    <language />
  </languages>
</importexportxml>

See Also

Other Resources

Using the Import Job Entity to Track Import Progress