AX2430
Importing from an internal Axiom database
You can import data from the current Axiom database. This feature can be used to automate the process of copying data from one table to another, or to transform the data within a table.
NOTE: Only administrators can create or edit an import that uses the current Axiom database as the source. Non-administrators do not see this option when creating or editing an import, and cannot open any existing imports that are configured to use this option. However, non-administrators can be given the right to execute an import that uses the Axiom database.
Source configuration
To import data from the Axiom database, complete the following configuration settings on the Source tab of the Import Wizard.
| Item | Description |
|---|---|
| Import type |
Select Internal Database to import data from the Axiom database. |
|
Import source |
Select one of the following database sources:
NOTE: Systems with an Axiom Contract Management license can also import data from the Current Contract Management database. See the separate product documentation for more information on importing contract management data. |
|
Source Staging Table |
Specifies the staging table to be used for the import. For more information, see Using product staging tables. |
When you use this option, Axiom automatically creates the necessary connection string in the background when the import is performed. If the import is copied to another system or if the current database is restored to a different location, the new context is used to create the connection string.
SQL Select Statement
The SQL SELECT statement defines the data query to the source database, resulting in the set of data to be imported to the temp table. You can then perform mapping and transformations on the data before importing into the destination table.
In the SQL Select Statement box, enter any valid SQL statement to define the data query. You can click the SQL editor button 
to open the Edit SQL dialog. This dialog provides a text editor for entering and reviewing large SQL statements, and several tools to check the statement. For more information, see Creating the SQL SELECT statement.
Variables can be used in the SELECT statement. See Using variables in imports.
The SQL Select statement does not apply when using a product staging table.
Axiom products sometimes use an import strategy where the client has a custom import utility that imports data to a staging table, and then the product provides a standard import utility to import the data from the staging table to a target table. The Product Staging Table import type is intended to be used for the standard import utility provided by the product. It imports data from the specified Source Staging Table to the destination table (as configured on the Mapping tab).
Although the Current Axiom system database import type could also be used for this purpose, the Product Staging Table import type provides special behavior that allows the import to dynamically adjust for any custom columns that the client may have added to the destination table. In order for this behavior to work, the client must add matching columns to both the staging table and the destination table. For example, if you as the client want to add a string column named Status to the destination table, then you must also add a string column named Status to the staging table.
When the import is executed, Axiom examines the staging table and the destination table, and dynamically adds mapped field definitions for any locally defined columns (meaning not product-delivered columns) that meet the following criteria:
- The columns have the same name and the same effective data type in both tables.
- The columns are not already present in the field mappings.
To support this behavior, the temp table uses column name mapping to line up the source and destination columns, rather than column order.
