Using an Ajax email handler we have created an object that contains the transcript from a mibew.org chat.

If the contact exists in our database the transcript is attached as an object (and on the contact record as a related list)

If the contact is not in the database the transcript is attached as an object to a new lead.

But upon conversion of that lead, how do we insure that the transcript moves from the lead to the contact?

Or to put it another way -

We want to create a lead that is linked to a chat transcript object & when it is converted the transcript remains linked to the record.

Any suggestions?

  • does it have to be master detail? You could do it with lookups to both objects. I haven't tried with master-detail to both though. – Jonathan Jenkins Jan 18 '13 at 13:36
  • thanks jonathan! right now we are working on using both look ups and master-detail fields. master for the contact and look up for the lead. we've got a lot of orphaned objects in our SFDC instance do to an over use of lookups. – Paul Weaver Jan 18 '13 at 13:45
  • It can't be architected with using master-detail to both due the first requirement where if the contact already exists it associates only to a contact. The master-detail requires that the record be associated to a lead also. You could create a new lead for all then convert the leads that are created for contacts that already exist and see if you can associate the converted lead id in the master-detail. To avoid the orphaned record in junction objects I'd use a validation where either the lead or contact relationship is required. – Jonathan Jenkins Jan 18 '13 at 13:51
  • yes, @JonathanJenkins, it looks like we have to use lookup fields on both contact and leads. – Paul Weaver Jan 18 '13 at 13:56
  • This is not ideal by any means what-so-ever but did you consider about having 2 different chat transcript objects, one detail for contact and lead each? On convert, copy/move from lead detail to contact detail. – Sai Jan 18 '13 at 17:59

Basically, you cannot create a master-detail relationship in which the User or Lead objects are the master, see,

Relationships Among Objects


Also, a idea about this,

Ability to create Master-Detail relationships from Custom Objects to Leads


|improve this answer|||||
  • Yep, we ended up having to go with lookup fields for this little project. thanks to all over here at the stack exchange! – Paul Weaver Jan 23 '13 at 12:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.