When you execute an offer activity based on an offer that supports the Microsoft Dynamics CRM delivery method, the actions undertaken at Microsoft Dynamics CRM largely depend on whether the offer was defined as creating a new Microsoft Dynamics CRM campaign.
If the offer was configured to create a new campaign, a new Microsoft Dynamics CRM campaign is created using the Microsoft Dynamics CRM credentials defined at the channel. Its properties are accordant with the offer’s settings.
If the offer was configured to use an existing campaign, an existing Microsoft Dynamics CRM campaign is used.
If the Microsoft Dynamics CRM channel’s Data to synchronize property is set to Lead, RPI records targeted by the Microsoft Dynamics CRM offer are created as leads in Microsoft Dynamics CRM, and associated with the new campaign.
Additional custom data fields ChannelExecutionID and RPContactID are created in campaign, contact and lead data objects at Microsoft Dynamics CRM only if they do not already exist.
When a new value was specified at an offer’s Lead Source, the value is created either at the Lead or Contact lead source lookup at Microsoft Dynamics CRM.
When creating a lead, the offer's Lead Status value will be used in preference to any Lead Status mapping as defined at the channel’s Field Parameters.
When campaign members are created, they will be reflected as Lead and Contact data objects at Microsoft Dynamics CRM
For campaign members only raw database, and not translated, values are used.
A system pulse is generated on the successful upload of data to Microsoft Dynamics CRM:
'[n] lead(s) | contact(s) has | have been uploaded via channel [Channel Name] as part of offer 'Offer Name' by activity 'Activity Name' in interaction 'Interaction Name'.
At execution of at Microsoft Dynamics CRM channel synchronization system task:
•A new table called RPI_MSCRM[LD|CT]_<TableName>_<CRM Account hash code>is created on in the client's data warehouse. Its table definition is based on the channel’s Field parameters column mapping.
•Only records that were created by Microsoft Dynamics CRM are written to the table.
•Each time the task runs, the table is dropped and re-recreated if a table with the same name exists. Prior to the original table being dropped, a latest copy of the records from Microsoft Dynamics CRM are downloaded first.
•If Allow update is checked at the channel configuration, only records created via RPI are used to facilitate the write back of updates to the data warehouse.