<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Adventures in Consulting</title><link>http://blogs.msdn.com/valdon/default.aspx</link><description>This is a place for me to share those little gems one finds when doing consulting work.  Since I focus on Windows SharePoint Services 2007 (WSS) and Microsoft Office SharePoint Server 2007 (MOSS), most of the posts will cover topics relating to those products.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>FF at the End of a Content Type ID Kills Update Propagation</title><link>http://blogs.msdn.com/valdon/archive/2009/12/04/ff-at-the-end-of-a-content-type-id-kills-update-propagation.aspx</link><pubDate>Sat, 05 Dec 2009 00:25:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9932849</guid><dc:creator>Valdon</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9932849.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9932849</wfw:commentRss><description>I just spent a couple of hours tracking down an issue where our content type update code wasn’t working for some content types.&amp;#160; The problem ended up being that one content type in the hierarchy had a content type ID that ended with “FF” (such as...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/12/04/ff-at-the-end-of-a-content-type-id-kills-update-propagation.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9932849" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/Content+Types/default.aspx">Content Types</category></item><item><title>Creating Several List Instances in a Single Feature</title><link>http://blogs.msdn.com/valdon/archive/2009/08/06/creating-several-list-instances-in-a-single-feature.aspx</link><pubDate>Thu, 06 Aug 2009 17:05:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9859363</guid><dc:creator>Valdon</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9859363.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9859363</wfw:commentRss><description>I’m not sure why I didn’t find this earlier, but I have always put a single list instance definition into a single feature. However, I recently had to put together several inter-related lists into a feature (no single list was useful by itself). The first...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/08/06/creating-several-list-instances-in-a-single-feature.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9859363" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category></item><item><title>Removing Extra Workflow Status Column in Default View</title><link>http://blogs.msdn.com/valdon/archive/2009/05/05/removing-extra-workflow-status-column-in-default-view.aspx</link><pubDate>Wed, 06 May 2009 05:25:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9590222</guid><dc:creator>Valdon</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9590222.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9590222</wfw:commentRss><description>When SharePoint starts a workflow on a list for the first time, it has this annoying behavior of adding a workflow status column to the default view of the list. Often times, this information is of no practical use for end users. Unfortunately, there...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/05/05/removing-extra-workflow-status-column-in-default-view.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9590222" width="1" height="1"&gt;</description></item><item><title>Using Calculated Fields to Pad Numbers with Leading Zeros</title><link>http://blogs.msdn.com/valdon/archive/2009/05/05/using-calculated-fields-to-pad-numbers-with-leading-zeros.aspx</link><pubDate>Tue, 05 May 2009 23:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9589616</guid><dc:creator>Valdon</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9589616.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9589616</wfw:commentRss><description>Just a quick note on one way to put leading zeros in a SharePoint list field using a Calculated Field. A client wanted a column to show the list item's name, followed by a number that was left-padded with zeros to two digits, like: Addendum-01 Addendum-02...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/05/05/using-calculated-fields-to-pad-numbers-with-leading-zeros.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9589616" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category></item><item><title>How to work around bugs in the SPGridView control</title><link>http://blogs.msdn.com/valdon/archive/2009/03/11/how-to-work-around-bugs-in-the-spgridview-control.aspx</link><pubDate>Thu, 12 Mar 2009 03:11:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9471155</guid><dc:creator>Valdon</dc:creator><slash:comments>4</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9471155.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9471155</wfw:commentRss><description>SharePoint has a little known web control called SPGridView. This control can give you a SharePoint list-like view of data from any data source you can bind to (from a database or other sources). It also has features to sort, filter and group the data...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/03/11/how-to-work-around-bugs-in-the-spgridview-control.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9471155" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/C_2300_/default.aspx">C#</category></item><item><title>Using Both Field and FieldRef in InfoPath List Loses Data</title><link>http://blogs.msdn.com/valdon/archive/2009/01/23/using-both-field-and-fieldref-in-infopath-list-loses-data.aspx</link><pubDate>Sat, 24 Jan 2009 00:13:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9373178</guid><dc:creator>Valdon</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9373178.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9373178</wfw:commentRss><description>It appears that if you have both a Field and a FieldRef definition in your SharePoint list definition file that includes XML (InfoPath) field promotion, you can no longer update the field through the list; you must do it through the XML only. I ran into...(&lt;a href="http://blogs.msdn.com/valdon/archive/2009/01/23/using-both-field-and-fieldref-in-infopath-list-loses-data.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9373178" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/InfoPath/default.aspx">InfoPath</category></item><item><title>Getting To the Root (Well Almost) - Navigating the SPWeb Hierarchy</title><link>http://blogs.msdn.com/valdon/archive/2008/11/11/getting-to-the-root-well-almost-navigating-the-spweb-hierarchy.aspx</link><pubDate>Wed, 12 Nov 2008 01:13:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9060873</guid><dc:creator>Valdon</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/valdon/comments/9060873.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=9060873</wfw:commentRss><description>Recently I was faced with the problem of finding an ancestor web (SPWeb object) of the current web. The ancestor needed to be the one just below the RootWeb. I quickly put together a solution that worked, but I later realized that it had massive memory...(&lt;a href="http://blogs.msdn.com/valdon/archive/2008/11/11/getting-to-the-root-well-almost-navigating-the-spweb-hierarchy.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9060873" width="1" height="1"&gt;</description></item><item><title>Empty Active Directory Groups do not Show up for SharePoint 2007 Audiences</title><link>http://blogs.msdn.com/valdon/archive/2008/09/08/empty-active-directory-groups-do-not-show-up-for-sharepoint-2007-audiences.aspx</link><pubDate>Tue, 09 Sep 2008 00:27:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8934893</guid><dc:creator>Valdon</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/valdon/comments/8934893.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=8934893</wfw:commentRss><description>I ran into an interesting issue at a customer site. They had dozens of newly created Active Directory groups, but only two of them were showing up when they wanted to create a new audience or specify one of the groups as a target for a list item. It turns...(&lt;a href="http://blogs.msdn.com/valdon/archive/2008/09/08/empty-active-directory-groups-do-not-show-up-for-sharepoint-2007-audiences.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8934893" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/Active+Directory/default.aspx">Active Directory</category></item><item><title>Lookup Helper Methods</title><link>http://blogs.msdn.com/valdon/archive/2008/06/16/lookup-helper-methods.aspx</link><pubDate>Mon, 16 Jun 2008 17:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8605578</guid><dc:creator>Valdon</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/valdon/comments/8605578.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=8605578</wfw:commentRss><description>Sometimes when writing custom code for SharePoint, you want to open the list to which another list field is referring (when it uses a lookup field). I had to do this to put the lookup field values in a custom menu item. Other times, you just want the...(&lt;a href="http://blogs.msdn.com/valdon/archive/2008/06/16/lookup-helper-methods.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8605578" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/C_2300_/default.aspx">C#</category></item><item><title>Wrapping Text in a SharePoint WebPart Title</title><link>http://blogs.msdn.com/valdon/archive/2008/04/25/wrapping-text-in-a-sharepoint-webpart-title.aspx</link><pubDate>Sat, 26 Apr 2008 03:29:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8425069</guid><dc:creator>Valdon</dc:creator><slash:comments>3</slash:comments><comments>http://blogs.msdn.com/valdon/comments/8425069.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=8425069</wfw:commentRss><description>An interesting bit of CSS formatting behavior that I ran across recently at a customer site. They wanted to be able to have long titles in some of their web parts, but it would always make the web part zone expand to fit the text rather than wrapping...(&lt;a href="http://blogs.msdn.com/valdon/archive/2008/04/25/wrapping-text-in-a-sharepoint-webpart-title.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8425069" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/CSS/default.aspx">CSS</category></item><item><title>Accessing images and other binary files in blob fields through SharePoint BDC</title><link>http://blogs.msdn.com/valdon/archive/2008/04/24/accessing-images-and-other-binary-files-in-blob-fields-through-sharepoint-bdc.aspx</link><pubDate>Fri, 25 Apr 2008 06:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8423321</guid><dc:creator>Valdon</dc:creator><slash:comments>5</slash:comments><comments>http://blogs.msdn.com/valdon/comments/8423321.aspx</comments><wfw:commentRss>http://blogs.msdn.com/valdon/commentrss.aspx?PostID=8423321</wfw:commentRss><description>There are many applications that store binary data in blob or varbinary fields of a database, including pictures, Office documents, PDFs and other types of documents. Recently, a customer had the need to display, in SharePoint, an image stored in an Oracle...(&lt;a href="http://blogs.msdn.com/valdon/archive/2008/04/24/accessing-images-and-other-binary-files-in-blob-fields-through-sharepoint-bdc.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8423321" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/valdon/archive/tags/SharePoint/default.aspx">SharePoint</category><category domain="http://blogs.msdn.com/valdon/archive/tags/MOSS/default.aspx">MOSS</category><category domain="http://blogs.msdn.com/valdon/archive/tags/C_2300_/default.aspx">C#</category><category domain="http://blogs.msdn.com/valdon/archive/tags/BDC/default.aspx">BDC</category><category domain="http://blogs.msdn.com/valdon/archive/tags/SQL+Server/default.aspx">SQL Server</category></item></channel></rss>