Mobile no copy across when converting lead

HI

ive added a mobile no field to the lead person screen - is it possible this field can copy across into the person mobile no field when adding the company/person record?

Many Thanks

Top Replies

  • Reading this link doesn't make it particularly clear.

    The text that says:

    The phone, alternative phone, and email fields are all set to map to the standard phone, alternative phone, and email fields…

Parents
  • 0

    Reading this link doesn't make it particularly clear.

    The text that says:

    The phone, alternative phone, and email fields are all set to map to the standard phone, alternative phone, and email fields. Only hardcoded values can be used for these fields.

    is the key part to this. The trouble is, this text has always been in the help files and it just isn't clear. Does it mean that you can or can't? If you can't map additional phone/email fields to person and/or company records, then it would be nice for the help file to just say that. If you can, some explanation of how it can be achieved would be useful.

    Mapping custom fields from a lead to a person or company is all done with proper naming of the fields and the DLL does the rest. Personally, I would have thought a simple mapping screen would have been easier, but it's been this way as long as I've been using Sage CRM which is from about 5.6 days. That said, phone and email fields are just a bit different. More so since the denormalisation of the database to remove the field from the primary records.

    That said, I've always ended up doing it via table scripts. It's been a long time since I did it last and I've moved companies a couple of times since I last did it so I don't have the code to hand.

  • 0 in reply to Vega

    I completely agree, some kind of mapping 'wizard' would be so much easier, a bit like Lead to Opportunity you can Map fields. this way you could map any field on a lead to any field on company/person/phone/email - handy if it's an old system and proper naming conventions weren't follow when a custom field was created.

    In the past we've always had to write something to read something as 'simple' as a mobile phone in order to populate it on person. 

Reply
  • 0 in reply to Vega

    I completely agree, some kind of mapping 'wizard' would be so much easier, a bit like Lead to Opportunity you can Map fields. this way you could map any field on a lead to any field on company/person/phone/email - handy if it's an old system and proper naming conventions weren't follow when a custom field was created.

    In the past we've always had to write something to read something as 'simple' as a mobile phone in order to populate it on person. 

Children