DriveWorks has the ability to export data to an external database (using a Microsoft Windows ODBC connection) as part of running a DriveWorks Project.
Each ODBC Data Export in the Document List can export data to a single table in a single database. By creating multiple ODBC Data Exports, it is possible to export data to any number of tables in any number of databases.
Each ODBC Data Export consists of one or more rows to be exported into the table in the target database.
Each row in the data export will be added to the table, or update an existing row in the table, or be ignored. The behavior for each row is controlled by Control Fields.
Before attempting to export data to any database familiarize yourself with the database the data will be exported to. Pay particular attention to the data types associated to each column in the data table.
Data types designate the type of data that will be stored within the field. This can take several different forms which includes (but is not limited to) text strings, numbers and dates.
It is important to note the data type of each column in the table you are exporting to.
The result of the rule, for each field of the data export, will need to match the data type the database is expecting.
When the Data Type is Float a numeric value must be the result of that column in the Data Export Document.
When the Data Type is Text a textual value must be the result of that column in the Data Export Document.
In DriveWorks Administrator open the Project the Document is to be add to and go to Stage4: Output Rules then Documents - Data
See To Edit an ODBC Data Export section below.
Control Fields control whether a row is inserted, updated, or ignored:
Common Fields can make it easier to export data to certain types of systems, for example PDM and ERP databases where often multiple rows will need to be exported, but certain columns always have the same value in each row. For example an IsSubmitted column might always contain the value 0.
For these columns, you may only want to build one rule, instead of a separate rule for each row. To do this, mark the column as a Common Field, and DriveWorks will automatically use the same rule for the column in all rows.
By using Specification Flow it is possible to gain even more control over when Documents are created.
The Wizard can be reopened at any time by selecting the Open Wizard button.
Each user that uses DriveWorks will need access to the database. This means that either a system DSN needs to be setup by an administrator on the machine they are using, or a user DSN needs to be setup by the user or an administrator on the user's account.
For more information about DSNs see the Info: Working With DSNs.
The options for the ODBC Export can have rules applied once the initial connection has been set up.
For example you will not want specifications made for testing purposes populating a production database.
Rules can be applied that connect to a testing database when using the Development environment, and then connect to the production database when using the Production environment.
From the Documents - Data task:
The rules for the export are edited by returning to Stage 4: Output Rules then Documents - Data.
|NewCustomerReturn||Will export the value of the control NewCustomer to the database.|
The ODBC Data Export Document is triggered in the Specification Flow by the Release Documents task.