Hans Muster's Library tagged infopath →  View Popular

Yes, I know this title sounds a bit odd, and the real title should be ‘When you are using an InfoPath task edit form, how do you use InfoPath data connection bindings to both retrieve and send data to a SharePoint 2007 workflow?’

So one day I was building an InfoPath 2007 task edit form and I wanted to send data to this form from inside of my workflow by using something like:

taskProperties.ExtendedProperties[“txtProductDescription”] = “Product ABC”;

I implemented an ItemMetadata.xml file with an ‘ows_txtProductDescription’ field, added a secondary data connection for it in my InfoPath form and followed all the normal steps and when I opened the form when my task was created, the data was there as expected.

However, what I didn’t realize was that when I closed the form and completed the task and then re-opened the form just to look at my previous settings, the data was gone! The form appeared as if it were a new form with default settings. To make matters worse, inside of the workflow I discovered that I could not use the task After properties to get the data out of the txtProductDescription field, it was always null. And this is where my multi-day odyssey of searching for the answer began.

To make things simple here, I’m just going to start with a simple form that has no binding and show you how to set things up. I hate to admit it took me several days and talking to several people to figure this out, so I hope it helps you shorten your path to a solution also.

Technologies Used:

* Microsoft Office SharePoint Server 2007 Enterprise Edition, SP1
* InfoPath 2007 – Browser enabled forms
* Visual Studio 2008 SP1 / C#

blogs.msdn.com/...-sharepoint-2007-workflow.aspx - Preview

infopath sharepoint workflow codesnippet

In meinen Projekten bin ich neulich über eine Migration eines Lotus Notes Workflows gestolpert. Normalerweise benutzt man hier aus Gründen der Gestaltung Infopath 2007 Formulare um die Dateneingabe zu validieren.

Jetzt bietet Notes ein sogenanntes selbstlernendes Feld (also eine Combobox die es erlaubt neue eigene Einträge zu erstellen).

Wenn man Infopath als Client verwendet ist das auch sehr einfach, dort ist eine Combobox als Control vorgesehen. Soll das ganze jetzt aber über die Infopath Forms Services laufen wird`s etwas schwieriger, denn die Combobox ist dort nicht verfügbar.

Abhilfe schafft hier ein eigenes kleines Control welches aus 3 Bausteinen besteht:

Einer Textbox für die Eingabe, einem Button für die Steuerung sowie einer Listbox für die Anzeige bestehender Felder. Datenquelle ist hier eine SharePoint Liste. In unserem Fall soll ein Bearbeiter entweder aus der bestehenden Liste ausgewählt werden oder ein neuer Bearbeiter direkt eingegeben werden können - das Ganze ist nicht an irgendein Directory, sondern nur an eine einfache SharePoint Liste gebunden.

blogs.msdn.com/...are-selbstlernende-felder.aspx - Preview

infopath moss fields learning sharepoint forms hack

When you use the "Assign a To-do Item" action in a SharePoint Designer workflow, a form is created that is presented to the user when they edit the task that the action created. This form allows the user to "complete the task" that was assigned during the workflow.

Located on this task form is a link to the related list item. When this related list item is an InfoPath form, a link is provided to the xml form, but unfortunately this link doesn't respect the "open in browser" directive that is selected on the form library advanced settings when the library is configured to forms server. Here's how you can make a change to the XSLT on the form to change the link to open the form using forms server.

sharepointsolutions.blogspot.com/...eate-forms-server-link_29.html - Preview

infopath forms moss sharepoint hack xslt

So here is the scenario, you have an InfoPath template for meeting agendas (one of the samples) and you publish this to a SharePoint site, creating a document library and leveraging the Office Forms Server to deliver a browser-based experience. You can now have the XmlForm Web Part on the home page showing one of these meeting agendas.

www.u2u.info/...Post.aspx - Preview

infopath forms webpart moss sharepoint hosting

Practical step-by-step tutorials, articles, and solutions for InfoPath, InfoPath Forms Services, and related Microsoft technologies.

www.bizsupportonline.net - Preview

infopath article programming moss forms

sharepoint.orcinus-orca.eu/...17 - Preview

infopath programming codesnippet troubleshooting

Learn how to use the XPathNavigator and XPathNodeIterator classes to access and work with data in business logic written with managed code in Microsoft Office InfoPath 2007 form templates.

msdn.microsoft.com/...bb509311(printer).aspx - Preview

infopath xml xpath codesnippet msdn

Using the Contact Selector Control

We have seen a number of requests on how to allow a user to enter (or select) a person’s name or logon alias and then validate that user against their Active Directory without using code. This has been especially true in workflow scenarios where User A needs to enter in the name of User B – the next person in the workflow process.

Well, InfoPath 2007 ships with a control called Contact Selector Control that will resolve these issues! You may have seen our older article on the subject; this one aims to dive in deeper.

blogs.msdn.com/...-contact-selector-control.aspx - Preview

blogarticle infopath activedirectory control

This article identifies best practices for efficiently deploying a Microsoft Office InfoPath 2007 form template to a production environment. It also describes how to optimize browser form scenarios using configuration options. (15 printed pages)

msdn.microsoft.com/...cc704269.aspx - Preview

infopath deployment msdn article bestpractices

Have you ever needed to develop an InfoPath form template that submits back to a SharePoint document library but you did not initially know the server or library name when developing the form? Or have a scenario where your InfoPath form template could be published (or added as a content type) to multiple SharePoint document libraries and you need the submit location to be dynamic? Well read on to find out how you can do this!

blogs.msdn.com/...-to-this-document-library.aspx - Preview

infopath submit trick sharepoint

If you've ever designed and deployed a form that will be frequently used or require significant data analysis, you have probably looked into maintaining data in a SQL database. With InfoPath 2003 and the InfoPath 2007 rich client, you get what you expect. You create a main database data connection to the SQL server and pick tables and columns that meet the requirements for submit functionality. When you open your form and click the "Run Query" button, you see the data pulled from the database as you'd expect. You then happily insert, update, or delete records and, when the time is right, hit "Submit". Luckily for you, the InfoPath client took care of maintaining the list of changes that you made while editing your form. With this list of changes intact, your updated data streaks back to the database to await the next query.

blogs.msdn.com/...n-infopath-forms-services.aspx - Preview

infopath blogarticle webservice submit database .net programming

Infopath Forum

www.infopathdev.com/forums - Preview

infopath community sharepoint forum office2007

Get the User Profile through MOSS Web Services

It is now easier than ever to pre-populate your InfoPath 2007 forms with the user profile information of the current user.

blogs.msdn.com/...through-moss-web-services.aspx - Preview

moss sharepoint user infopath

Submitting to a SharePoint List

As you know, submitting to a Microsoft Windows SharePoint form library from an InfoPath form is quite simple: just add a “submit” type of data connection to InfoPath and away you go. However, submitting to a SharePoint List is another matter. In this post, we will take a look at the steps necessary to enable this functionality.

blogs.msdn.com/...ting-to-a-sharepoint-list.aspx - Preview

sharepoint programming infopath blogarticle

Starting from the Microsoft Office SharePoint Server 2007 user interface, you can choose the content type for which you want to create a custom document information panel. Microsoft Office SharePoint Server 2007 launches Microsoft Office InfoPath 2007, supplies the content type schema as the primary data source, and automatically generates a document information panel form based on that schema. When you finish customizing the form, you can upload it directly to the content type, or to another location.

msdn.microsoft.com/...ms568568.aspx - Preview

infopath sharepoint office contenttypes msdn