If you’ve had this problem, then two things to make you feel better:
This post, meanders a bit, so if you want the solution, jump to the bottom.
Still here? Sucker.
So, what are the prerequisites to causing this problem:
I think that’s it.
The web part will display correctly anywhere in your root web, but nowhere else. I’m calling it a “web” here because it maps to how Sharepoint’s API. If it helps for you to think about it as a single “Site” in WSS2.0 fashion, go nuts. When you visit subsites, you see the following error:
“Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.”
How helpful, especially if you’re an administrator or developer. As if they’d have a magic wand to fix the problem. The error might as well say:
“You’re screwed. Unless you’re a clever developer, give up, swear at Sharepoint and call tech support. Not many people at your company are going to be able to help you.”
Which is silly, because once we come to the cause, the error is completely within the realms of detection. To the developer who wrote that line of code… 10 minutes on the naughty step.
The problem is seemingly unresolveable. If you try to add the dataview directly to a page in a subsite, it works fine, but master page? Sharepoint tells you to go whistle.
The cause? Sharepoint doesn’t know which “web” the list comes from.
The Dataview web part can take parameters, including, parameters which tell pages where to find a list. In Sharepoint Designer, when you edit a master page, it fails to insert a parameter telling pages the list lives in the root.
Bad Sharepoint Designer! Bad!
The problem compounded because taking a dataview created on a subsite and dumping the code into the masterpage doesn’t work either (which makes it very tricky to solve).
To figure this out, I took the following steps in Sharepoint Designer:
A side-by-side comparison revealed several things…
First, the datasource control (a child of the dataview web part) is referred to with a different namespace in the master page than in the page itself. This is why you can’t copy dataview code from a regular page into a master page. Maybe there’s a good reason for having done this, but I think the masterpage programmer forgot to speak to the regular page programmer. However, that isn’t the root cause, but something to be aware of.
Second, THERE’S ANOTHER PARAMETER. OMG!!! Froth, swear, stomp, swear, slam your keyboard. Feel better?
Knowing a parameter exists and knowing the syntax are two different things. Before finding the actual code, I was pretty confident the problem was down to subsites not knowing where the list was.
The worst thing is that the url of the web is actually part of the dataview web part, down at the very bottom of the code. Why doesn’t this flow through to the datasource? Naughty step!
It’s simple enough to copy the parameter from the subsite dataview into the masterpage dataview.
<WebPartPages:DataFormParameter Name=”WebURL” ParameterKey=”WebURL” PropertyName=”ParameterValues” DefaultValue=”/”/>
I don’t believe the approach is necessary if you’re referring to a list in a subsite (the parameter should be inserted automatically).
Hope that helps!
Spent the past several days working out of our Frankfurt office, trying out some things and speaking with people about their knowhow needs.
In the meantime, we have been using templates a lot and are desperate for several key extensions to be installed. Can’t wait. One everything is in place, watch out.
Have just got home after a much delayed flight. Quite tired and have a bit more work to do before sleep and my 29th birthday.
Well, here we go. Three days later, one server, one personal wiki and one personal blog. The wiki has been secured, as it’s for my personal use only. I’ll be setting up a shared KM wiki for use by myself and Matthew Parsons. Hopefully the wiki skin can be shared, although I’m not really keen to develop and support something for full cross-browser use. Firefox, IE and Safari should be sufficient, sorry Opera fans. The wiki skin will probably be ported to wordpress to give the site a consistent look.
As it stands Matthew and I are looking at sharing thoughts on Powerpoint, Microsoft Office and Wikis for use as an enterprise KM tool among other things. We’re also keen to experiment and play with emerging technology.
So. Nobody is going to read this first post. But, you need to start somewhere, so…
here we go!