Qdabra Database Accelerator

Re: Update an Existing SharePoint Form Library

Patrick Halstead — Thu, 24 Sep 2009 19:55:36 GMT

DBXL must be the primary store for your XSN because of the following reasons:

You may not be using SharePoint (many of our customers are using just DBXL)
DBXL adds features that SharePoint doesn't have - like dynamic permissions, conditional mapping to SharePoint, etc. - to use these features you must use a version that is in DBXL.
DBXL extracts data from your form to assist in the SQL database mapping. So it has to have the most up-to-date version of your form

It's easy to just take the XSN that you have published and attach it to DBXL and save. You shouldn't need to create a new form library. If you are experiencing problems, try attaching the form to DAT, saving, and then extracting the form from DAT (right click attachment in General tab and choose Save As). The XSN will be "fixed up" as part of the save operation. You can take this fixed-up XSN and copy it to your SharePoint site (just make sure you don't go through the "republish" steps in the designer as that will "fix-up" the form to point to SharePoint. In other words, you want to upload the form to the SharePoint library without publishing it. You can use the File Explorer to do this.

Re: Update an Existing SharePoint Form Library

ErnestoM — Thu, 24 Sep 2009 12:28:55 GMT

Your current SharePoint form library XSN probably has a submit operation, which submits the form to the SharePoint form library. When using DBXL, the form must submit to the DBXL web service, and the DBXL web service, in turn, maps the new form into SharePoint.

In general, for SharePoint integration, these are the necessary steps:

1. Modify your InfoPath form template such that is submits to the DBXL Document service. Remove any connections that submit to SharePoint directly.
2. Create a new document type in DBXL using this xsn form.
3. Create SQL mapping if desired. Submit a document to test. Edit the SQL mapping if necessary.
4. Create SharePoint mapping. Submit a document to test. Edit the SharePoint mapping if necessary.

You need to let DBXL do this SharePoint mapping so that the PI and href in the solution are correctly referring to the DBXL instance which is the core store for your data (that's because the Web Service is the gatekeeper and must be the official reference for XSN and XML data).

5. Save your existing xml documents and import them into DBXL. I wrote some steps to cover one way to do this. The documents will be auto-mapped to SharePoint and SQL (but if they aren't, a quick Reshred All will do it).

Now, can DBXL work in your scenario? The problem I see is that you are submitting directly to SharePoint, but DBXL needs to be the gatekeeper for these documents. Patrick wrote a blog post that may be related, but it concerns SQL. Read it here.

Update an Existing SharePoint Form Library

emdc2 — Wed, 23 Sep 2009 23:20:26 GMT

Can you (how), set-up DBXL to work against an existing SharePoint Form library? The .xsn has already been published to Sharepoint as a document library and users are already submitting forms to this document library.

To use DBXL, do you have to create the library and publish the .xsn through the DBXL admin tool? How would we get this up and running if we already have our forms published? I tried to add an existing SharePoint list to the DBXL admin tool SharePoint tab mappings and it saved, but the form doesn't work at the location unless you first create the document library through DBXL. Am I missing something here?

Can someone point me in the right direction?

Thanks!