About Input Tables

You can use DivePort input tables to store and retrieve row-oriented tabular data from the DivePort portal. Example

• Input tables can be explicitly created as input tables for data entry or they can be created as a result of defining document libraries for the portal.

• Input tables can reside in flat files in the DivePort webdata directory, in a linked directory, or they can reside in an SQL database.
• Portal input tables have a default structure that includes audit data, such as created by and created at and basic components, such as id (for tables) and URL (for document libraries).
• Input tables support the addition of metadata in the form of custom columns or attributes.

• The table definition in DivePort includes column names, data types, constraints on which data can be used as input, definition of lookups, and specification of access control.

NOTE: You cannot rename an input table. As an alternative, delete the input table and then re-create it with a new name.

Rows added to a basic (flat file) input table are saved to the default tables directory, located at: di\solution\webdata\<diveport>\tables. Example.

For each input table, the default directory contains:

• An xml file defining the attributes.

• A txt file containing the data that appears in the columns and rows.

• Backup bak files which are generated automatically.

In addition, a file with the extension highest-seen.xml is created for input tables that use auto-incrementing fields. This allows users to version-control the main xml file, but not the secondary file, because the secondary file is expected to change frequently.

On the DivePort title bar, select ADMIN > Input Tables to view the list of the portal input tables.

In this example, patient-satisfaction, Sales, and States are user-defined input tables. The patient-satisfaction table has 17 rows of data, and the States table has 59 rows.