Salesforce IdeaExchange
- then -
Marketing Automation Comments
| Marketing Automation Ideas
|
Applications Comments
| Applications Ideas
Map Lead fields to more than one object
I just hate being limited to a 1 on 1 mapping of fields upon conversion. Why can't I map a lead field to an account AND a contact, as is already possible for some standard fields (e.g. addresses)?
|
Ali_J_in_NH 10/12/06 |
Completely agree on this one . . . would be fantastic, and would end terribly kludgy ISPICKVAL workarounds. |
|
ttt 10/12/06 |
You can do this in some way today using formula fields not shown on the page layouts, and assigning those custom fields to other fields on the target objects. |
|
ErikM 10/12/06 |
That was a very useful suggestion, thanks ttt. Still, having multiple assignments would be much more straightforward. |
|
hemm 01/05/07 |
2 issues at play here: 1) related to ttt's solution: When I have tried this in the past, Salesforce balks because it says a 1300 character formula cannot map to a 100 character text field. Even though no formulas result in 1300 characters, SFDC thinks it does. 2) if we could get past that, we then have a problem with ISPICKVAL. Example: For several clients, we have used custom address fields and we use a picklist for country names. To get the value of a picklist field in a formula, you cannot simply reference the value. You have to use a Case statement and ISPICKVAL for every picklist value to output a text version of the value. For a country list with 200+ values, formula fields run out of space. I tried using multiple formula fields linked together, but there is also a limit on that too. In Winter 07, you have functionality called "Field Update Rules". With these, you still use a formula to get at the picklist value. Same problem. This suggestion needs to be implemented. |
|
LogoJon 07/19/07 |
PLEASE!!! |
|
amanda_howell 10/01/07 |
This would make my life 100 times easier. |
|
marketforce Jan 16 |
This was something we could do with Siebel before we migrated to Salesforce and we miss it terribly. |
|
Chris_Murphy Feb 11 |
At the very least we should be able to map standard lead fields, the ones that default to the account, to another object. This small change seems simple enough to implement for SFDC and would be a great help. |
|
Chart Oct 3 |
Merged Idea
originally posted 06/06/07
Mapping Fields
You should be able to map a lead field to contacts and to accounts--so mapping in 2 places, not just 1. Thanks
|
|
Non-Profit Oct 3 |
Merged Comment
originally posted 06/21/07
This is important as it would be benefical to see custom lead fields in accounts and opportunities.
|
|
hudini007 Oct 3 |
Merged Comment
originally posted 06/21/07
It would also be great if the admin could determine where the SF standard fields are mapped to.
|
|
twellman Oct 3 |
Merged Comment
originally posted May 8
http://ideas.salesforce.com/article/show/90940/Lead_Mappingone_to_many
This should be combined with the above idea. |
|
lisaba Oct 3 |
Merged Idea
originally posted 10/15/07
Lead Mapping--one to many
It would be great if it was possible to map one lead field to both an opportunity AND contact field upon conversion....
|
|
guest San Francisco, CA Oct 3 |
Merged Idea
originally posted 10/05/06
Map lead fields to multiple fields
Please enable abilty to link the same custom lead field to relating custom fields in opptys, accounts and contacts. Thanks!
|
|
gmichel Oct 3 |
Merged Comment
originally posted 11/13/06
Would enable to propagate lead description both to contact and to oportunity when an opportunity exists. Would save a lot of copy/paste operations...
|
|
MartinWilliams Oct 3 |
Merged Comment
originally posted 11/29/06
I cannot believe this is even being requested - it should be there already!!!
Please promote folks! |
|
hayli Oct 3 |
Merged Comment
originally posted 12/01/06
We just received this request from our users today. Sometimes you want to know where the account came from, if it came for a campaign or if it was already in the system (from another source) and the contact came from a campaign.
|
|
byuhawaii Oct 3 |
Merged Comment
originally posted 01/26/07
A little annoying when you are trying to segment lists and have to run multiple reports and realize that custom filelds such as "product interest" do not migrate over. Seems like a lot of fragmentation.
|
|
LogoJon Oct 3 |
Merged Comment
originally posted 07/19/07
This is really going to be important for us when in Summer 07 we will be able to send transactional emails through workflows. We will want to send emails to Opportunities when the stage changes, but for an email to be automatically sent there needs to be an email field in the Opportunity Detail. I want to map the email from leads to an Opportunity field.
|
|
cesaralopez Oct 3 |
Merged Idea
originally posted 04/16/07
Custom Lead Field Mapping
It would be great to be able to map a custom lead field to two or more objects.
|
|
LucBaart Oct 3 |
Merged Comment originally posted 04/16/07 |
|
marekklu Oct 3 |
Merged Comment
originally posted Mar 4
This would be great! i need to map details to both the account and opportunity objects and i cant do this at this time!
|
|
marlowe Oct 3 |
Merged Idea
originally posted Oct 3
Map a Lead Field to more than one other field
We have a Lead Custom field named Database Platform. It is mapped to Opportunity: Database Platform.
I would also like to map it to: Account: Database Platform |
|
agf Oct 9 |
Yes, great idea, we really need this too. We currently map some custom Lead fields into custom Opportunity fields -- but when we convert a lead and _don't_ create an opportunity (which unfortunately happens more than we'd like ;-), we lose that data. Ideally for us, it would go into the Contact field only if the opportunity field isn't available -- so we don't end up duplicating data. But duplicating would be better than losing it :-) |
|
mattone84 Oct 23 |
very good idea! now I create a duplicate field on lead and map this one to opportunity for example: lead field X lead field X for opportunity (formula whic takes value from lead field X) lead field X is mapped into contact field x lead field x for opportunity is mapped into opportunity field x |
|
eahills Oct 28 |
This would be great, we really need this. We lose a lot of data on lead conversion, and there's no workaround we can find that isn't ridiculous and klunky. Promote this! |
track comments for this idea
Please log in to post a comment
last 100 promotions:
- rnoia
- SteffenADP
- kbrathwaite
- rharelson
- Harold
- michaelattts
- deepbluesea
- eahills
- uptimedev
- mattone84
- thecrmninja
- bdavis
- grueser
- kati_suvanto
- Mhagey
- wendysue
- agf
- marlowe
- newleaders
- jschaff
- tgroom
- Candleroses
- bhfs
- Ilene_LaBarbera
- JBA
- arnaudc
- mktgideas
- howard_huie
- kquadrat84
- BryanMQuinn
- andreas_krebs
- mgoodearl
- zyxwv
- avlerik
- twellman
- jsmengel
- sfsandiego
- nufchas
- ellenc
- kartikm
- marekklu
- sdingels@astaro.com
- Jimbo
- photonican
- Megs
- QTM
- TheBoot
- epbennett
- 5500
- crichardson
- Dougg
- NSDavid
- erikavl
- Marc_Baizman
- Adam.Gerlinger
- joemora
- bradcurrier
- carramrod
- cynthia_drechslr
- energyindustryuser
- ibarrie
- ta_invisible
- patrickhc
- Faun
- susana_nts
- suesue
- clearimage
- freewire
- craskulinecz
- leos337
- Tina_Buchholtz
- stevenbell
- Chris_Murphy
- at
- WLP
- Melissa_Hughes
- dbellalta@ioniasolutions.com
- EricG
- pierre-alain
- marketforce
- ShannonJohnson
- justmy2cents
- JenCalvert
- m1adm
- Jesterale
- CoriFox
- JoAnnCulbertson
- HappyGirl1128
- AnnGeerts
- Sunny
- daniele
- mlee
- nc_user
- ehadmin
- joakim
- JohanLiljegren
- rpr2
- LisaBailey
- Matsco1
- esanders
POST IDEA