Comments on: Picklists vs. Lookups

By: Mitch Milam

Mitch Milam — Wed, 14 Jul 2010 13:09:44 +0000

Unfortunately, there is no automated or programmatic way to acccomplish this. You will need to create a new lookup, move the data from the picklist into the lookup entity, then replace the picklist with a lookup.

By: bl

bl — Wed, 14 Jul 2010 13:05:21 +0000

I need to convert a picklist attribute that is located on 3 different entities to a lookup. How best to accomplish this? Thank you

By: Manish MISTRY

Manish MISTRY — Thu, 30 Jul 2009 01:26:23 +0000

And why do you forget that with lookups, its really easy to have a reverse-lookup: if you have a color lookup for products, you can view a color e.g. "Blue" and in the left hand side related entities navigation click on Products to get a complete list of all the products that have color="Blue" As easy as that with just read privilege! a simple but very useful query sometimes.

By: mitch

mitch — Thu, 07 Aug 2008 14:51:46 +0000

Not without writing a bunch of Javascript

By: multiplex77

multiplex77 — Thu, 07 Aug 2008 08:47:23 +0000

That's great, but is it possible to still have a dropdownlist (picklist) instead of the more cumbersome Lookup to share the same entity data?

By: Xbox » Picklists vs. Lookups

Xbox » Picklists vs. Lookups — Mon, 08 Oct 2007 17:04:34 +0000

[...] unknown wrote an interesting post today onHere's a quick excerptWhile in a CRM design meeting yesterday, we began discussing adding a picklist to one of the CRM forms. One of the other developers made the following remark: “This field is also on two other forms. Let’s make it a lookup instead. … [...]

By: microsoft » Picklists vs. Lookups

microsoft » Picklists vs. Lookups — Mon, 08 Oct 2007 17:03:38 +0000