<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: SharePoint SPListItem quirks</title>
	<atom:link href="http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/</link>
	<description>Just another SharePoint developer blogging</description>
	<pubDate>Tue, 06 Jan 2009 03:58:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.8-bleeding-10187</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Erik Burger</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-707</link>
		<dc:creator>Erik Burger</dc:creator>
		<pubDate>Wed, 22 Oct 2008 06:29:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-707</guid>
		<description>Got to love those "quirks" eh? Excellent post, really useful. 

Does anyone have any deas on how we can prevent ourselves and our fellow devs from running into this problem? Use the InternalName attribute? I doubt that would make a difference but maybe I'm missing something. Use an extension method? And how would it look?

It would be interesting to know why MS doesn't provide a way to get a Field by its InternalName. I've run into a major problem using an MS template that references a Field by its DisplayName (details here: http://www.reversealchemy.net/2008/09/10/sharepoint-custom-templates-and-language-packs/). Why not use the InternalName? Wouldn't that make life easier?

Or am I *really* missing something?

Cheers,
Erik</description>
		<content:encoded><![CDATA[<p>Got to love those &#8220;quirks&#8221; eh? Excellent post, really useful. </p>
<p>Does anyone have any deas on how we can prevent ourselves and our fellow devs from running into this problem? Use the InternalName attribute? I doubt that would make a difference but maybe I&#8217;m missing something. Use an extension method? And how would it look?</p>
<p>It would be interesting to know why MS doesn&#8217;t provide a way to get a Field by its InternalName. I&#8217;ve run into a major problem using an MS template that references a Field by its DisplayName (details here: <a href="http://www.reversealchemy.net/2008/09/10/sharepoint-custom-templates-and-language-packs/" rel="nofollow">http://www.reversealchemy.net/2008/09/10/sharepoint-custom-templates-and-language-packs/</a>). Why not use the InternalName? Wouldn&#8217;t that make life easier?</p>
<p>Or am I *really* missing something?</p>
<p>Cheers,<br />
Erik</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kipper stiever</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-84</link>
		<dc:creator>kipper stiever</dc:creator>
		<pubDate>Thu, 08 May 2008 18:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-84</guid>
		<description>dude, what a PIA! i just ran into the same issue. thanks for the post, this would have taken me 3 days to figure out as well, no doubt.</description>
		<content:encoded><![CDATA[<p>dude, what a PIA! i just ran into the same issue. thanks for the post, this would have taken me 3 days to figure out as well, no doubt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Corra</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-83</link>
		<dc:creator>Joel Corra</dc:creator>
		<pubDate>Tue, 25 Mar 2008 20:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-83</guid>
		<description>You could probably turn this into a whole site dedicated to SharePoint quirks. For instance, one I came across recently is that if you update an SPListItem through the object model, and it has a Notes/Comments field with versioning enabled (one of the default fields on a Contact list), it blanks out the Notes field--if you check the version history, it actually shows Notes being set with a blank value.  The original notes then no longer show in any Data Sheet view.  However, that doesn't happen if you update the item through the regular SharePoint interface.

Bil Simser has also documented at least 2 "quirks" with the AddFieldAsXml method of the SPList:

AddFieldAsXml cannot be used to set the InternalName correctly
http://weblogs.asp.net/bsimser/archive/2005/07/21/420147.aspx
SharePoint basically ignores the InternalName property in the XML definition and uses the DisplayName for the both the internal name and display name.

AddFieldAsXml... I wish this monkey would go away
http://weblogs.asp.net/bsimser/archive/2005/07/27/420766.aspx
The properties of the  node in the XML definition have to be in a certain order, or it throws an error.</description>
		<content:encoded><![CDATA[<p>You could probably turn this into a whole site dedicated to SharePoint quirks. For instance, one I came across recently is that if you update an SPListItem through the object model, and it has a Notes/Comments field with versioning enabled (one of the default fields on a Contact list), it blanks out the Notes field&#8211;if you check the version history, it actually shows Notes being set with a blank value.  The original notes then no longer show in any Data Sheet view.  However, that doesn&#8217;t happen if you update the item through the regular SharePoint interface.</p>
<p>Bil Simser has also documented at least 2 &#8220;quirks&#8221; with the AddFieldAsXml method of the SPList:</p>
<p>AddFieldAsXml cannot be used to set the InternalName correctly<br />
<a href="http://weblogs.asp.net/bsimser/archive/2005/07/21/420147.aspx" rel="nofollow">http://weblogs.asp.net/bsimser/archive/2005/07/21/420147.aspx</a><br />
SharePoint basically ignores the InternalName property in the XML definition and uses the DisplayName for the both the internal name and display name.</p>
<p>AddFieldAsXml&#8230; I wish this monkey would go away<br />
<a href="http://weblogs.asp.net/bsimser/archive/2005/07/27/420766.aspx" rel="nofollow">http://weblogs.asp.net/bsimser/archive/2005/07/27/420766.aspx</a><br />
The properties of the  node in the XML definition have to be in a certain order, or it throws an error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sudhakar</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-82</link>
		<dc:creator>sudhakar</dc:creator>
		<pubDate>Thu, 12 Jul 2007 09:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-82</guid>
		<description>really helped me, good job, thanks</description>
		<content:encoded><![CDATA[<p>really helped me, good job, thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Online Collaboration + .Net + SharePoint = My Techie Life Adding item to sharepoint 2003 SPList Programmatically &#171;</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-81</link>
		<dc:creator>Online Collaboration + .Net + SharePoint = My Techie Life Adding item to sharepoint 2003 SPList Programmatically &#171;</dc:creator>
		<pubDate>Thu, 19 Apr 2007 11:29:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-81</guid>
		<description>[...] Please visit the original article: http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks for more infomation&#8230;   Posted in SharePoint, .Net. [...]</description>
		<content:encoded><![CDATA[<p>[...] Please visit the original article: <a href="http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks" rel="nofollow">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks</a> for more infomation&#8230;   Posted in SharePoint, .Net. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eddy</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-80</link>
		<dc:creator>Eddy</dc:creator>
		<pubDate>Fri, 06 Apr 2007 09:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-80</guid>
		<description>Thanks for this.
It is a disgrace that it is not documented in MSDN.</description>
		<content:encoded><![CDATA[<p>Thanks for this.<br />
It is a disgrace that it is not documented in MSDN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daz</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-79</link>
		<dc:creator>daz</dc:creator>
		<pubDate>Tue, 03 Apr 2007 10:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-79</guid>
		<description>it helped a lot!
si' si' ...</description>
		<content:encoded><![CDATA[<p>it helped a lot!<br />
si&#8217; si&#8217; &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Evets</title>
		<link>http://www.buro9.com/blog/2007/02/26/sharepoint-splistitem-quirks/comment-page-1/#comment-78</link>
		<dc:creator>Evets</dc:creator>
		<pubDate>Thu, 08 Mar 2007 12:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.buro9.com/2007/02/26/sharepoint-splistitem-quirks/#comment-78</guid>
		<description>thank you for those examples, it helps me a lot :)</description>
		<content:encoded><![CDATA[<p>thank you for those examples, it helps me a lot :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
