This project is read-only.

Lookup Field with Picker 2010

Rating:        Based on 14 ratings
Reviewed:  14 reviews
Downloads: 7720
Released: Nov 21, 2011
Updated: Jun 9, 2012 by cglessner
Dev status: Beta Help Icon

Recommended Download

Application iLoveSharePoint.Fields.LookupFieldWithPicker.wsp
application, 25K, uploaded Nov 21, 2011 - 7720 downloads

Release Notes

Just forget the fuc**** dropdowns!

SharePoint Foundation 2010


* Single- and multi-Selection Mode
* Cross site picking
* Search in picker dialog
* Search Operators: equals, not equal, contains, begins with, greater than, greater or equal than, less than, less or equal than.
* Select fields you would like to search for.
* Relationship behaviors
* Supports default values (constants, current user id and default values by url param, useful for 1-n scenarios) must be configured via PowerShell
* Languages: English, German
* Delivered as SharePoint Solution Package (WSP)


Lookup Field with Picker 2010

11/07/2011 Fixed Issue: Lookup Field with Picker 2010 does not store value (August hotfix package)
_11/21/2011 Fixed Issue: Entity validation for calcualted columns

Reviews for this release

Hey there! this solution works great on 2010, i'm gonna migrate to 2013, is the solution keep working?
by PabloF on Jun 4, 2014 at 11:28 PM
I hate to say it, but there is a huge performance problem with this solution in case of multichoice. If you add more that 50-100 lookups your edit form will load insanely slow and you might even end up hitting timeout. The problem is with the validation process. It's incredibly CPU-intence. When you are trying to validate(resolve) even 3-4 lookup names your server CPU workloload jumps to 100%
by Zerg00s on Aug 9, 2013 at 9:04 AM
Great! It works for me on SharePoint 2010. Now I migrated my project on SharePoint 2013: there will be a new release for this version? Thanks a lot, Gennaro.
by geborx on May 15, 2013 at 1:08 PM
I need help, not work the instalation
by pino_1689 on Jan 22, 2013 at 5:09 PM
Great lookup function. I do have problems when trying to populate the field through a SharePoint Designer workflow - the value is not inserted. What is the explanation for this?
by tranders on Dec 2, 2012 at 10:42 PM
Great control, it so easy to choose items from huge lists. But unfortunately it doesn't work with Office 365 and i can't find something else. Will you adapt it to Office 365?
by yoshitoshi on Jul 24, 2012 at 11:31 AM
very nice, but it would be great if it returned the values as text as opposed to the lookup list ID followed by a Hash then the value, the ability to work in datasheet view woudl also be awesome rather than having it as read only as it is now and having to work on one item at a time. Also, is there anyway it can work with the DIP? thanks
by giustis5 on Apr 11, 2012 at 1:46 PM
Simply Excellent !
by AxelLimousin on Sep 11, 2011 at 12:11 AM
This control is fantastic. There is one one issue. The relations does not seem to survive if you save the site as a template. The copy has all relations if you enter data, but if you enter Lists Settings all relations are linked to Announcements (in my case). This makes it impossible to edit the relation in the copy. If you import data into this filed, make sure to use lookup # mark notation.
by volvojoplse on Aug 30, 2011 at 3:43 PM
Fantastic control! Greeting from sunny Croatia.
by gorandri on Jun 29, 2011 at 10:33 AM
Great FieldType now we've got a nice list of documents in stead of the enormous dropdow box.
by ureka on Jun 15, 2011 at 12:37 PM
Hello, I tried your picker and it's great. Like mpeterson79 I'd like to be able to search on multiple fields. Is there a way to setup that ? Thanks for the great work.
by hmertens on Mar 19, 2011 at 1:06 AM
I also posted on your WSS picker page. I was wondering if there is a way to return more than a single field when choosing from the picker. For example: When I select a customer name from the picker, I want it to also return the account number and address. Not just the customer's name.
by mpeterson79 on Dec 28, 2010 at 10:40 PM
We have had to resort to a custom field type, as the OOB lookup control simply does not scale to around 32K lookup items. When we try to edit a Lookup field with a larger number of items, we simply get a blank box. We are testing this control and initial impressions are good. Will update more later.
by shailensukul on Dec 21, 2010 at 6:17 PM