<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Comments on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/comments/</link>
    <description>Recent content in Comments on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 26 Apr 2011 10:21:12 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/comments/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tip: infopath comments and newline textbox</title>
      <link>https://matt-thornton.net/tech/sharepoint/infopath-comments-newline-textbox/</link>
      <pubDate>Tue, 26 Apr 2011 10:21:12 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/infopath-comments-newline-textbox/</guid>
      
        <description>&lt;p&gt;One method for persisting data in a SharePoint environment is the use of Infopath forms. Infopath stores data in your form in XML format. I have a form which has a “comments” box where people add new comments as they progressively update the form and a “consolidate comments” box which shows all previous comments*. However, Infopath forms don&amp;rsquo;t natively support appending new data to existing data - and new comments added may blow away any previous comments.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>Force comment entry when editing a list item</title>
      <link>https://matt-thornton.net/tech/sharepoint/sharepoint-force-comment-entry-when-editing-a-list-item/</link>
      <pubDate>Wed, 10 Feb 2010 11:28:58 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/sharepoint/sharepoint-force-comment-entry-when-editing-a-list-item/</guid>
      
        <description>&lt;p&gt;Quick tip: custom lists are a great way to store data about a business process or operation that doesn&amp;rsquo;t necessarily fit in a standard list. They can be used to store virtually any type of data, that makes sense in list form. For instance, you might record the configuration details of all the switches on your network. They&amp;rsquo;re especially helpful in that by enabling versioning on a list, you can create an audit trail of when things changed. Critically, though, when something changes, you&amp;rsquo;re likely to want to know why. Therefore, when someone changes an item, you might want to insist that they add a comment to quickly describe the change they have made, and why.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>