SharePoint 2010 Autocomplete Lookup Field

New Post: Global vs Web App Deployment

nadeemyousuf — Sat, 16 Mar 2013 07:19:20 GMT

Simply changing the scope won't help. The fact is Custom Field development involves Control templates and field types xml both of which are deployed to 14 hive.
And hence the field is available globally.

New Post: Global vs Web App Deployment

wajackson61 — Fri, 15 Mar 2013 15:29:46 GMT

nadeemyousuf,

Are you saying no easy way to do this' because of how it was designed' or even 'no easy way to do this even changing the scope via source code in visual studio'?

Thanks

New Post: Global vs Web App Deployment

nadeemyousuf — Fri, 15 Mar 2013 15:18:30 GMT

I am afraid there is no easy way of doing that.

New Post: Global vs Web App Deployment

wajackson61 — Wed, 13 Mar 2013 16:37:40 GMT

We need this solution to be deployed to a single web-application versus globally - is this possible? How?

Thanks

Closed Issue: Error while searching [1207]

nadeemyousuf — Wed, 30 Jan 2013 11:42:07 GMT

Hi!

I have installed your field, but when I type a value I got an error message: Resource not found for the segment ...

I have used it inside a second site collection on a webapplication http://server/sites/dev
Comments: Fixed issue with non alphanumeric characters in the List title and Field title.

Created Release: Fixed issue with non alphanumeric characters. (Jan 30, 2013)

nadeemyousuf — Wed, 30 Jan 2013 11:41:12 GMT

Fix for issue 1207: Fixed issue with non alphanumeric characters in the List title and Field title.

Released: Fixed issue with non alphanumeric characters. (Jan 30, 2013)

Wed, 30 Jan 2013 11:41:12 GMT

Fix for issue 1207: Fixed issue with non alphanumeric characters in the List title and Field title.

Source code checked in, #22666

nadeemyousuf — Wed, 30 Jan 2013 11:32:51 GMT

Fix for issue 1207: Fixed issue with non alphanumeric characters in the List title and Field title.

Commented Issue: Error while searching [1207]

nadeemyousuf — Fri, 25 Jan 2013 14:37:13 GMT

The reason I am using List Title and not list URL is because I use REST to query the list. I have blogged about the REST findings [here](http://sharepointnadeem.blogspot.in/2012/01/sharepoint-2010-rest-api.html).
Meanwhile I will try to look into the dot issue and will update the code ASAP.

Commented Issue: Error while searching [1207]

bonm014 — Fri, 25 Jan 2013 13:37:11 GMT

The problem within your code is larger than the dot. You use the title of the list as the url. this is not correct you have to use the url of the list to define the location of the list.

Inside AutocompleteLookupFieldControl.cs you use:
string lookupListName = lookupList.Title;
control.LookupListName = lookupListName.Replace(" ", "");

Change the title to the url and then check whatelse you have to do. The url can still remain a DOT, this needs to be removed aswell.

Commented Issue: Error while searching [1207]

bonm014 — Fri, 25 Jan 2013 09:38:42 GMT

Fixed it, the problem was that my listname contains a dot '.'. The Listdata.svc removes the dot. So I have changed your AutocompleteControl.ascx that the dot will be removed.

Maybe a nice one to implement inside your solution

Created Issue: Error while searching [1207]

bonm014 — Fri, 25 Jan 2013 09:24:43 GMT

Reviewed: Fixed issue with having special characters (Dec 25, 2012)

riolinx — Wed, 26 Dec 2012 07:55:15 GMT

Rated 5 Stars (out of 5) - Excellent implementation, which support multi-valued fields

New Post: Sharepoint 2013?

nadeemyousuf — Fri, 30 Nov 2012 06:16:15 GMT

Unfortunately not at this time. And honestly I haven't got any chance to work on SharePoint 2013 yet.

New Post: Sharepoint 2013?

Tailslide — Fri, 30 Nov 2012 00:26:54 GMT

Seems to almost work but displays all the html for the lookup link on my library as text. Any chance of an update?

Source code checked in, #19629

Project Collection Service Accounts — Mon, 01 Oct 2012 20:29:21 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #19628

Project Collection Service Accounts — Mon, 01 Oct 2012 20:27:32 GMT

Checked in by server upgrade

New Post: Two problems

draxtor — Wed, 29 Aug 2012 13:51:22 GMT

I have two problems with this solution.

First it only shows up in some web applications and site collections. In some of them not. I've installed solution and deployed it globally. Is there some dependency feature that I have to turn on in order to use this solution?

Second problem is that it doesn't work. I get javascript alert saying (colors is my lookup list)

{

"error":{

"code":"","message":{

"lang":"sr-Latn-CS","value":"Resource not found for the segment 'colors'."

}

New Post: Edit in datasheet functionality

nadeemyousuf — Sun, 15 Jul 2012 09:22:28 GMT

Hi yoshitoshi,

I don't see this error in IE 9.

New Post: Edit in datasheet functionality

nadeemyousuf — Sun, 15 Jul 2012 08:01:29 GMT

Hey bbrown1000,

You are right, this is a limitation with Custom Fields. They are readonly in datasheet view.