SQL Export Specification Line Item  (kourier_export_sql_item.aspx)


Purpose

To define the fields to be included in the SQL data export file, the SQL column headings to use, and any data conversions or formulas required.

Available Toolbar Commands

Click the Done icon in the toolbar to save the current line item and return to the export specifications main page.
Click the Add icon in the toolbar to save the current line item, clear all fields and keep the window open so that you can add another line item, which will be the last line number available.
Click the Remove icon in the toolbar to delete the current line item, close the window and return to the export specifications page.
Click the Up icon in the toolbar to move the line item up in the line item list relative to the other line items, thereby decreasing the current line item number. Click Done or Add to save your change.
Click the Down icon in the toolbar to move the line item down in line item list relative to the other line items, thereby increasing the current line item number. Click Done or Add to save your change.
Click the Help balloon to open the help for this page.

Important: to save any changes you make after creating or editing Export Line Items you must save your changes using either the New, Save, or Save As toolbar commands

File/Key Field

KT_EXPORTS/Export Name

Prerequisites

If an export contains user-defined literals, they should be entered using Substitution Literals.

Cautions

None

Line Item Fields

Field Name Description - Usage - Notes
Line The order sequence this field should appear in the export.
Field ID You can specify D-, I- and V-type dictionary items. In addition, it is possible to reference a field simply by entering its attribute number. This feature is quite useful when exporting items from a temporary file.
SQL Column Enter the SQL column heading for this exported field. This field is used when building SSIS Packages in order to update the SQL table. If the DDL button is used, the column heading will be used for the SQL table column names.
Conversion Enter any valid dictionary conversion code, substitution parameter, or a literal string.  This code will override the conversion code in the dictionary item. Multiple conversion may be separated by the | (pipe) character.
Formula Enter a user-defined formula for this field using standard UniBasic syntax and commands. The results of the formula will determine the find output value for this field.  A formula icon will be displayed in the list view if there is a formula defined for a field. Hover your mouse over the icon to see the note.
Format This field is only used when an export is generated in FIXED format.  It is used to over-ride the length of the output and the justification of the output.
Key Code Use this to indicate if the field is:  A) Primary Key, B) Primary Key & Change Key, or C) None of the above. This is used to determine how the column is used when processing SQL updates and deletes.  If the DDL command is used, this field indicates the primary keys to create in the DDL that is created from the export.
Source ID Check this field if the column is used as the Source ID for the table. Using a Source ID column allows you to store data from multiple companies, locations, sites, etc. in the SQL table and retain the original source of the data. Only one column per SQL Export can be indentified as the Source ID.  Note: the data value used as the Source ID may not contain the underscore character because the SSIS package determines the Source ID from the file name that it being processing and everything to the left of the first underscore character in the file name is considered the Source ID.
Comments Enter any comments you wish to describe or document this export field. A note icon will be displayed in the list view if there is a formula defined for a field. Hover your mouse over the icon to see the note.
Indexed Check this field if you want this column to have an index created for it when you use the DDL command to create the SQL table.
Case Sensitive Check this field if you want this column to be treated as a case sensitive field within SQL Server.

User Guide - Table of Contents