[Applies to: Microsoft Dynamics CRM 4.0]

Default values of Status and Status Reason attributes

Each record in Microsoft Dynamics CRM Online has two attributes to identify the status of the record: Status and Status Reason. If you are planning customization of Microsoft Dynamics CRM Online, deciding when workflow rules are needed, or importing data from a previous customer relationship management (CRM) system to Microsoft Dynamics CRM Online, use the Status and Status Reason reference information in this article in your planning process:

  • The Status Reason values are customizable, so you can use the Customization area to make the values match the terminology you use in your organization, create new Status Reasons, and select the default Status Reason values for each Status. The helpful tables in this article can be used to quickly identify if any Status Reason values need to be customized.
  • You can set up workflow rules whenever a record changes Status or Status Reason. You can use the tables in this article when thinking through which Status and Status Reason changes should trigger a workflow rule.
  • When you import data to Microsoft Dynamics CRM Online, and if your existing data has Status and Status Reason values, you will need to map these values to Microsoft Dynamics CRM Online values. Data without Status and Status Reason values will be imported with the default values shown below.

Default values of Status and Status Reason attributes

The default values of the Status1 and Status Reason1 attributes for each record type are listed in the following sections.

  • In the Status Reason column, the default value is marked with an asterisk (*).
  • Each record type is listed showing its display name and the logical database name. The display name is used if you are working with the record type through the user interface. The logical database name is used if you are working with the record type through the SDK or when manually editing a data map.
  • The integer values for Status and Status Reason attributes are required only if you are importing data and need to manually edit a data map.

Click any of the following links to see valid Status and Status Reason values.

Account (account)

Activity (activitypointer)

Appointment (appointment)

Article (kbarticle)

Campaign (campaign)

Campaign Activity (campaignactivity)

Campaign Response (campaignresponse)

Case (incident)

Case Resolution (incidentresolution, notcustomizable)

Contact (contact)

Contract (contract)

Contract Line (contractdetail)

Currency (transactioncurrency)

Discount (discounttype)

E-mail (email)

Fax (fax)

Invoice (invoice)

Lead (lead)

Letter (letter)

Marketing List (list)

Opportunity (opportunity)

Order (salesorder)

Phone Call (phonecall)

Price List (pricelevel)

Product (product)

Quote (quote)

Service Activity (serviceappointment)

Task (task)

1 Status and Status Reason are stored as four attributes in each database table. If you are working with the record type through the SDK, or are manually editing a data map, you will need to use the logical names shown in the following table, rather than the display names of the attributes.

Status: Integer attribute


Status: String attribute


Status Reason: Integer attribute


Status Reason: String attribute


Related Links