Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
An ActivityParty record stores the names of any person referred to in the associated activity. Typically several ActivityParty records can be associated with each activity.
Data in the cdf_ActivityParty table must meet the migration criteria specified in Data Requirements for Migration. The following table shows all of the attributes in Microsoft CRM that can be migrated from the cdf_ActivityParty table and the respective attribute names and types in the CDF database. The table also shows whether the attribute is required and whether it is used to create a relationship with other entities. For drop-down lists and Boolean attributes, the table shows the valid values and the default value in Microsoft CRM. The last rows of the table list the Microsoft CRM ActivityParty attributes that cannot be migrated using the Microsoft CRM Data Migration Framework.
Microsoft CRM tab name and attribute label |
CDF attribute name |
CDF type |
Required or Relationship in CDF |
Valid Microsoft CRM values |
Default Microsoft CRM value |
| Not on tab | ActivityId | int | Required,
Relationship |
||
| ActivityPartyId | int (PK) | Required | |||
| Any party referred to in the Activity 3 | PartyObjectTypeCode1 | int (picklist) | Required | See ObjectTypeCode Values | 2 |
| PartyObjectTypeCodeName2 | nvarchar (200) (picklist) | Account (1)
Contact (2) Lead (4) Opportunity (3) User (8) |
|||
| ID of the party | PartyId | int | Relationship | ||
| PartyIdName2 | nvarchar (2000) | ||||
| Role of the party | ParticipationTypeMask | int | Required | 1 (Sender)
2 (To) 3 (Cc) 4 (Bcc) 5 (Required) 6 (Optional) 7 (Organizer) 8 (Regarding)3 9 (Owner)3 |
|
| E-mail address of the party | AddressUsed4 | nvarchar (2000) |
1 PartyObjectTypeCode data is not in the cdf_StringMapCrm table; you must cleanse the data manually. No default value is used for PartyObjectTypeCode; a value must be specified.
2 The field is used only in the CDF database; it is not migrated.
3 You should create an ActivityParty record for all parties except for the owner of the activity, and the object the activity is regarding. ActivityParty records for the owner and object the activity is regarding are automatically created when the activity is migrated.
4 This attribute needs to be populated only for e-mail activities. If it is blank, Microsoft CRM will assume the party referred to has no e-mail address, and when you go to the activity, you’ll see an error message stating that a recipient does not have an e-mail address. The actual string in AddressUsed is not used; Microsoft CRM uses the e-mail address stored in the record for the referred to contact, lead, account, opportunity or user. You can either populate AddressUsed for all ActivityParty records related to e-mail activities with a string such as the actual e-mail address or “HasEmailAddress”, or write a procedure to check the party’s record and set the AddressUsed value only for those parties with e-mail addresses.