InfoPath Dev

Hi there,

I am following the learning modules fairly closely as I work through my form development.  I have a form that is working in DBXL and shredding properly into my database.  Now I am workign through shredding into Sharepoint as well.  My DBXL install is on the same server as my Sharepoint install.  When I follow page 1 of the DBXL Training Module 3, I am unable to see my forms showing up in my Sharepoint list. 

I add the sharepoint list as per the instructions on page 1 of the 3rd Module,  by typing in a URL to a non-existant list: (e.g. http://myintranet/IT/myTestFormList).  (I can then go to that URL in sharepoint and see the list, click on Add Document and fill out the form etc. so it seems to create it).  When I fill out the form as I add a document, I can go to DBXL and see the entry there, as well as opening up SSMS and query my DB and see all of the relevant records there, so it is submitting to DBXL fine.  I suspect it is not shredding to Sharepoint.

 When I setup the list in DBXL I notice that the following happens:

1. I type in my URL
2. When I hit Save, I get a prompt saying "Changes Saved".
3. If I select the first two checkboxes as per the instructions, I get a prompt saying: "An unhandled exception occured while calling the SetDocumentType method.   S00002: Caught exception ensuring the Sharepoint form library <url to form library>.  The request failed with the error message:
   --
   <html><head><title>Object moved</title></head><body>
   <h2>Object moved to <a href="<baseURL>/_layouts/1033/error.aspx......

<body></html>

And then the URL dissapears, if I don't check the first two boxes, it seems to work.  Curious what this message means and if anyone knows what this is?

Thx,

Robin

Hi Robin,

The first thing to check is whether DBXL is installed on the SharePoint - 80 site. If it is, then let's check whether the DBXL app pool and the SharePoint - 80 app pool are using the same identity.

If everything looks ok for the above, then I would suggest sending us your form so we may try it on one of our servers. Let us know whether you're using ShP 2010 or MOSS 2007 and we'll try it out to see if we run into an issue.

Thanks.

They are on the same Server, but not the same identity.  Both are AD domain accounts.  Would applying the security groups Sharepoint is in to DBXL work to resolve the error?  If not what would the impact be on changing the DBXL identity? 

Thx,

R.

Also I was able to successfully publish my form to a Sharepoint list via Infopath publish option (e.g. circumventing DBXL).  After doing this I go into DBXL and I am able to setup the Sharepoint integration (by entering the URL into the Sharepoint tab in DBXL for my Form, do not check any of the option checkboxes for the mapping).  Then if I reshred my existing documents (or submit a new one), it seems to show up into the DB and Sharepoint correctly.  I am wondering if this approach, although a bit more cumbersome, still valid?  Also, I can't seem to get the "Name" column in SP be the Form name as is configured in DBXL, it seems to override it and be the Form ID (e.g. 1431) in DBXL.  Is there a way to change this so my "Name" which has the editable link to the form is the name I have configured via my Submit to DBXL option?

Robsil - I had the same issue with form name while learning to use DBXL.  My answer was here

http://www.infopathdev.com/forums/p/25489/88473.aspx#88473

RobSil1976:

If not what would the impact be on changing the DBXL identity? 

Hi Robin,

There's no negative impact on SharePoint, and changing the DBXL identity has the advantage of allowing you to create the SharePoint mapping.

About the workaround you found, I would need to test it more thoroughly to tell you whether it's valid going forward.

For the name column in SharePoint, make sure you define the DBXL::Name token in the DBXL Submit data connection. This becomes the Name column in SharePoint when a SharePoint mapping is added.

Hope this helps!