Comments on: Power User Toolbox: JavaScript for SharePoint – Pt5

By: Bag

Bag — Sat, 13 Feb 2010 13:08:43 +0000

You can use the list title “User Information List” instead of the GUID, but only from the root URL.

By: German Blogs

German Blogs — Sun, 18 Jan 2009 21:30:17 +0000

SharePoint Kaffeetasse #98…

Tools und Addons Custom Content Editor Web Part for SharePoint jQuery http://jquery.com/ jQuery is a…

By: larry

larry — Wed, 24 Dec 2008 17:04:52 +0000

Not having access to the administator directories of the SharePoint Server, I was only able to find the core.js. What is the location or URL I can use to download the list.js file also?

By: Power User Toolbox: JavaScript for SharePoint - Pt6 | End User SharePoint

Power User Toolbox: JavaScript for SharePoint - Pt6 | End User SharePoint — Fri, 12 Dec 2008 01:20:40 +0000

[...] A Mad Scientist JavaScript Developer Looking over the last two articles in this series, parts 4 and 5, some ideas may have popped into your head. “If I use the web service to get data then use [...]

By: Tom Winter

Tom Winter — Fri, 05 Dec 2008 14:25:54 +0000

Regarding “…we can normally use the list name (very cool) instead of the Globally Unique Identifier (GUID) as a parameter in the SPAPI_Lists function but I was not able to make that work in this situation…”

After some looking around I found this in Microsoft’s online documentation for the SharePoint Web Services under the Lists web service’s GetList Method:

Parameters: listName: A string that contains either the title or the GUID for the list. When querying the UserInfo table, the string contains “UserInfo”.

So use “UserInfo” as the name. This worked for me. The GUID for this list seems to be unique to each SharePoint install since mine (which I used before I found this tidbit) is different than the one used here.

http://msdn.microsoft.com/en-us/library/lists.lists.getlist.aspx

By: AutoSponge

AutoSponge — Mon, 01 Dec 2008 17:18:24 +0000

Krys Kujawa,

Accessing AD through a web service requires a web service for AD. That’s usually a C# or ASP.NET page that turns a web request into an LDAP query (from what I understand). There should be examples “out there” but it’s beyond the scope of my abilities or this article series.

Paul

By: SharePoint Daily

SharePoint Daily — Mon, 01 Dec 2008 14:16:28 +0000

SharePoint Daily for December 1, 2008…

Top News Stories SharePoint 2007 – Best Practices for Collaborative Portals (Sys-Con) It was the usual…

By: Krys Kujawa

Krys Kujawa — Mon, 01 Dec 2008 10:45:44 +0000

This looks really useful, but how does it work if all you get back from the User Information List are Windows Groups rather than Windows Users?

I’ve figured you can use the MembershipGroupId to limit the list to just check specific SharePoint Groups for a user (as opposed to the generic User Information List), but if the user is part of an AD Group (as per MS Good Practice for SharePoint) I don’t think the user will be found by Darren’s code, will it?

By: AutoSponge

AutoSponge — Sun, 30 Nov 2008 01:10:35 +0000

Rao,

While a simple “Welcome <>” web part may seem useless, it’s merely a demonstration of a powerful option available without .NET code or access to SPD that brings data to the page from an “outside” source.

For instance, combine the ability to bring the user’s manager’s name from an SP list (using the JavaScript API) and the ‘pre-populate a form field’ script from pt4. That’s something that a lot of people ask for–”automatically put my manager as the approver for a manually started workflow.”

Without hard specs to develop toward (or rather before you get the specs in hand), I feel it’s important to have a “toolbox” full of options. I didn’t want this series to start out with “solutions” but rather provide some building blocks and see how our readers put them together.

Of course, if you have specific requests, I’m all ears.

Paul

By: Rao

Rao — Sat, 29 Nov 2008 10:31:24 +0000

Hi,
Sorry for asking this question. What is the main aim of these parts on Power User ToolBox: Java Script on SharePoint.

Thanks,
Rao.