Category | InfoPath

Very often you need to retrieve a published InfoPath form, unfortunately, in SharePoint 2010 this is quite an ordeal.  In SharePoint 2007 you could simply open the InfoPath forms library in explorer view then open the forms directory and the template.xsn file would be readily visible.  In SharePoint 2010 the template.xsn file is now much better hidden/protected by SharePoint 2010.  In order to retrieve the document follow one of the two steps below. Method 1 The easiest method is to simply access the file via URL, keep in mind, when you publish the form its name is changed to template.xsn. ...

---

Problem You have a shiny new SharePoint 2010 environment and it’s running beautifully but you can’t create workflows.  Actually, some workflows that don’t have an InfoPath association screen do work, however, others, such as the 3 State Workflow don’t work.  Figure 1 below shows the 2nd screen of the 3 state workflow which is actually an InfoPath form, if you get an error on this screen then follow the steps in the solution below. Figure 1: InfoPath based 3 state approval workflow association screen Solution Firstly, before making any changes make test test test.  Do not make...

---

Problem Day after day I have users asking me how to get additional information about the selected user from the contact selector/people picker per my example at http://sharepointassist.com/2009/02/27/adding-a-contact-selectorpeople-picker-to-an-infopath-form/. Unfortunately, there is no easy way to do this, the only way to do this is to wire in a simple web service query that pulls the necessary information when a user chooses a name in the people picker. Upon selection, the web service call is made, returning data to the GetUserProfileByName data connection, the resulting data in the GetUserProfileByName...

---

Sometimes InfoPath doesn’t allow you to rename your main data source so you are stuck with a name that doesn't necessarily match with the function of the form.  This is very common for those of us that like to use Microsoft’s InfoPath templates as a head start.  For example, a form designed based upon an InfoPath sample may include the "expenseReport" name. This is quite annoying especially when you need to compile the datasource with the "xsd /c" command and the output classname is less than helpful.   Below is the example of a form data source that was created...

---

Problem You’re receive an error message when publishing a InfoPath form to a SharePoint server with forms services enabled.  Explanation I received this error while working on a web application other than the default (port 80) SharePoint site on the server.  For some reason when I created the new web application, which I verified was associated with an SSP, refused to render any InfoPath forms in a browser. Solution After lots of digging on Microsoft’s websites I cam up with the following solution.  Good luck! Login to your SharePoint server and run the following STSADM...

---