How Status and Status Reason Data Is Imported

Valid values for Status Reason (statuscode) depend on the associated Status (statecode).

To view valid values of Status and Status Reason for each record type, see Default values of Status and Status Reason attributes (Resource Center). How this data is imported depends on whether the information exists in your source files:

• If a source file contains status and status reason columns, do one of the following tasks:
  • In your data map for import, map the values for Status and Status Reason column to valid values by adding a <PickListMap> section for each. More information: Work with Data Maps
  • Prior to importing data, customize the record type to use the same Status Reason values as your source Status Reason column Status values cannot be customized. More information: How List Values Are Imported
• If a source file does not contain Status and Status Reason columns, or you select to ignore these columns during mapping using the Import Data Wizard, when the wizard imports the record, the default Status and Status Reason values are added to the record.

Suggested Preparation in Source Files

If status and status reason data is in your source files, verify that:

• Data in the status and status reason columns matches valid values in Microsoft Dynamics CRM.

  - OR -

• The mapping the values of State and Status in the source file to existing values using a data map.

Example of Using a Data Map to Map Status and Status Reason Values

The following steps show how to edit the data map for two columns in your lead file:

• The Status column maps to the Status (statecode) attribute.
• The Status Reason column maps to the Status Reason (statuscode) attribute.

These steps assume you create your own data map. For details of the data map elements used in the example, see Data Map Schema Reference.

1. Identify valid Status and Status Reason attribute values for the record type. The values are displayed in the following table. Default values are marked with an asterisk (*).

   Status Value	Valid Status Reason Values
   Open (0)*	New (1)* Contacted (2)
   Qualified (1)	Qualified (3)*
   Disqualified (2)	Lost (4)* Cannot Contact (5) No Longer Interested (6) Canceled (7)

2. Identify unique values in your source files, and make a table to identify which source values map to which target values.

   The Status Reason values must map to valid Status values. If your source system Status values do not map 1:1 with Status values, you need to edit your source data to match the structure because Status values are not customizable.

   This example is based on finding records that match the structure using one of the following patterns:

   • Records with New in the Status column, with corresponding Contacted and empty values.
   • Records with empty values in both columns.
   • Records with Not qualified in the Status column, with corresponding Cannot contact and Not interested values in the Status Reason column.
   • Records with no data in either column.

     Status Mapping	Status Reason Mapping	Comment
     "New" and empty --> Open (0)	empty --> New (1) "Contacted" --> Contacted (2)	Since "Contacted" matches Contacted, no mapping is needed.
     "Not Qualified" --> Disqualified (2)	"Cannot contact" --> Cannot Contact (5) "Not interested" --> No Longer Interested (6)	Since "Cannot contact" matches Cannot Contact, no mapping is needed.

3. Do a test import of leads using a file that contains just one record with each status or status reason pair.
4. When you get to the Map Fields wizard page for your Status and Status Reason columns, select Ignore.
5. After the import completes successfully, export your data map.
6. Open the data map using any XML editor A tool designed for editing XML files, such as XML Notepad 2007. XML files can also be edited with any text editor, such as Notepad..
7. In the <EntityMap> section for the Lead record type, find the <SourceAttributeName> elements with a value of Status and Status Reason.

   The data map sections will look like this:

   <AttributeMap>

   <SourceAttributeName>Status</SourceAttributeName>

   <TargetAttributeName></TargetAttributeName>

   <ProcessCode>Ignore</ProcessCode>

   </AttributeMap>

   <AttributeMap>

   <SourceAttributeName>Status Reason</SourceAttributeName>

   <TargetAttributeName></TargetAttributeName>

   <ProcessCode>Ignore</ProcessCode>

   </AttributeMap>

8. Fill in <TargetAttributeName> values with statecode and statuscode, and change the value of <ProcessCode> in both <AttributeMap> sections to Process.

   <AttributeMap>

   <SourceAttributeName>Status</SourceAttributeName>

   <TargetAttributeName>statecode</TargetAttributeName>

   <ProcessCode>Process</ProcessCode>

   </AttributeMap>

   <AttributeMap>

   <SourceAttributeName>Status Reason</SourceAttributeName>

   <TargetAttributeName>statuscode</TargetAttributeName>

   <ProcessCode>Process</ProcessCode>

   </AttributeMap>

9. Look up the integer values for each mapping you need from the table you created in step 3.
10. Add a <PicklistMaps> section for the statecode and statuscode sections, and create one <PicklistMap> element for each value in your source data that needs to be mapped.

    <AttributeMap>

    <SourceAttributeName>Status</SourceAttributeName>

    <TargetAttributeName>statecode</TargetAttributeName>

    <ProcessCode>Process</ProcessCode>

    <PicklistMaps>

    <PicklistMap>

    <SourceValue>New</SourceValue>

    <TargetValue>0</TargetValue>

    <ProcessCode>Process</ProcessCode>

    </PicklistMap>

    <PicklistMap>

    <SourceValue></SourceValue>

    <TargetValue>0</TargetValue>

    <ProcessCode>Process</ProcessCode>

    </PicklistMap>

    <PicklistMap>

    <SourceValue>Not Qualified</SourceValue>

    <TargetValue>2</TargetValue>

    <ProcessCode>Process</ProcessCode>

    </PicklistMap>

    </PicklistMaps>

    </AttributeMap>

    <AttributeMap>

    <SourceAttributeName>Status Reason</SourceAttributeName>

    <TargetAttributeName>statuscode</TargetAttributeName>

    <ProcessCode>Process</ProcessCode>

    <PicklistMaps>

    <PicklistMap>

    <SourceValue></SourceValue>

    <TargetValue>1</TargetValue>

    <ProcessCode>Process</ProcessCode>

    </PicklistMap>

    <PicklistMap>

    <SourceValue>Not Interested</SourceValue>

    <TargetValue>6</TargetValue>

    <ProcessCode>Process</ProcessCode>

    </PicklistMap>

    </PicklistMaps>

    </AttributeMap>

11. Change the Name parameter for the <Map> element. Each data map must have a unique name to be imported.
12. Import the data map.
13. Do another test import using the data map you imported.

Note

• If you create a custom record type and want to import status and status reason data to it, create the record type prior to importing the data to it. More information: How Custom Record types Are Imported