InfoPath Dev

We have approximately 100 forms that will be migrated to InfoPath.  Some will require submission of the data to SQL server but most won't.  My intention is to logically group the xsn files into different libraries where the users will fill them out.  These templates will be primarily open access.  Once they are submitted, again, some will go into SQL and most will be submitted to various form libraries with different security, workflow etc.

 My question is - do I have complete control over where the XSN is stored when using the DBXL Administration tool?  It seems as though when I attach the form to a new entry in the catalog the tool specifies where the XSN is stored ie .../dbxl/qdabrawebservice/forms...

 I hope that made sense :)

Jason

I think I found the answer elsewhere in the forums but if someone can verify for me I would appreciate it.

I can use the DAT to upload the XSN and do any required mapping to SQL and then save the XSN from the DAT and put in in a SP library - as long as I don't go through the InfoPath publishing process.

Is that correct?

Hi Jason,

DBXL v2.3 needs to "own" the xsn. You attach the template to the DBXL Administration Tool and it gets accessed via that path you discovered (shown in the DAT General tab).

You can then add database and SharePoint mappings. However, DBXL still "owns" the xsn. DBXL can publish that XSN to a form library (or two, or three, depending on your license) by using the SharePoint tab. With DBXL v2.3 you cannot take the XSN and put it in a Sharepoint library (or publish it) manually; again, DBXL needs to control that.

If you have <x> number of form templates that do not need database mapping, then just publish them to SharePoint and you're done (I don't think DBXL needs to be involved in those scenarios). For the templates that need SQL (database) mapping, add those to DBXL and then add the necessary SharePoint mapping.

DBXL v2.3 has a free trial, so you could try all this out without having to purchase anything, to see if it fits your requirements.

Does this address your question? Let me know if you have any other questions.

Thank you.

Thank you for the quick response.  I believe you have answered my question.

 If I'm reading you correctly once DBXL owns the xsn, I can use the tool in order to push that xsn to a form library.

The goal is to have libraries containing the actual XSN files so users can see them, open them, fill them out and submit them somewhere else.

Ok - I just tested it in our evaluation version and I am not seeing the result I had hoped for.

 Is it possible to push the XSN to a form library so the XSN itself is an item in the library?  So users can open the template by clicking on the item and not using the New menu?

 Does that make sense?

I think this is a moot point actually because if I simply upload the xsn to a form library I don't think I'll be able to get it to open in a browser.

Hi Jason,

DBXL (DAT) creates a form library for the XSN, yes, it doesn't add multiple XSNs to the same library.

As far as "users can see them, open them, fill them out and submit them somewhere else", the form submits the XML to DBXL (which in turn can then map it into the database or the form library). So throughout the process DBXL is involved.

Hope this info helps!