<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infopath on Matt Thornton</title>
    <link>http://localhost:1313/tags/infopath/</link>
    <description>Recent content in Infopath 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="http://localhost:1313/tags/infopath/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tip: infopath comments and newline textbox</title>
      <link>http://localhost:1313/tech/sharepoint/infopath-comments-newline-textbox/</link>
      <pubDate>Tue, 26 Apr 2011 10:21:12 +0000</pubDate>
      
      <guid>http://localhost:1313/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>Visual Studio 2010 Workflow &#43; Infopath 2010 forms - troubleshooting</title>
      <link>http://localhost:1313/tech/visual-studio-2010-workflow-infopath-2010-forms-troubleshooting/</link>
      <pubDate>Mon, 28 Mar 2011 21:58:33 +0000</pubDate>
      
      <guid>http://localhost:1313/tech/visual-studio-2010-workflow-infopath-2010-forms-troubleshooting/</guid>
      
        <description>&lt;p&gt;Microsoft markets that Sharepoint Designer workflows are directly exportable to Visual Studio workflows. And in many ways, this is absolutely true. It&amp;rsquo;s trivial to create a .wsp from an SPD workflow and import it to VS. However, if you then inspect the workflow that has been created for you, a little concern would not be underestimated. If your SPD workflow was what you wanted, then you could be reasonably confident that its VS version would do the same job. But presumably your reason for importing to VS is because you need more control over the workflow in the longer term, in which case, you&amp;rsquo;re likely to be left underwhelmed by what the import process creates for you. Imagine creating a webpage in Microsoft Word and you&amp;rsquo;ll get the drift.&lt;/p&gt;
&lt;p&gt;So when faced with a similar proposition, recreating the workflow in Visual Studio from scratch immediately became apparent as the best solution. After all, the intent and purpose of the workflow was clear; recreating it in VS ought to have been a doddle. However, to complicate matters, the SPD workflow used Infopath edit forms. This turned out to be easy in SPD, but non-trivial in Visual Studio. Getting an Infopath form to register with a VS workflow project requires various items, that VS may not do automatically for you.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>