If you’ve read much of my blog in the past, you know that I’m a big fan of the Data View Web Part (DVWP). It’s my tool of choice in many cases to customize display of content from lists.
Many people are more aware of the Content Query Web Part (CQWP) because it can be added and manipulated within the SharePoint UI rather than needing to use SharePoint Designer. CQWPs also offer the advantage that they can show content from across a set of sites that meet various criteria, something that DVWPs can’t do.
So, with DVWPs, you get easy manipulation of the display (using SharePoint Designer), but only from a single list (or several if you can connect them), and with CQWPs, you get the ability to show content from across the Site Collection, but you have little formatting freedom.
There’s a new article (with a video) at MSDN that explains the basics of how you can expand the CQWP functionality to get more control over the display formatting. Check it out at:
Thanks to Joel Krist at Akona Systems for a great explanation.
UPDATE 2009-05-08: Wow. Sometimes I end up back at one of my old blog posts and I have to say “Wow”. My points about DVWPs here are fundamentally wrong, as DVWPs can quite easily show items from across the Site Collection using the Crosslist DataSourceMode. Search for “Crosslist” to see my more recent posts on this.
Today, in one of my occasional manual visits to Windows Update, I was offered the Office 2003 SP3 important update, but I am running Office 2007. My guess is that because I upgraded from Office 2003 that some widget or another is still around that makes Windows Update want to offer SP3 to me.
Methinks it’s not a good idea to install SP3, but if someone reads this who has a definitive answer, let us know!
Interesting post about some upcoming enhancements to Live Maps. From what I’ve been able to glean, these enhancements should be available on October 16th (or so).
Think of this: pretty soon you will be able build a Popfly mashup that shows a map of your recent trip with your route highlighted, with clickable pushpins that take you to a slideshow of your photos or your home movies from the location, all with your own narrative voiceover. How cool would that be? And it shouldn’t even be all that hard! (Assuming you have the time to do the small amount of work to make it happen.)
While trying to solve an unrelated problem (Why can’t I have a Rich Text column that works right in a Document Library in SharePoint?!?!? More on that later…), I ran across this great post on Keith Bunge’s blog (Click Mice, Unclick Mice): Data View Web Parts bound to List Names.
By binding your Data View Web Part to a list name rather than a list GUID, your DVWP can be portable!
I’ve found that if you create a Web Part Connection between two Web Parts using the SharePoint UI, you cannot reliably remove the connection. After you remove the connection, if you remove one of the connected Web Parts, you often get an error that SharePoint can’t find the identifier of the removed Web Part. This can leave your site in a permanently broken state.
The solution is to remove the connection in SharePoint Designer. Removing it there seems to do the job more completely.
UPDATE 10/1/2007: Just to elaborate a bit (since I ran into this again today), here’s the easy way to do this. If you get the error about the Web Part Connection, it will look like:
Could not find the connection provider Web Part with ID "g_2df2bab0_40ee_4955_9e8b_bfce21bb937f".
Copy that nice looking ID (g_2df2bab0_40ee_4955_9e8b_bfce21bb937f) and open the aspx page in SharePoint Designer. Go into code view and search for the ID. It will live in a code block that looks something like this, in one of the two locations highlighted in red:
<WebPartPages:SPWebPartConnection ID="g_D0184680A5C14C6286A98B8C8236B091" ConsumerConnectionPointID="DFWP Parameter Consumer ID" ConsumerID="g_ac7e15f7_3724_4a37_a059_9de6481a2835" ProviderConnectionPointID="DFWP Row Provider ID" ProviderID="g_2df2bab0_40ee_4955_9e8b_bfce21bb937f"> <asp:rowtoparameterstransformer ProviderFieldNames="@ID" ConsumerFieldNames="listItemID" />
The bolded section is what you want to delete. (If this is the only Web Part Connection on your page, you can also delete the <SPWebPartConnections></SPWebPartConnections> surrounding tags.)