- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi all,
we are struggeling to find the respective config options to take new custom fields, which we have added to the lead form and account table, into consideration when converting leads to accounts using the ootb button/action. We would like to achieve that if converting leads to accounts that the data of these new fields are mapped/transferred too.
Any help would be very much appreciated.
Many thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @chrisanding
To map newly added custom fields from Leads to Accounts during lead conversion using the OOTB action, there are two possible approaches:
-
Dot-walking approach
If the Account record has a reference to the Lead (or vice versa), you can use dot-walking to access and display Lead field values on the Account. However, this only works for reference-based access. -
Script-based field mapping
To actually transfer data, you must explicitly map the custom Lead fields to the corresponding Account fields using script logic. During lead conversion, retrieve the values from the current Lead record and populate the mapped Account fields programmatically (for example, via a Business Rule, Script Include, or customization of the lead conversion logic).
i hope these should be helpful for you.
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Thank You
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @chrisanding
To map newly added custom fields from Leads to Accounts during lead conversion using the OOTB action, there are two possible approaches:
-
Dot-walking approach
If the Account record has a reference to the Lead (or vice versa), you can use dot-walking to access and display Lead field values on the Account. However, this only works for reference-based access. -
Script-based field mapping
To actually transfer data, you must explicitly map the custom Lead fields to the corresponding Account fields using script logic. During lead conversion, retrieve the values from the current Lead record and populate the mapped Account fields programmatically (for example, via a Business Rule, Script Include, or customization of the lead conversion logic).
i hope these should be helpful for you.
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Thank You
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Sanjay191,
the business rule approach worked, thanks! However, there is also a standard procedure for my requirement. The mapping can be found under csm_table_map.list. In the Lead to Account data record, it is possible to create new rows for the custom fields.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Sanjay191,
the business rule approach worked, thanks! However, there is also a standard procedure for my requirement. The mapping can be found under csm_table_map.list. In the Lead to Account data record, it is possible to create new rows for the custom fields.
best regards
