Apex Code Development You need to sign in to do that
Don't have an account?
certi_vimal Behaviors of Required fields in Lead and Converted Person Account
Hi,
I have a query regarding Required fields behaviors in Lead and converted Person Account.
Lets say we have 5 required fields in Lead and 10 required fields in Person Account. The Lead is converted to Person Account. All the 5 required fields data of Lead are populated in corresponding Person Account's 5 required fields. BUT, what happens to remaining 5 required fields of Person Account? They remain blank?
Please advise on the behaviour/output of this scenario.
Also, another query is : Does it always be true that Required fields of Lead need to be as Required fields of Account too? Can there be a required field in Lead which is not at all present as field of Account?
Thanks,
Vimal
When you convert from a lead to an account/contact, field requiredness is ignored. This means that the contact or account that is created may have required fields that are still blank. The next time a user attempts to edit the record, they will be required to enter all required fields before they can continue saving the record.
Required fields on leads do not need to be required fields on accounts or contacts. Those fields need not exist at all, and their data will stay with the lead without being stored within an account or contact; you can see this data in a Converted Lead report. This allows you to, for example, collect pre-sales qualification data that won't be needed after the sales process starts.
The only limitation to these rules are standard required fields. Those fields will be filled in on the lead, and their data will carry over to the account and contact without fail. The standard fields include Last Name and Company (Account Name). The company field may be made optional by signing up for Person Accounts; a lead without a contact becomes an account-contact hybrid called a "Person Account."
All Answers
When you convert from a lead to an account/contact, field requiredness is ignored. This means that the contact or account that is created may have required fields that are still blank. The next time a user attempts to edit the record, they will be required to enter all required fields before they can continue saving the record.
Required fields on leads do not need to be required fields on accounts or contacts. Those fields need not exist at all, and their data will stay with the lead without being stored within an account or contact; you can see this data in a Converted Lead report. This allows you to, for example, collect pre-sales qualification data that won't be needed after the sales process starts.
The only limitation to these rules are standard required fields. Those fields will be filled in on the lead, and their data will carry over to the account and contact without fail. The standard fields include Last Name and Company (Account Name). The company field may be made optional by signing up for Person Accounts; a lead without a contact becomes an account-contact hybrid called a "Person Account."
Thanks sfdcfox. Makes sense.
But what about Leads converted via Apex? Curious to know if it will still ignore the extra required fields of Account?
Apex Code follows the same rules as the UI in virtually every case, and this is no exception. Custom required fields will be ignored during conversion initiated from an Apex Code statement, from an API convertLead() call, as well as the UI.