Browse by Tags
-
qForm is a sample form that comes with Qdabra’s Database Accelerator (DBXL) v2.4. The form has a built in taskpane that allows assignment and workflow, as well as taxonomy (tags). This document serves as a guide for anyone wishing to use qForm to develop their InfoPath solutions. Click DOWNLOAD above...
-
DBXL's taxonomy allows users to tag documents with categories. An administrator can manage these categories and tags from DAT. To learn more, click DOWNLOAD above to obtain this document. A free trial of DBXL v2.4 is available on Qdabra.com .
-
If you encounter errors in the xref tables in DBXL, this document will explain how to identify and address these. Click DOWNLOAD above to obtain this document. To obtain a trial version of DBXL v2.4, please visit Qdabra.com .
-
The DBXLResource API allows users to use custom XML in their DBXL Document Type Configurations. As explained in the scenarios below, this grants the user to customization flexibility. The scenarios explain situations in which the administrator sets and controls the XML and situations in which the users...
-
If the Enable History checkbox is selected for a particular Document Type, all of the previous versions for a document are saved to the database for historical review and can be retrieved. You can add workflow to your form by following the steps in the attached document, which you can obtain by clicking...
-
Hi, I have worked through the "How to create a button that saves to DBXL but does not close the form" post at http://www.infopathdev.com/files/folders/miscellaneous/entry49724.aspx . I don't want to have a button for this save (it will confuse the users.) I am calling the code from an on...
-
Hi I am having problems trying to connect to the DBXL Document Service from SharePoint. DBXL and SharePoint are running on the same server. I have been following the "Create a SharePoint data view that uses GetListItems to access DBXL forms" In the instructions it doesn't mention having...
-
When I submit the form, the following things happen as expected: It appears in the document tab in DAT. It appears in the SharePoint forms library The following things happening are un-expected It creates a record in the SQL server where only the doc id is getting correctly updated to the mapped field...
-
This helps me understand why the guide didn't work for me. I published the form to Sharepoint from Infopath. In order to make certain the form was routed to the correct document type in DAT I had to add a field to my main data source and give it a default value which matched the document type name...
-
Thanks Ernesto. The Expense Report example works fine. And my browser based form works fine when submitted through DAT. Just can't seem to get the form data into the SQL Server database when submitted from the Form Library in Sharepoint. What am I missing?