autocompleteLookup Discussions Rss Feed

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

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?

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.

New Post: Edit in datasheet functionality

yoshitoshi — Thu, 05 Jul 2012 14:10:18 GMT

Doesn't work in my IE9.

Error: method "autocomplete" not supported with this object.
Line 909, char 3, code 0

Agent:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8)

New Post: Edit in datasheet functionality

bbrown1000 — Wed, 04 Jul 2012 12:59:41 GMT

The autocomplete lookup field type works amazing in the NewForm and EditForm pages...even with over 10,000 items in the lookup lists. But in datasheet view, the autocomplete lookup field is read-only which means lookup values cannot added, edited, or bulk imported using the datasheet view. I think this is a design limitation of the custom field type framework. If so, is there a workaround? If it's not a limitation can you describe how it could work?