Transferring leads

In order to move leads from one linked campaign to another (regardless of tenant), each must be removed from the source linked campaign and added to the target linked campaign.

There are several possible mechanisms for doing this, two of which are:
1.	APIs that modify and add individual records to  an active campaign:
a.	CM:DE:IR (Insert Record),
b.	CM:DE:UR (Update Record)
This method has the advantage that both the database tables and the cache are updated as necessary automatically.

However, there is no mechanism to delete a record. So the process would be to update records with a disposition that prevents calling in the source campaign and insertion of copies of the images into the destination campaign. This may introduce some complex corner cases, e.g. a record is moved from campaign A to campaign B and back to A.

2.	Updating the <campaign>_list tables directly - This method has some additional complexities:
a.	Before updating, the process must:
¥	issue the CM:DE:CU (Close Cursor) SDMP message;
¥	Wait for the CM:DE:NU (Now Unloaded) acknowledgement from CM (campaign manager)
¥	Issue the update
¥	Upon completion, issue CM:DE:RL (Reload) to force reload of the primary cursor
b.	Records already in the cache may not be updated. When records are cached, <switch_result_col> is set to a negative integer value. These records may not be updated.
3.	If it is necessary to update records that are already cached, these need to be handled individually via the CM:DE:UR (Update Record) message.