The opportunity does not contain the a reference to activity from which it was originated. This is also true for the convert activity button that come out of box.
You started off in the right direction by adding a new toolbar button that triggers the process. What you should do is write a plug-in on the letter activity update message.
You can identify the process by adding a new bit field to the letter entity. When the user clicks on the custom convert to opportunity button you set the bit field to true and do a crmForm.Save() which triggers the update plug-in. E.g.
function CustomConvert()
{
crmForm.new_conversionproc.DataValue = true;
crmForm.new_conversionproc.ForceSubmit = true; // field is disabled by default.
crmForm.Save();
}
Your plug-in then identifies that this is a convert operation by checking that the bit field is true e.g.
If (context.InputParameters.Contains(ParameterName.Target)
{
DynanicEntity Target = context.InputParameters[ParameterName.Target] as DynamicEntity;
If (Target.Properties.Contains(“new_conversionproc”) )
{
Boolean conversionProc = (Boolean)Target.Properties[“new_conversionproc”];
If (conversionProc == true)
{
//conversion here…
}
}
}
Now create a new opportunity with the fields you want to map from the current activity (Target), optionally set the activity regarding object id to the newly created opportunity.
Blog: http://mscrm4ever.blogspot.com/ * Website: http://gicrm.upsite.co.il/
