Lookup Field with Picker

Coordinator
Sep 27, 2008 at 3:22 PM
Here you can post anything about Lookup Field with Picker...
Sep 29, 2008 at 7:30 AM
I've been looking all over for a solution like the Lookup Field with Picker... thanks for putting it together so nicely.  I do, however, have one problem.  I need to export my list to Excel (for a legacy system) but any field created as a Lookup Field with Picker is displaying something like -- "3;#Adult Medicine-Ames Main" instead of simply "Adult Medicine-Ames Main" as I need.

Any idea how to work around this?
Coordinator
Sep 29, 2008 at 8:04 PM
Hi, unfortunately I haven't any idea. The Excel export and DataSheet View don't like custom fields.
The only thing you can do is using Excel string operations and save the export in a DocLib :-(
Bye, Christian
Oct 21, 2008 at 9:32 AM
Dear Christian,
I've found your control to be very useful in my test environment but have encountered a problem installing it in production environment.
The problem is that if you install Lookup with Picker on to Russian version of MOSS2007, when you click on Address book button you get the following exception: Could not find any resources appropriate for the specified culture or neutral culture. Make sure "Resources.iLoveSharepoint.Fields.LookupFieldWithPicker.resources" was correctly embedded or linked into assembly "App_GlobalResources.Irm4gqng" at compile time, or that all satellite assemblies required are loadable and fully signed.

Can I somehow circumvient this error by supplying additional resource files or what?

Best regards,
Konstantin 
Coordinator
Oct 22, 2008 at 8:55 AM
Hi Konstantin,
have you copied the ressource file as described in the readme.txt?
Bye, Christian
Oct 22, 2008 at 10:27 AM
Hi Christian, no, I haven't. Sorry for such a dumb mistake on my part
Coordinator
Oct 23, 2008 at 8:40 AM
Hi Konstantin, no problem ;-)
Nov 17, 2008 at 1:27 PM
Hi,

is it possible to databind the lookup field not to a list but to a view? Why I would like to do that is, I need to filter the data in the lookup.

Thanks in advance!
Coordinator
Nov 17, 2008 at 7:21 PM
Hi Mark,

unfotunately you can't pre filte the lookup. With one exception, if you haven't read permission to some items they should not be visible.

Bye, Christian
Nov 20, 2008 at 8:50 AM
Hi Mark,

look at http://www.codeplex.com/CustomFieldControls Query Based Lookup field Control

Bye Saulius
Nov 20, 2008 at 9:11 AM
Edited Nov 21, 2008 at 6:29 AM

Hi Chistian,

Maybe it’s possible to use some function like “substring” to get only first part of value.

Ex: 108;#108  must return result only 108

I found solution myself :)
http://www.codeplex.com/spdwfextensions
using function Entry() with parameters
 1 - Lookupwithpicker.value
 2 - 0  item position
 3 - ;  separator

Bye Saulius

Coordinator
Nov 25, 2008 at 7:37 AM
Hi Saulius,

sorry, I'm a little bit late.
Thanks for the clue ;-)

Bye, Christian

Jan 21, 2009 at 7:50 AM
Edited Jan 21, 2009 at 8:06 AM
Hi,

I've tried this solution in a test enviroment, works perfect on 32-bit windows server 2003.
But...I can't get it wright on a 64-bit server 2003 R2 with sp2. When I create a custom list, I have a chance to select your lookup field with picker, but when I click on it, I get an error.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Web Controls
Event ID: 7043
Date:  21.1.2009
Time:  4:59:51
User:  N/A
Computer: LJSWSS0000001
Description:
Nalaganje datoteke predloge kontrolnika »/_controltemplates/LookupFieldWithPickerEditor.ascx« ni uspelo: The resource object with key 'lookupWithPickerChooseSearchFieldsLabel' was not found.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



Any idea? Thanks in advance

Bozo
Coordinator
Jan 21, 2009 at 4:29 PM
Hi,

ensure that there resource file resides in the virtual folder of the web application (port) where you need the picker as described in the readme.txt.

Bye, Christian
Jan 22, 2009 at 8:36 AM
Ok, one port was not installed so I did it manually.
Still getting errors, it sure must be because of language pack that I use (Slovenia). I keep getting errors such as under. I tried renaming, but no luck.
I guess I'll have to qouit on this nice lookup solution. 

Greetings, 
Božo

 
01/22/2009 10:08:45.40  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "XomlUrl", keyfile core. 
01/22/2009 10:08:45.40  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
01/22/2009 10:08:45.40  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "RulesUrl", keyfile core. 
01/22/2009 10:08:45.40  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
01/22/2009 10:08:48.48  w3wp.exe (0x1720)                        0x1590 SharePoint Portal Server       Runtime                        8gp2 Medium   Initializing portal application domain '/LM/W3SVC/1/Root-1-128770889200476701'. 
01/22/2009 10:08:48.51  w3wp.exe (0x1720)                        0x1590 SharePoint Portal Server       Runtime                        8gp7 Medium   Topology cache updated. (AppDomain: /LM/W3SVC/1/Root-1-128770889200476701) 
01/22/2009 10:08:48.51  w3wp.exe (0x1720)                        0x1590 SharePoint Portal Server       Runtime                        8gp6 Medium   Initialized portal topology cache for application domain '/LM/W3SVC/1/Root-1-128770889200476701' 
01/22/2009 10:08:48.51  w3wp.exe (0x1720)                        0x1590 SharePoint Portal Server       Runtime                        8gp4 Medium   Portal application domain '/LM/W3SVC/1/Root-1-128770889200476701' initialized. 
01/22/2009 10:08:48.64  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8sl1 High     DelegateControl: Exception thrown while adding control 'Microsoft.SharePoint.Portal.WebControls.SearchBoxEx': System.Threading.ThreadAbortException: Thread was being aborted.     at System.Threading.Thread.AbortInternal()     at System.Threading.Thread.Abort(Object stateInfo)     at System.Web.HttpResponse.End()     at Microsoft.SharePoint.Portal.WebControls.SPSCommon.StopProcessingRequestIfNotNeeded(Page page)     at Microsoft.SharePoint.Portal.WebControls.WebPartLoc.StopProcessingRequestIfNotNeeded()     at Microsoft.SharePoint.Portal.WebControls.SearchBoxEx.OnInit(Object sender, EventArgs e)     at System.Web.UI.Control.OnInit(EventArgs e)     at Microsoft.SharePoint.WebPartPages.WebPart.OnInit(EventArgs e)     at System.Web.UI.Control.InitRecursive(Control namingContainer)     at Syste... 
01/22/2009 10:08:48.64* w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8sl1 High     ...m.Web.UI.Control.AddedControl(Control control, Int32 index)     at Microsoft.SharePoint.WebControls.DelegateControl.AddControlResilient(Control ctl) 
01/22/2009 10:08:49.46  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        6y1a Medium   Creating reg key "SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports" 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        72kg High     #20015: »iLoveSharePoint.Fields.LookupFieldWithPicker.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape. 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        72kg High     (#2: »iLoveSharePoint.Fields.LookupFieldWithPicker.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape.) 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile iLoveSharePoint.Fields.LookupFieldWithPicker. 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        72kg High     #20015: »iLoveSharePoint.Fields.LookupFieldWithPicker.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape. 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        72kg High     (#2: »iLoveSharePoint.Fields.LookupFieldWithPicker.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape.) 
01/22/2009 10:08:50.09  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile iLoveSharePoint.Fields.LookupFieldWithPicker. 
01/22/2009 10:08:50.11  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "DistributionLists_Alias", keyfile core. 
01/22/2009 10:08:50.11  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'DistributionLists_Alias' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". 
01/22/2009 10:08:49.73  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "XomlUrl", keyfile core. 
01/22/2009 10:08:49.73  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'XomlUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
01/22/2009 10:08:49.73  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "RulesUrl", keyfile core. 
01/22/2009 10:08:49.73  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'RulesUrl' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\Fields\fieldswss.xml". 
01/22/2009 10:08:50.59  w3wp.exe (0x1720)                        0x15D8 Windows SharePoint Services    Topology                       88gr Monitorable alternateUrl is null 
01/22/2009 10:08:50.61  w3wp.exe (0x1720)                        0x15D8 Windows SharePoint Services    Topology                       88gs Monitorable hostHeaderSiteInfo is null 
01/22/2009 10:08:51.18  w3wp.exe (0x1720)                        0x15D8 Windows SharePoint Services    General                        8e2s Medium   Unknown SPRequest error occurred. More information: 0x80070002 
01/22/2009 10:08:51.90  w3wp.exe (0x1720)                        0x1590 CMS                            Publishing                     6p52 Medium   Constructing PortalSiteMapProvider 
01/22/2009 10:08:51.21  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    Web Controls                   7043 Critical Nalaganje datoteke predloge kontrolnika »/_controltemplates/LookupFieldWithPickerEditor.ascx« ni uspelo: The resource object with key 'lookupWithPickerChooseSearchFieldsLabel' was not found. 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     #20015: »cmscore.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape. 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     (#2: »cmscore.sl-SI.resx« ni mogoče odpreti: ni take datoteke ali mape.) 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile cmscore. 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     #20015: »cmscore.resx« ni mogoče odpreti: ni take datoteke ali mape. 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     (#2: »cmscore.resx« ni mogoče odpreti: ni take datoteke ali mape.) 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile cmscore. 
01/22/2009 10:08:52.34  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'List_Pages_UrlName' could not be found for file with path: "(unavailable)". 
01/22/2009 10:08:52.43  w3wp.exe (0x1720)                        0x1590 Office Server                  Office Server Shared Services  7fx8 High     Starting shared object cache refresh timer with an interval of 0 seconds. 
01/22/2009 10:08:52.43  w3wp.exe (0x1720)                        0x1590 Office Server                  Office Server Shared Services  6pli High     Shared object cache refresh timer started. 
01/22/2009 10:08:52.45  w3wp.exe (0x1720)                        0x1590 Office Server                  Office Server Shared Services  8i1t Medium   Adding new shared object store for connection 'Server=ljssqlsrv0001;Database=SharedServices_DB_1;Trusted_Connection=yes;App=Windows SharePoint Services;Timeout=15'. 
01/22/2009 10:08:52.45  w3wp.exe (0x1720)                        0x1590 Office Server                  Office Server Shared Services  6y2d Medium   Cached shared object store for connection 'Server=ljssqlsrv0001;Database=SharedServices_DB_1;Trusted_Connection=yes;App=Windows SharePoint Services;Timeout=15'. 
01/22/2009 10:08:52.48  w3wp.exe (0x1720)                        0x1590 Office Server                  Office Server Shared Services  7fxd Medium   Initialized new shared object cache at version 39. 
01/22/2009 10:08:52.51  w3wp.exe (0x1720)                        0x1590 Search Server Common           MS Search Query                8wqm Medium   'SharedServices', scope cache: creating 
01/22/2009 10:08:52.54  w3wp.exe (0x1720)                        0x1590 Search Server Common           MS Search Query                90gl Medium   SQL: dbo.proc_MSS_ScopeCacheGetChangedConsumers 0 
01/22/2009 10:08:52.54  w3wp.exe (0x1720)                        0x1590 Search Server Common           MS Search Query                8wqg Medium   'SharedServices', consumer scope cache '00000000-0000-0000-0000-000000000000': creating 
01/22/2009 10:08:52.57  w3wp.exe (0x1720)                        0x1590 Search Server Common           MS Search Query                90gk Medium   SQL: dbo.proc_MSS_ScopeCacheGetChanges 'shared' 
01/22/2009 10:08:52.51  w3wp.exe (0x1720)                        0x122C Office Server                  Office Server Shared Services  6pls Medium   Cache blocked for shared object '1dd1db1d-8a07-4e27-9249-b7d328818fa2' of type 'Microsoft.Office.Server.Search.Administration.SearchSharedApplication'. 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     #20015: Cannot open "iLoveSharePoint.Fields.LookupFieldWithPicker.en-US.resx": no such file or folder. 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     (#2: Cannot open "iLoveSharePoint.Fields.LookupFieldWithPicker.en-US.resx": no such file or folder.) 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile iLoveSharePoint.Fields.LookupFieldWithPicker. 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     #20015: Cannot open "iLoveSharePoint.Fields.LookupFieldWithPicker.en-US.resx": no such file or folder. 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        72kg High     (#2: Cannot open "iLoveSharePoint.Fields.LookupFieldWithPicker.en-US.resx": no such file or folder.) 
01/22/2009 10:08:53.68  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e26 Medium   Failed to open the language resource keyfile iLoveSharePoint.Fields.LookupFieldWithPicker. 
01/22/2009 10:08:53.70  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8e25 Medium   Failed to look up string with key "DistributionLists_Alias", keyfile core. 
01/22/2009 10:08:53.70  w3wp.exe (0x1720)                        0x1590 Windows SharePoint Services    General                        8l3c Medium   Localized resource for token 'DistributionLists_Alias' could not be found for file with path: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\xml\base.xml". 
01/22/2009 10:09:06.14  w3wp.exe (0x1720)                        0x122C Windows SharePoint Services    General                        8dzz High     Exception Type: System.Web.HttpException  Exception Message: The resource object with key 'lookupWithPickerChooseSearchFieldsLabel' was not found.  
01/22/2009 10:09:09.61  w3wp.exe (0x1720)                        0x1778 Windows SharePoint Services    Topology                       88gr Monitorable alternateUrl is null 
Coordinator
Jan 22, 2009 at 10:14 AM

To use the picker with other languages, you have to copy the resource file "iLoveSharePoint.Fields.LookupFieldWithPicker.resx" (where to find see readme.txt) and rename it to "iLoveSharePoint.Fields.LookupFieldWithPicker.[language-culture].resx" e.g iLoveSharePoint.Fields.LookupFieldWithPicker.de-de.resx for German. If you want, you can translate the resource file with any resource editor like VS. Let me know if you have a translation and want to share it with others.

 

Feb 6, 2009 at 8:56 AM
Instead of manually copying the iLoveSharePoint.Fields.LookupFieldWithPicker.*.resx from "%commonprogramfiles%\Microsoft Shared\web server extensions\12\CONFIG\Resources"
to the web application resource folders e.g. "C:\Inetpub\wwwroot\wss\VirtualDirectories\*\App_GlobalResources\" you can simply run the "copyappbincontent" using stsadm. (' "%stsadmDir%\stsadm.exe" -o copyappbincontent ') after deploying the solution. This should do the trick.
Feb 6, 2009 at 4:46 PM
Hi,

I have installed the LookupWithPicker and are currently testing it in our SharePoint system in several lists.

I have come across a couple of issues but I am not sure if they are 'bugs' or errors in our system and would appreciate any 'pointers' in how to fix them.

1) I cannot use a LookupWithPicker field in one list as a search field in another LookupWithPicker. Is there any way to correct that?
2) I am using a LookupWithPicker to lookup addresses from another list where there are the columns "Name or Number", "Street1", "Town/City", "Region". When searching for 'Peterborough' of which there are 42 records, the search returns the error "There was an error in the callback" regardless of whether the criteria is 'Contains' or 'Begins with'. The Maximal search results is set to 500. This error also occurs when searching for '53' against the "Name or Number" field, but '53 w' returns the desired results. Is there any way to determine what the "There was an error in the callback" error is?

Thanks in advance.
Coordinator
Feb 8, 2009 at 7:30 PM
Hi,

1) I think this is a feature request. Seems the field chooser filters the LookupWithPicker columns.
2) Sounds like a bug. Unfortunately "There was an error in the callback" is diffucult to debug, it's a AJAX like functinality from ASP.NET 2.0. What type of field is "Name or Number"?

Bye, Christian
Coordinator
Feb 10, 2009 at 6:39 AM
@andhe Thanks fo the tip :-)
May 14, 2009 at 1:06 PM

Hi Christian,

I integrated the sourcecode from your MultiLookupFieldWithPickerControl to have a debug-possibility in my solution package and it works really good with one big except:

If I use the control within the normal list, everything works fine but if I integrate the control in the PageLayout in a Publishing Web, try to select more than one item from the catalogue and try to save the page, I get an exception:

Failed to get value of the "Products" column from the "Lookup with Picker" field type control.  See details in log. Exception message: Index was outside the bounds of the array..

SPException: Failed to get value of the "Products" column from the "Lookup with Picker" field type control. See details in log. Exception message: Index was outside the bounds of the array..] Microsoft.SharePoint.WebControls.BaseFieldControl.OnLoad(EventArgs e) +1986 SKBPrototypeCore.LookupFieldWithPickerControl.OnLoad(EventArgs e) +44 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Control.LoadRecursive() +141 System.Web.UI.Control.LoadRecursive() +141 System.Web.UI.Control.LoadRecursive() +141 System.Web.UI.Control.LoadRecursive() +141 System.Web.UI.Control.LoadRecursive() +141 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Could you please have a look at that issue?

Greetings from Erlangen, Germany

LoneSurvivor

May 15, 2009 at 3:33 PM

This control fit one of our needs perfectly.  Thanks for sharing.

Do have one question, though:

Is it possible to gray out the text box and force users to use the search function?  We have this tied into a list that can have non-unique values, so if a user decides to just type in a name that corresponds to multiple results, the control just selects the first one and the user doesn't know they might be using the wrong info.

May 18, 2009 at 1:30 PM

Hi again,

okay, I found out what's going wrong: I added a second field with type of the Lookup-Field with Picker in SharePoint Designer and I discovered, that SPD this time created the custom-tag for FieldMultiLookupWithPickerControl which differs from the custom-tag, SP Designer added for the other field before: LookupFieldWithPickerControl.

While using FieldMultiLookupWithPickerControl anything works fine! I'm very glad about that but I still don't understand, why SharePoint Designer created two different Tags... Sorry for the confusion...

Greetings from Erlangen,
LoneSurvivor

Jun 3, 2009 at 8:07 AM
Edited Jun 3, 2009 at 11:47 AM

Hi,

Using Windows 2008 Enterprise - nothing shows up in MOSS after installation of the Lookup.

Previous posts mention copying a resource file but I see no mention in the current read me?

Works OK in 2003, does it do X-Site?

Thanks,

Casey

Jun 15, 2009 at 12:31 PM

Hi, I have just installed the latest version of the lookup with picker and it works ok in the form, (it can check matches for a typed entry) however when I click on the picker button to search for a record i receive the following error message in the pop-up window which should house the picker:

"Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site.  at
Microsoft.SharePoint.ApplicationPages.Picker.OnLoad(EventArgs e)
  at System.Web.UI.Control.LoadRecursive()
  at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)"

I am no expert on the back end of sharepoint and I understand that certain addins are required to be entered into the safecontrols section of the webconfig file, I have tried doing this with the following code entries, both do not work:

<SafeControl Assembly="LookupWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e1eb4ce568bda77d" Namespace="LookupWithPicker" TypeName="*" Safe="True" />

<SafeControl Assembly="iLoveSharePoint.Fields.LookupFieldWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8ecfa5d637948fe" Namespace="iLoveSharePoint.Fields.LookupFieldWithPicker" TypeName="*" Safe="True" />

Can someone please assist with this?

Thanks, Andrew

Jun 22, 2009 at 12:46 AM

I'm have the issue exactly as posted above.  I've used the control before without issue but have installed the latest version on a new server and am getting the safe control issue.  I've tried adding a safe control as follows but still getting the safe control message:

<SafeControl Assembly="LookupWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e1eb4ce568bda77d" Namespace="LookupWithPickerr" TypeName="*" Safe="True" />

Any help would be greatly appreciated.

Coordinator
Jun 24, 2009 at 11:27 AM

Hello,

@AndyThomas and @Chloes: You have to add ensure that the following entry exists in the web.config for the approriate Web Application (port).

<SafeControl Assembly="iLoveSharePoint.Fields.LookupFieldWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c8ecfa5d637948fe" Namespace="iLoveSharePoint.Fields" TypeName="*" Safe="True" />

By default the entry should exists on port 80 on your local server. You can also deploy the solution on other web apps and servers via stsadm or by adding the entry manual.

@cairokerry:

This step is only needed for non english or german sites.

Bye, Christian

Jun 24, 2009 at 11:48 AM

Hi Christian,

Thank you for your response, it is now working perfectly.

Regards, Andrew

Sep 17, 2009 at 11:29 AM

Hello Sir,

I have just installed the latest version of the lookup with picker and it works ok in the form, however when I switch to "Edit in Datasheet", and I click on the field of the lookup with picker, it show "Read-only" on below and I cannot enter any data in this field, why? please advice, thanks for your help.

 

Gary.

Sep 24, 2009 at 6:52 PM

Hello All!

 

I tried the picker on Win2003 x86 and it works like a dream! Great job there! :) I only got a little problem. Can i pick values from from another list at another subsite ? Like this: list1 is on http://mysite.com and the other (which will contain the picker field) is on http://mysite.com/subsite.

Regards

Coordinator
Sep 25, 2009 at 7:37 AM

Hello,

you have to create a site column of type Lookup Picker in site  htt://mysite.com, then you can reuse it on http://mysite.com/subsite.

Bye, Christiab

Sep 25, 2009 at 12:48 PM

Hello Christiab!

 

Boy I'm stuuuupid! :) I didnt't think of this solution!

 

Thanks so much!

 

Regards

Sep 28, 2009 at 7:58 PM

Hi,

I have a column in a list with a lookup to another list. I then want to make a template out of both lists and put them on another site.

When I create the new lists on the other site using the templates from the other, when I try to open an existing, because I made the template with content or create a new item, I get the error 'list does not exist'.

would it work if both lists had exact same names or is it something deeper?

I tried creating a new column with a lookup to the new list and that seems to work okay, but I can't get rid of the old column, I get the same error as above 'list does not exist'

any help would be greatly appreciated.

Chris.

Coordinator
Oct 6, 2009 at 7:49 AM

Hi Chris,

this is not possible with SharePoint, you will get the same behavior with the builtin lookup. The problem is that when you create a new list it gets a new ID. Lookup fields refer to this ID. You could try to use a Site Template, as far as I rember there's a mechanism which fix the lookup IDs. No warrantie ;-)

Bye, Christian

 

 

Oct 13, 2009 at 1:30 AM
Edited Oct 13, 2009 at 1:53 AM

2 Bugs with Lookup Against Number
List is a bunch of cities, states and postal codes. If it makes a difference, it is a very long list.

Bug 1
I have a Lookup linked to PostalCode field (in the US, this is a 5 digit number, but stored as text since it can start with 0). As a shortcut, if you enter the number and click "Check Names" button, it resolves to the wrong item.
Example: Enter 10001 then Check names and it resolves to 24430. For reference, that is NOT the ID of the record...so not sure why/what record it is pulling ?? If you use the lookup form, it DOES find properly, so this only happens on the Check Names button press.
Expected behavior: Resolve to the correct PostalCode Number, when you click "Check Names"

Bug 2

Then ran this test, attached the field to the CityName field, which is pure text.
Type "Burlington" and Check Names and it works. A black line appears under Burlington. However, if you type "1"  it resolves to a completely different City name "Holden"...which happens to be the record position ID of the list. ie, if you type 6, and check names, it resolves to the CityName of the record with ID=6
Expected behavior: Do not resolve the ID. Typing a number should cause a lookup error (red squiggly lines under the text), that the City cannot be found

 

More info: Confirmed the problem is NOT my list. I tried the other tool LookupWithPicker, (it's not nearly as good though) but the 'check names' function works properly to resolve the Postal Code entered. But I don't like that control, IHEARTSP has much more functionality!!

Oct 16, 2009 at 12:27 AM

Having the same problem above

Nov 17, 2009 at 4:28 AM

Hi,

The software worked fine for me the first time, but when I installed it on another location - I have encountered some problems. My error is "Only PickerDialog types can be used with the dialog. The type should be configured as a safecontrol in this site."

I have tried the solution explained above by Christian (as follows) but still get the same error. Are there any other ideas?

 

Thanks

Rahulan

Dec 17, 2009 at 4:57 PM
cglessner wrote:

Hi Chris,

this is not possible with SharePoint, you will get the same behavior with the builtin lookup. The problem is that when you create a new list it gets a new ID. Lookup fields refer to this ID. You could try to use a Site Template, as far as I rember there's a mechanism which fix the lookup IDs. No warrantie ;-)

Bye, Christian

 

 

 Well my workaround is to use Sharepoint Manager and go to the list items and delete it, then I recreate it as I need using same name as before and all my workflows and views seem to be uneffected.

Feb 17, 2010 at 12:21 PM

Hi

The list picker works fine on my site installation, but the list we are using has around 8000+ entries, and the search limit can only be set to 500. Is there anyway to increase this limit?

Thanks.

Mar 14, 2010 at 9:35 PM

Any news on upgrading this for sp 2010. I know it's still in beta but i figured i'd ask.
I've actually tried by replacing the sharepoint.dll, sharepoint.security dlls with the updated versions & updating the version through out the source code, but it wasn't that simple lol.
I keep getting the following error when selecting the lookup column option on a create column screen

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. 

Parser Error Message: Could not load file or assembly 'iLoveSharePoint.Fields.LookupFieldWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7c0cefa721ae73bb' or one of its dependencies. The system cannot find the file specified.

Source Error: 

Line 5:  <%@ Import Namespace="Microsoft.SharePoint" %>
Line 6:  <%@ Implements Interface="Microsoft.SharePoint.WebControls.IFieldEditor,Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
Line 7:  <%@ Assembly Name="iLoveSharePoint.Fields.LookupFieldWithPicker, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7c0cefa721ae73bb" %>
Line 8:  <%@ Import Namespace="iLoveSharePoint.Fields" %>
Line 9:  <%@ Import Namespace="System.Collections.Generic" %>


Source File: /_controltemplates/LookupFieldWithPickerEditor.ascx    Line: 

Mar 14, 2010 at 9:48 PM

Actually the above error wasn't really an issue it was a web.config error on my part.


The error i'm getting now is

 

 

Server Error in '/' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error: 


Line 183:            return;
Line 184:        
Line 185:        base.InitializeWithField(field);
Line 186:        
Line 187:        SPList userInfoList = SPContext.Current.Web.SiteUserInfoList;

Source File: c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\LookupFieldWithPickerEditor.ascx    Line: 185 

Stack Trace: 


[NullReferenceException: Object reference not set to an instance of an object.]
   Microsoft.SharePoint.ApplicationPages.LookupFieldEditor.InitializeWithField(SPField field) +272
   ASP._controltemplates_lookupfieldwithpickereditor_ascx.InitializeWithField(SPField field) in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\LookupFieldWithPickerEditor.ascx:185
   Microsoft.SharePoint.ApplicationPages.FieldCustomizationPage.OnLoad(EventArgs e) +748
   Microsoft.SharePoint.ApplicationPages.FieldNewPage.OnLoad(EventArgs e) +17
   System.Web.UI.Control.LoadRecursive() +65
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2427

 

 

Apr 1, 2010 at 8:32 AM

hi zsysop,

hi have the similar problem on Sharepoint 2010 beta version. I deployed Lookup field with picker, than I tried to create lookup field and after I chose <label for="onetidTypeLookupFieldWithPicker">iLove SharePoint - Lookup with Picker column </label>

<label for="onetidTypeLookupFieldWithPicker">from chosse collection issue occured: Server Error in '/' Application. In log I saw line: </label>

<label for="onetidTypeLookupFieldWithPicker">System.NullReferenceException: Object reference not set to an instance of an object.    at Microsoft.SharePoint.ApplicationPages.LookupFieldEditor.InitializeWithField(SPField field)     at ASP._controltemplates_lookupfieldwithpickereditor_ascx.InitializeWithField(SPField field) in c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\LookupFieldWithPickerEditor.ascx:line 180     at Microsoft.SharePoint.ApplicationPages.FieldCustomizationPage.OnLoad(EventArgs e)     at Microsoft.SharePoint.ApplicationPages.FieldNewPage.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 44f945ac-bea4-4c59-b1cc-8f046c4d540c</label>

Any smart guy to help me with this issue?

Coordinator
Apr 5, 2010 at 6:08 PM

Hello,

I haven't tested lookup field with picker until now with SP2010. But I look forward to release a new version for SharePoint 2010, hopefully in Avril.

Bye, Christian  

Coordinator
May 8, 2010 at 8:18 PM

Hello,

I've just published the first draft from Lookup Field with Picker 2010: http://ilovesharepoint.codeplex.com/releases/view/44989

Deploying the solution on your SP2010 should upgrade the broken SP2007 picker.

Feeback would be appreciated.

Bye, Christian

 

May 12, 2010 at 10:31 AM

Hi Christian, I just tested the Lookup Field with Picker 2010 release 44989 on my development machine.
I succeeded in adding the field as a site column and also as a document library column, however the field settings are not stored for some reason.
Also the lookup value itself is not saved when selecting a lookup value from the Edit Properties dialog.

Is that working on your machine?

Thanx, Geert van Raaij

May 12, 2010 at 11:29 AM
cglessner wrote:
Hi,

2) Sounds like a bug. Unfortunately "There was an error in the callback" is diffucult to debug, it's a AJAX like functinality from ASP.NET 2.0. What type of field is "Name or Number"?

Bye, Christian

 Hi, Christian,

Somewhere in your blog comments you said you fixed the "there was an error in the callback" ajax issue in version 2.0. We now run v.2.56 and still the lookups for our lists generate this error. Can you shed some light on how you solved it previously? What generally causes this error in your experience?

Thanks in advance

Coordinator
May 12, 2010 at 9:55 PM

@gvraaij Yes, it runs on my machine pretty well. But I've got the problem too while development. After I delete the field and recreate it, it worked. Haven't any idea why?

Bye, Christian

Coordinator
May 12, 2010 at 10:00 PM

@ACrush sorry I don't rember what the cause has been. Anyway it should be fixed. Maybe a look in the SharePoint trace file could give a hint.

Bye, Christian

May 25, 2010 at 9:21 AM

Christian, I also managed to get the lookup field up and running. Thanx.
Some more questions however.......

  • In your Field Type Definition file "fldtypes_iLoveSharePoint_LookupFieldWithPicker.xml" you still refer to the previously used FieldEditorUserControl: LookupFieldEditor.ascx
    Did you forget to delete this from the def. file?
  • Is there a possibility to configure which search fields to use from the lookup list?
  • In my case I would like to keep the possibility to use a FieldEditorUserControl related to the custom lookup field.
    But the one thing that broke in SP2010 compared to SP2007 is the fact that in the method InitializeWithField(SPField field) the field parameter (of type SPField) is always null.
    Can someone share their experience with that in case of SP2010?

Thanks all.
Regards Geert

May 26, 2010 at 11:40 AM

I also get the error:

"there was an error in the callback"

I'm running the latest version (V2.56)

Any idea how to solve this?

May 26, 2010 at 2:11 PM

The saddest part of 'error in callback' is that the failing code is not available to the debugger.

We had to resort to recreating the failing list. Still the risk remains that other lists might fail as well.

Must thoroughly monitor and govern changes and test, test, test.

Jun 1, 2010 at 2:50 PM
Hi, I'm using the 2007 version of the lookup field with picker. Is there any way to instanciate such a field from a content type defined in a feature ? When I "spsource" the content type, I get the following error : "the SearchFields attribute is forbidden" thanks for the help steve
Coordinator
Jun 2, 2010 at 10:00 AM

Hi Seve,

you can't set the SearchFields attrtibute declarative in the Version for 2007. In the 2010 you can't set the SearchFields attribute at all, because the searchable Fields will be determined by the SP2010 dependent Fields of SPLookups.

If you want to set it in the 2007 version, you should use a Feature Receiver and add the column programtically to your content type.

Bye,

Christian

Jun 3, 2010 at 9:21 AM

Thanks for your answer, but I'm having troubles to create the field by code. Do you have any sample code ?

 

thanks,

steve

Jun 3, 2010 at 12:45 PM

apart my previous question, I don't find the correct source code release, corresponding the the stable 2.26 version. I want to "patch" some found bugs, but all release I tried to compile failed.

thanks,

steve

 

Jun 3, 2010 at 12:56 PM
As for the 'error in callback' , it seems to be only there because I use the Dark Blue Duck Scanning Enabler. When I scan a page I can choose the data, but I get the error. So when I press OK, it asks me again because I haven't filled out that form according to sharepoint. And when I choose the data then it works fine. Seems like a small bug..
Aug 6, 2010 at 3:10 PM

Christian,

Is the search only on sharepoint lists or can we use bdc as a source to search with multi-select mode? If not, what is work around to do this.

 

Coordinator
Aug 9, 2010 at 8:15 AM

Lookupfield with Picker supports only SharePoint lists. BCS has a picker of its own.

Aug 9, 2010 at 11:19 AM

Thanks for your reply.

You mean to say sharepoint 2010 BCS has its own picker where user can select mulitple rows?  

Coordinator
Aug 12, 2010 at 7:49 AM

Yes, but I'm not sure if this is an server or foundation feature.

Aug 16, 2010 at 9:51 AM

hi all,

how to generate LookUp with picker linq entity in code? SpMetal tool doen's recognize and not generate this "special column" to my linq schema. So do I have to add it manually to the code?

If yes, what type it is?  If no, how to write spmetal commnad?

I work with LINQ to Sharepoint schema.

thank You

 

Coordinator
Aug 19, 2010 at 9:39 AM

Hello, it inherits from SPFieldLookup. Means it should behave exactly as the builtin Lookups.

Bye, Christian

Aug 26, 2010 at 2:31 PM

I'm using Lookup Field with Picker 2010 (beta2) on my sharepoint 2010 server.

it works great in the list, but I'm having an issue using it in a workflow.

the builtin picker gives you the option to return the field as: Lookup value (as Text)

but when I use the Lookup field with picker 2010 I can only return field as: As string.

Since the lookup stores the data in an array all the values look like

12;#Project Lunch

so when I'm trying to conpare the value in the picker to another value they don't match.

I've been told if I use the build in picker and pick lookup value as text. it will trim off the array info and just return the data (for example: Project Lunch)

I don't know if this is a bug or something that can be fixed. I just wanted to let you know what I'm running into trying to use your awesome picker.

 

thanks,jb

Coordinator
Aug 31, 2010 at 7:03 AM

Hello jb,

unfortunatley you have some restrictions when you develop custom field types. Escpecially with Office Intergration, Datasheet View and SharePoint Designer. As fas as I remember there are some new string parsing functions in SPD 2010 - maybe they can help.

Bye, Christian

Sep 21, 2010 at 10:26 AM

Hi,

I've discovered an issue where the EditForm.aspx for a list which contains a Lookup With Picker control is timing out when a large number of items have already been added to the lookup with picker field. My current example has 156 items already added to the lookup field.

Any ideas?

 

 

Oct 5, 2010 at 6:43 PM

I tweaked your code little bit and made my own custom lookup that talks to across farms.  I am loading all the items (user wants to see all items on load) for a given list in picker dialog when the user clicks browse button. It takes 5 to 10 seconds time to load all items and it doesn't display anything like it is loading or doing something. I would like to display a empty picker dialog with please wait option when the user clicks browse button. Any ideas how to acheive this?

Thanks

KPD

Dec 28, 2010 at 9:17 PM
Edited Dec 29, 2010 at 4:43 PM

I have my picker set up to choose from a list of customers.  This customer list has their name, address, phone #, acct #, etc.  What would be GREAT is if the picker returned more than one field to the form.  When I pick a customer's name out of the picker, I want it to return not only their name, but also their address and account number.  Any way of doing this?

Also, when typing something into the text box and then using the 'Check Names' control, it doesn't return the correct item.  Example:  I type '1020' into the box, and it returns something completely different.  Yet when I search for '1020' it works correctly.

Mar 3, 2011 at 9:28 AM

sHi Christian,

Many thanks for the Picker control - has got me out of a nasty hole with a couple of large datasets !

I am trying to run some code after the Picker has been updated to populate some default values into other fields on the form - is there any event that has been exposed ?

I've tried to mess around with the following inputs:  _hiddenSpanData, _OriginalEntities, _HiddenEntityKey,_HiddenEntityDisplayText, _downlevelTextBox,

Adding an alert as follows

ctl.onchange = function(){alert('Hello World');};

To no avail.

Any help would be much appreciated.

 

James

Mar 7, 2011 at 12:17 PM

For anyone who might be interested, I ended up attaching a propertychange event to the hiddenSpanData, which maybe hacky but does the trick:

  {$(#ctl00_m_g_nnnnnn_ctl00_ctl04_ctl01_ctl00_ctl00_ctl04_ctl00_ctl00_hiddenSpanData";).bind('propertychange',function(e) {e.preventDefault(); alert(this.value);});}

Mar 23, 2011 at 4:07 AM
Edited Mar 23, 2011 at 4:08 AM

Hi Christian:

I am using powershell to set a field of "Lookup with Picker",

but somehow I can't get field value collection with following script snippet:

 

	[Microsoft.SharePoint.SPFieldLookupValueCollection]$pool = New-Object Microsoft.SharePoint.SPFieldLookupValueCollection
	[Microsoft.SharePoint.SPField] $pool_field = $item.ParentList.Fields.GetFieldByInternalName("lookup_with_picker_field")
	Write-Host $pool_field.TypeAsString #LookupFieldWithPicker
	Write-Host $pool_field.AllowMultipleValues #True
	
	$pool = $pool_field.GetFieldValue($item["lookup_with_picker_field"].ToString())
	#exception here

	[Microsoft.SharePoint.SPFieldLookupValue] $new_lookup_value = New-Object Microsoft.Sharepoint.SPFieldLookupValue
	$new_lookup_value.LookupId = $item_to_add.ID

	$pool.Add($new_lookup_value)
	$item["lookup_with_picker_field"] = $pool
	$item.Update()

Exception:

You cannot call a method on a null-valued expression.
At :line:30 char:74
+     $pool = $pool_field.GetFieldValue($lookup_item[$pool_field_name].ToString <<<< ())

This snippet worked for generic multi-lookup type,

so how can I manipulate LookupWithPicker with powershell?

Thanks.

(I am using MOSS 2007)