SharePoint Skater

Hiding buttons on the SharePoint ECB with JavaScript

2012-05-10T20:34:00Z

Some of my best discoveries come from forum questions. Not that I'm the first one to discover it, mind you -- I'm well aware that my wheel has probably been invented countless times -- but my mind grows best when I have to research a solution for someone else's problem (maybe that's why I like consulting).

Today's question was a simple one: how do I remove the Edit Item and Workflows buttons from the ECB (Edit Control Block) in a particular list view? If you're not familiar with the ECB for a list item, go to a list and select any list item; the List Item ECB will appear in the ribbon with commands like New Item, New Folder, etc.

Since a list view is just an aspx file, we can add some client-side code -- either directly in the page, or by way of the Content Editor Web Part. Our code depends on jQuery, and looks like this:

$("td").hover(function() {
	hideEditAndWorkflows();
});
$("input").hover(function() {
	hideEditAndWorkflows();
});
function hideEditAndWorkflows() {
	$("#Ribbon\\.ListItem\\.Workflow").css("display", "none");
	$("#Ribbon\\.ListItem\\.Manage\\.EditProperties-Large").remove();
	}

If you're a jQuery novice, you'll want to visit jQuery.com and get the latest version -- simply upload the necessary JS file to a library and add a script link to it in the page (there's a ton of reference material out there, including the excellent documentation at the jQuery site).

You may wonder at the backslashes we're using in the hideEditAndWorkflows function. Since these element IDs contain special characters (normally the dot denotes a class in CSS selectors), we have to escape them so that we can pass them properly through the system.

Once you have this code in place, you'll see the Edit and Workflows buttons for a moment after clicking the first list item on the page; after that, they should disappear and be completely unavailable to your average user.

Of course, client-side techniques like this will only go so far; if someone is technically adept and has the ability to perform these operations, he or she can open up the developer console and find the missing pieces. Be aware of this whenever you manipulate the SharePoint UI with JavaScript; while it's fun and easy, this technique should never be a substitute for proper governance.

Enjoy!

Error when creating a site from a custom template: "A duplicate name 'FieldName' was found"

2012-05-08T21:01:00Z

This happened to me in a client's WSS3 environment, but it seems to apply to 2010 as well. I had a site template created in one environment, but upon moving it to another, the Create Site operation resulted in a neat little error, complete with stack trace: "A duplicate name 'YourField' was found". Upon investigating, I found that one of the lists in the newly-created site did indeed have duplicate fields. What was odd in this case was that the the list was based on a content type, and only one of the duplicates came from said content type. I deleted the extra fields, re-saved the template in the new environment, and created again -- only to have similar results. Several forum posts recommend cutting open the template on your local machine, editing the XML, and rebuilding the solution CAB, but in my case, all it took was a quick "Delete list" followed by re-creating it and re-adding the content type. Save as template again, and this time -- instant site creation satisfaction.

SharePoint Saturday Houston: 9 days and counting

2012-04-18T19:05:00Z

In just over a week, I'll be speaking at SharePoint Saturday Houston. My topic will be Manipulating SharePoint with Client-Side JavaScript; we'll address client-side coding as a whole, look at the Client-Side Object Model, and then dive into a working sample app using the CSOM and jQuery. Come see how easy it is to develop complex solutions for SharePoint 2010 without ever opening Visual Studio.

The event is already chock-full of high-profile speakers and generous sponsors (and a few guys like me, with a session right after the huge gourmet lunch) -- and with just over 100 seats left, you'll want to register right away. Hope to see you there!

SharePoint Client Object Model: Step One

2012-04-10T19:12:00Z

I almost didn't make it out alive. I followed the instructions in every piece of sample code and every forum post by someone who had no idea why their client OM code wasn't working, and my code still wouldn't get past the page load. I kept getting "'Type' is undefined" errors when sp.core.js tried to register the SP namespace.

As it turns out, you need the help of the default master page (or one like it) to get the object model loaded. Once I told my sample page to use the default master and modified everything accordingly, it hooked up and ran just fine.

Now I can finally get some work done.

Agility in SharePoint: Writing Functional Requirements

2012-02-03T16:52:00Z

SharePoint brings more power than ever to the end user. As usual, this is a double-edged sword. Its utility as a development platform is unmatched, but since many of the development tools are accessible from the browser UI, the dividing lines can get blurred.

Requirements-gathering (and subsequent documentation) can be tricky, and it's easy for us technical types to get confused about functional versus technical. Business users do not care about technical requirements and they should not have the opportunity to dictate them. If you have to explain a term (for example, "list" or "metadata column") to an end user, then most likely it does not belong under the heading of "functional requirements".

Functional requirements are about what the end user needs to accomplish. An excellent guide for this is the concept of the User Story, as employed in Agile project management (we're kind of big on that here at Improving). The basic format is as follows:

As a _______ (what type of user),

I want _________

so that I can ___________

This kind of requirement requires (heh) that you also define acceptance criteria, by which you can determine that the requirement has been fulfilled. The end result is that nobody can claim confusion about what you're trying to do, since the team has already agreed on the definition of "done".

Non-technical hiatus: Movember

2011-11-29T16:20:00Z

Here at Improving Enterprises, we have a relatively new annual tradition of forming a moustache team for Movember. For those who are new to the concept, Movember is a month-long fundraising effort for men's cancer research. Each year, men (Mo Bros) from around the world join in sprouting a symbol of solidarity -- with the goal of eradicating men's cancers.

If you're able, please consider donating to this vital effort. You can read up on where the money goes and how it is spent, you can learn about the history of Movember, and of course you can see goofy pictures of me with incomplete facial hair (if you're into that sort of thing).

Thank you for your time, your money, or merely your attention. To show my gratitude, here's what the genetic recombination of Burt Reynolds and Derek Zoolander would look like if he had some sort of mental problem.

"The requested operation requires elevation"

2011-07-13T21:20:00Z

Typical SharePoint 2010 install. I had created all my domain users, set up my servers, and started installing the prerequisites. When the first box in the farm restarted and the preparation utility came up, I was asked for credentials and provided them, only to be rejected. At first I thought it was a standard "access denied" error, but a look at the fine print revealed the error titling this post.

I tried Run As Administrator; still no success.

Eventually I realized that I was signed in as the farm account, though I had not yet made it a local administrator. I right-clicked Computer Management, ran THAT with the proper credentials, made the farm account local admin, and all was right with the world.

Sometimes it's the little things.

"The data source control failed to execute the insert (or update) command", or How to Make Your Workday a Bit Shorter

2011-05-27T16:08:00Z

Custom list. Custom New/Edit/View forms. Everything works perfectly... until the latest round of updates.

Now if you Bingle this error message, you'll get about twenty possible causes that run the gamut from a known bug, an unknown bug, and fixed/not fixed/hotfixed/workaround bug, all the way to corrupt content types and invalid form data.

In my case, however, it turned out to be a misspelled column name in a FormField control.

I'm just glad it's Friday.

Removing the 12:00 timestamp from Calendar View

2011-05-04T21:33:00Z

Occasionally, you have a calendar full of all-day events and you don't want the calendar cluttered up with redundant timestamps. Here's a simple client-side script, suitable for framing (or a master page, or a content editor web part) that will cut down on the visual noise.

<script language="JavaScript">
var allDates = document.getElementsByTagName("nobr");
for(var i=0;i 0) {
      allDates[i].innerHTML = allDates[i].innerHTML.replace("12:00 AM","");
    }
  }
</script>

Nitpicking that matters: changing default forms on a SharePoint 2007 list

2011-04-20T19:34:00Z

This is a fairly common request, but the solution is often missing one crucial point. To use a custom New/Edit/Display form on your list, proceed as follows:

Open your site in SharePoint Designer.
Right-click the desired List (under the Lists node) and select Properties.
Click the Supporting Files tab.
Under Content type specific forms, select the Item content type (this is the part most people forget). If you are using a custom content type, select that; just make sure that the Folder type is NOT selected.
Use the Browse button to select your custom forms in each category.
Click OK.

SharePoint Designer workflow workarounds: tracking individual column changes

2011-03-07T15:46:00Z

This post is long overdue, but since the question keeps popping up on various SharePoint discussion lists, I figured I'd document the answer here (next time I can just post a link instead of typing the whole thing out again).

In a SPD workflow, you cannot trigger a SharePoint workflow when a column changes; you can only use the ItemChanged event. To get more granular, then, you need to add some extra bits.

Let's say you have a list called "5K Races" with a column called StartTime, and you want to execute some actions when the StartTime value changes. Simply perform the following steps:

1) Create an additional column (same datatype) called OldStartTime.

2) When the workflow starts, compare StartTime to OldStartTime.

a) If they are equal, then do nothing (end).

b) If they are NOT equal, proceed with your workflow.

3) If 2b, then set OldStartTime to the value of StartTime.

By performing step 3, you ensure that by the end of the workflow, OldStartTime will be equal to StartTime -- this is important because the workflow will continue to run every time a particular item is changed, but by taking away the criterion that would cause the workflow to run the second time, you have avoided an endless loop situation.

Read-only lock on a SharePoint site collection, or Why can't I edit anymore?

2011-03-01T16:01:00Z

Monday morning, the calls started. For some reason, long-time users were unable to edit list items. I figured we had a permissions issue, so I popped in to look at the Site Settings -- and found that I couldn't. A quick trip to Central Administration showed that I was still listed as a Site Collection Administrator, but I had no power at all on the site collection in question.

A quick glance at the logs told me that the server had recently shut down unexpectedly (this is a Hyper-V virtual machine). Apparently, in the confusion, somehow SharePoint decided to lock the site collection as Read Only. This can be remedied in one of two ways:

1) In Central Administration, go to Application Management->SharePoint Site Management->Site collection quotas and locks. Once you have arrived, select the correct application and site collection, and you will have the opportunity to view and set the lock status of the collection (it most likely will be set to "Read-only", and you'll want to move that radio button to "Not locked").

2) Fire up stsadm and issue the following command:

stsadm -o setsitelock -url http://myportalsitecollection -lock none

Phone number mask in a DataView WebPart (DVWP)

2010-12-07T16:34:00Z

This came up today on the [sharepointdiscussions] list. A user needed to display a read-only field in a phone number format; it's pretty simple, but it may be just what you need.

Assuming your list item contains a field called "Phone Number" (with a space), the following XPath will give you a number in the classic US telephone format:

<xsl:value-of select="concat('(',substring(@Phone_x0020_Number,1,3),')',substring(@Phone_x0020_Number,4,3),'-',substring(@Phone_x0020_Number,7,4))" />

If you need to mask an input, try this jQuery solution.

Generate a Word document from list data

2010-12-06T16:24:00Z

This came up on a discussion list lately, so I threw together some code to meet the need. In short, a colleague needed to take the results of an InfoPath form survey and give them to the user in Word format. The form data was already in a list item, so it was a simple matter of using the SharePoint API to get the list item, formatting the data appropriately, and using response headers to make the client machine treat the response as MS Word content.

The following rudimentary code can be run in an ASPX (or an assembly) in the 12 hive. When you link to the page, send the list name and item ID in the querystring and use them to grab the appropriate data.

// Clear the current response headers and set them up to look like a word doc.
HttpContext.Current.Response.Clear();
HttpContext.Current.Response.Charset ="";
HttpContext.Current.Response.ContentType ="application/msword";
string strFileName = "ThatWordFileYouWanted"+ ".doc";
HttpContext.Current.Response.AddHeader("Content-Disposition", "inline;filename=" + strFileName);

// Using the current site, get the List by name and then the Item by ID (from the URL).
string myListName = HttpContext.Current.Request.Querystring["listName"];
int myID = Convert.ToInt32(HttpContext.Current.Request.Querystring["itemID"]);
SPSite oSite = SPContext.Current.Site;
SPWeb oWeb = oSite.OpenWeb();
SPList oList = oWeb.Lists["MyListName"];
SPListItem oListItem = oList.Items.GetItemById(myID);

// Build a string with the data -- format it with HTML if you like.
StringBuilder strHTMLContent = newStringBuilder();

// *
// Here's where you pull individual fields out of the list item.
// *

// Once everything is ready, spit it out to the client machine.

HttpContext.Current.Response.Write(strHTMLContent);
HttpContext.Current.Response.End();
HttpContext.Current.Response.Flush();

Simple Pleasures in SP 2010: TryGetList method

2010-10-05T17:19:00Z

How many times has this happened to you?

SPSite site = new SPSite("url");
SPWeb web = site.OpenWeb();
SPList list = web.Lists["ListName"];
ERROR!!!

...because, of course, that list happens not to exist! Have you ever wished for a better approach than either "Try...Catch" or "loop through the whole mess"?

You just got your wish.

SharePoint 2010 includes a brand-new method on the SPListCollection, called TryGetList. This method returns a list if successful, but if not, it returns -- get this -- a null value! No more clumsy extra logic blocks every time you need to do something simple like grabbing a list. It's not rocket science, but the great innovations rarely are.