Tag / InfoPath

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...

---

Problem You've developed a custom workflow using Windows Workflow foundation, Visual Studio, and a nice little product called InfoPath, however, when you test your workflow you get the error message "This form cannot be opened. It is not workflow enabled." If this above change doesn't work follow the steps in this blog article about publishing a workflow enabled InfoPath form.   Resolution This form cannot be displayed properly because your security level is not set to "Domain". Open the form and republish it with the security level = "Domain"

---

Requirement You're creating a Visual Studio and Windows Workflow Foundation workflow for SharePoint and you would like to use InfoPath for the Workflow Initiation, Workflow Association, and Workflow Task Edit forms. Note: The final step is the most important step so don’t skip it. Solution Set the form's Security Level to "Domain" Now publish the form to a local network place **** Leave the access path BLANK ***

---