SharePoint - Using Managed Paths and InfoPath Data Connections to a SharePoint

Asked By RichardHarbridg

03-Dec-08 08:57 AM

I have encountered an error in the way that InfoPath interprets data
connections to SharePoint when using managed paths.

If you use Managed Paths to make a path like this (explicit):
the InfoPath browser form accesses the data connection to a list in this site
collection (department) it tries to access it from the root site collection
of 'portal' which causes an error.

This results in the following WARNING message in the event viewer of the
SharePoint server.

The following query failed: Vertical Sectors (User: AD\Username, Form Name:
Account Profiles Form Library, IP: , Request:
http://portal/_layouts/FormServer.aspx?XsnLocation=http://portal/department/FormLibrary/Forms/template.xsn&SaveLocation=http://portal/department/FormLibrary&Source=http://portal/department/FormLibrary/Forms/AllItems.aspx&DefaultItemOpen=1,
Form ID:
urn:schemas-microsoft-com:office:infopath:FormLibrary:-myXSD-2008-11-18T16-38-05,
Type: DataAdapterException, Exception Message: The form cannot run the
specified query.
List does not exist

The page you selected contains a list that does not exist.  It may have been
deleted by another user.)

I will see if I can determine a workaround, but this definitely seems like
something that should be brought to the InfoPath or SharePoint groups if my
assumptions are correct.

03-Dec-08 10:09 AM

I was able to do a 'workaround' using XML and the owssvr.dll however this is
an extremely limited workaround comparatively speaking.

This is a potentially large issue and I really want to push for it's
resolution, so I am going to illustrate the steps needed to reproduce this
issue in InfoPath/SharePoint:

1. Create a SharePoint Managed Path that directly follows the root with
explicit inclusion. Name this a department name as an example (HR, Sales,
etc).

2. Create a site collection in that new path.

3. Enable all the features (enterprise etc).

4. Create a simple form in InfoPath (no need for fields). Add a data
connection to lookup the values of any SharePoint list in the new department
site collection.

Ensure this data connection is set to grab the data on form load (or you can
use the refresh button, whatever works for you.)

5. Publish the form to an infopath form library in SharePoint.

6. Open the form.

At this point you should notice a typical 5566 error message and the event
log on the Server will display an event like what I listed above.

At this point my assumption is that for whatever reason the infopath
SharePoint data connection has been designed without considering managed
paths and their impact. Remember the connection is under the same domain, so
it shouldn't be a cross domain issue which removes that complication. The
fact that the xml method worked fine also proves that the list exists, and
it's not a access/security issue.

This leaves only my previous assumption thus far.

Anyone's help, ideas, or advice would be greatly appreciated,
Richard