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.