Yesterday while attempting to publish an InfoPath form to a SharePoint site, I received the error “The following Url is not valid…”. My site Url was:

http://server:103/sites/poc

To resolve the issue, create a Blank Team site collection in your web application which is not under “sites”. You need a site at the root of the Url. Problem solved.

To add the Contact Selector control to the Designer Controls pane in InfoPath 2007:

1. In Office InfoPath 2007, on the Design Tasks pane, click Controls.
2. On the Controls pane, click Add or Remove Custom Controls.
3. In the Add or Remove Custom Controls dialog box, click Add.
4. The Add Custom Control Wizard appears.
5. Under Select a Control Type, select ActiveX Control. Click Next.
6. In the list of ActiveX controls, select Contact Selector. Click Next.
7. Under Specify Installation Options, select Don’t include in a .cab file. Click Next.
8. Under Binding property, select value. Click Next.
9. For Field or group type, select Field or group (any data type). Click Finish. Click Close. Click OK.

Link

How to: Configure a Contact Selector Control on Your InfoPath Workflow Form

Today I was reviewing some of the workflow examples in the new MOSS SDK (released at the end of February). One of the examples is using an InfoPath form for workflow. When I attempted to open the form, by double-clicking it in Windows Explorer, I received the following error:

The form cannot be opened because it requires the domain permission level and it currently has restricted permission. Contact the form author the resolve the issue.

Forms that require the domain permission level contain features that access information on a network, such as data connections, linked images, and code.

This morning I was creating an InfoPath 2007 form and wanted to add an OnChanged event handler for a dropdownlist control. Bear in mind this is my first foray into InfoPath programming - never had a need previously. I right-clicked the dropdownlist control and selected Programming - Changed Event. Visual Studio Tools for Applications fired up but the project was VB.NET. No offense to VB but I would rather program in C#. Need to find a way to remove the current VB project and create a C# one instead.

Read the rest of this entry »