Salesforce IdeaExchange

540

Picklists For Lookups To Other Objects

In certain instances, it would be better for a lookup field to another object to be formatted as a picklist instead of a free text field.

Perhaps certain custom objects could be designated as a "static" or "reference" objects, and would be limited to holding a certain number of records (say 100 or 200). The user would then have the option of creating a "Picklist Lookup" field on another object which would present the records in the "reference object" as values in the picklist.

That would allow administrators and developers to store hidden data values for picklist items in the "reference object", but still present the label values in the picklist.

This is a basic capability in any relational database, and it would greatly enhance the capabilities of the Salesforce.com platform and allow for more robust business application development

This is related to Chris925's idea:

http://ideas.salesforce.com/article/show/65873/Make_picklist_values_hyperlink...

but different because I would like to see the picklist values actually stored in a custom object, not just have a hyperlink to a report for the selected value.

Scott_Jorgensen 05/17/07	This is a very interesting idea, I think it has the potential to be very elegant and powerful. What if you configured how the Lookup behaved in the Page Layout Editor?
AlexCRMmanager 05/18/07	Yes Scott, the Page Layout Editor would be a great place to control the Lookup behavior. Thanks for your comment!
rarce3209052007 Jun 18	Merged Idea originally posted 09/11/07 picklist-lookup field
rarce3209052007 Jun 18	Merged Comment originally posted 09/27/07 It's useful to let our clients to select different items from a lookup and place them in a picklist field.
lindsay.ryan11192007 Jul 3	I agree reference lookups that function like picklists (ie allow for in object field dependencies) are a much needed structural element. It would be especially awesome if there were a convert to custom object option for picklist values that first created the custom object, populated it with records based on the picklist values and then changed the picklist field to a lookup. Often times what happens as a field starts out short and sweet then evolves over time to be something that really belongs in a lookup relationship
neil_wingate Aug 14	I think this is one of the best ideas I have seen, primarily because I deal with user complaints regarding the lookup/popup window. Also, Managing nearly a dozen identical picklists on different objects is exhausting and just bad database design. I need to change each one of them each time we add a new "market". I would donate blood to have this implemented....
AlexCRMmanager Oct 25	If I had a dollar for everytime I've gotten a request for a lookup-picklist, I probably wouldn't have to work for a living! :-P

track comments for this idea

Please log in to post a comment

recently promoted by:

bettersfdc
rdoss
asya
michaellatideas
travis05
neil_wingate
zee_hamdy
avlerik
susana_nts
siemensplm
cliffa
cv_sam
hugh_mcgowan
chuckgoss02202008
qms
jraymcdadm
raver
anthony_szabo
critic
davids12272007
mary.annjoy
datarzan
e36mpower
Faun
gmuys12182007
Stevemo
Tina_Buchholtz
craskulinecz
Leahanne
JonP
mhiacumensolutions
nshah
rarce3209052007
SPIDynamics
blacher
DarkGuide
EddieDial800
RemH
alevine
berger
Enterit
Chrisr
ollie123
NetGenIT
EdCRM
TimMadigan
LucBaart
wylieatworknz
EricCH
nayoub
LizJordan
Jefe55
Scott_Jorgensen
AlexCRMmanager

Resources

Successforce.com

Picklists For Lookups To Other Objects - Salesforce IdeaExchange

Salesforce IdeaExchange

Picklists For Lookups To Other Objects

Search Community

Categories

1-800-NO-SOFTWARE | Privacy Statement | Security Statement