InfoPath Dev

I have InfoPath 2010, Sharepoint 2007 and DBXL 2.3.

I have a form which has been in use for >1 year.  There is a SharePoint mapping allowing data to be promoted to a Form Library.  The users do not edit the documents in the form library, they are purely used to trigger alerts.  I have added new fields to the form in the last few months, I have promoted those fields in the form and when looking at the SharePoint tab in DBXL those fields are shown.

When I go to the SharePoint Form Library only 2 of the 3 fields are present.  I have checked the settings on the form - and it is not that the 'missing' field is not showing on the view - it isn't in the Library columns.

On the SharePoint tab in DBXL I have the URL filled in, and the Method selected as WebService.  SSO is set to none, SSO Appl.Name is blank and none of the "Insert Expression" tick boxes are filled in.  When I save I do not get any errors.

I have tried ticking the Publish Library and XSN tick box and saving and I get an error S0002:Caught exception ensuring SharePoint form Library. .... Remote server returned an error (409) Conflict.

Can any one shed any light as to why one of the promoted fields is not getting to the form library - and what I can do to fix the issue.

Thank you.

Catharine

Hi Catharine,

Are there any errors in the Qdabra or Application logs? I imagine there is a possibility that DBXL is failing to map using Web Service. With Object Model (and Publish Library and XSN checked) we have another way of mapping the form from DBXL to SharePoint. However, sounds like this may be failing in your environment. (409) Conflict is not an error I am familiar with but perhaps the event viewer has additional details, or perhaps switching to Object Model solves the issue.

One final resort might be to:

1. Modify your submit data connection such that the doctypename is hardcoded (pgs 1-2 in this document)

2. Publish the form from InfoPath directly to the SharePoint form library.

3. Then attach the template.xsn (which is in SharePoint) to DAT. That is, instead of attaching a local copy of the XSN, attach the copy that is stored in the SharePoint form library, i.e. http://<servername>/<YourFormLibrary>/template.xsn

This way DBXL is forced to use the form template stored in SharePoint, and we force SharePoint to have the latest via the InfoPath publishing wizard. Make sense? Again, this is an option I would suggest trying if the SharePoint mapping woes cannot be resolved.

DBXL v2.3 was the first version of DBXL with SharePoint mapping, and improvements have been made since then, so perhaps another option is to upgrade.

Let us know if you need additional information. Thank you.

Hi Ernesto,

I cannot see any errors in the Qdabra logs, I don't have access to the application logs so I can't confirm any errors/not in that one.

I think I need to do the upgrade, and then see if the issue remains.

I have the Upgrade from DBXL v2.3 to 2.4 document.  Can I jump from v2.3 to 2.6 ?  Or do I need to do each jump ?

I could not find an Installing 2.6 document.

I have 5 document types to deal with - approx 3,500 documents.

We do have a full licence, and we have some consultancy time in credit, would it be possible to set up a meeting to check we have all the correct things in place + a hand to hold while I do the upgrade ?

Catharine

Hi Catharine,

Yes, you can upgrade from v2.3 to v2.6; the process is the same as for v2.3 to v2.4. Notice that this process will require some downtime.

Here is the v2.6 installation guide.

You do have a credit with us, so please let us know via support at qdabra dot com the best day/time to schedule this support. Thanks!

Hi Catharine,

I have sent email but have not heard back. Let me know if you're still interested in upgrading and we can help.

Thanks!