autanabp
Has it ever happened to you that when converting a Lead to an organization, contact and / or opportunity, you do not update a field correctly according to the value that brings selected or loaded in the Lead, especially with Picklist type fields?
Recently I almost went crazy and drove support crazy with this incident, emails come and emails goes, and nothing that appeared the origin of the problem, until I finally found the reason for this failure.
The problem is in the fields that have a Default Value established, whether picklist or text type, the problem occurs in any type of data.
When a default value is selected in any field of the entities that are autogenerated with the conversion of the Lead and that in turn this field is mapped for this process, the creation of the new entity will precede its default values for the fields that have it configured, to the value that is selected and that comes from the Lead.
It happened to me with some picklist type fields (but I tell you that it happens with any type of data) in the address of both the client and the contact; in the respective entities I had them set by default city Madrid and the postal code 28001, if in the Lead another value different from these was selected, the entities of organizations and contact me were creating them with the default values (Madrid-28001) and not with those I had selected in the Lead.
Once I removed the default values from the fields involved in Organizations and Contact, surprise, the bug was fixed!, the entities converted from the lead, loaded in the address picklists the values correctly to those selected in the Lead.
I hope this post will help you greatly!!
