|
|
|
|
Name
|
Enter a unique name for the export. By convention, exports are named using an Integration ID such as KS for KommerceServer, followed by an underscore and a string that describes its purpose (e.g., KS_CONTACTS).
|
|
Title
|
Enter a short descriptive name for this export. This name is displayed in on-line lookups.
|
|
Export Format
|
Enter the export format. If the export verb is KEXPORT, the possible choices are shown below. Other export verbs (normally user-written BASIC programs) may or may not support these formats.
|
|
|
|
TAB
|
Data values are delimited by the tab character. Use this format to generate files that can be automatically loaded in the Excel or other PC applications.
|
|
FIXED
|
Data values are of a fixed length. Each column in the export will be padded with blank characters to the length of the column.
|
|
XML
|
Data values are enclosed in XML tags.
|
|
JSON
|
Data values are returned in JSON format.
|
|
HTML
|
Data values are enclosed in standard HTML tags.
|
|
ASCII
|
Data is exported in flat file format where each attribute appears on a separate line. Value marks and sub-value marks are embedded in each line. This format is similar to wIntegrate's ASCII format.
|
|
CSV
|
Data values are delimited by the comma character. If a data value is non-numeric it is enclosed by the double quote character. If a data value contains the double quote character it will be duplicated.
|
|
PIPE
|
Data values are delimited by the pipe character. This format is often used when interfacing with Oracle systems.
|
|
TILDE
|
Data values are delimited by the tilde character.
|
|
|
Enable Net Change
|
When net change is enabled any add, change, or delete of a record in the file referenced in the Export Data File field will be tracked. Kourier tracks these changes by creating an RDBMS index named KCL_INDEX. A subfile is created under the KT_CHGLOG file using the same name as the file referenced in the Export Data File field with the string _LOG appended to that file name.
Only files that are defined locally to the current account may have Net Change enabled.
You may also enable Net Change with Checksum, which provides an additional level of filtering when records are exported. This feature is useful if your application writes records to the file referenced but those changes may not be of interest to the target application.
|
|
Last Update
|
Display only field, shows the last date/time that the export specification was saved.
|
|
Note
|
Enter a free form comment or note for this Export Specification. If a note is entered, a small icon will display on the Export Specification listing. Hovering your mouse over the icon will display about 40 characters of the note.
|
|
Select Verb
|
Enter a valid verb to perform the selection, such as select or sselect.
For UniData systems, ECLTYPE “P” and ECLTYPE “U” syntax is supported. For ECLTYPE “P”, use the upper case version of the select verb. For ECLTYPE “U”, use the lower case version of the select verb.
The export processor first processes the selection portion of the screen, and then passes the selected items to the export section. The selection portion of the screen can be used to limit the number of records exported.
|
|
Select Data File
|
Enter the name of the U2 data file to use to select data records for exporting.
|
|
Using File
|
Enter the name of the file that contains the dictionary items referenced in the select statement.
To use the dictionary file with the same name as the data file, leave this field empty. For example, if you enter CUSTOMER as the data file and do not enter a using file, the CUSTOMER dictionary file is used.
To specify an alternate dictionary file, enter DICT and the file name.
To specify a data file that contains dictionary items you want to use, enter the file name.
|
|
Select Statement
|
Enter the selection criteria statement using standard U2 query syntax.
For example, if you want to select all of the CUSTOMER records with PHONE 619], enter WITH PHONE 619] in the Statement field. This field may also contain substitution tags.
If your select statement uses a dynamic substitution tag that will be specified in the Command field in a Service by including the HEADERS keyword, you must specify a default value for the substitution tag so that the Test capability works correctly. For example, if your HEADERS expression was HEADERS "StartDate=01-01-15" then your substitution expression in the export should be {%StartDate(S;*;'01-01-14'}.
|
|
Export Verb
|
Enter the name of the export verb. In most cases this will be the Kourier program called KEXPORT, although it is possible to write a BASIC program to generate the dataset to be exported.
|
|
Export Data Files
|
Enter the name of the data file to use to export data records. To enter a list of related export files click the drop-down icon. 
Note, if more than one file is entered, the field will be disabled (grayed out) and only the primary file name will be displayed, followed by the total number of files in brackets. For example. If the primary file is GL, and there are two additional related GL files, the field will be disabled and display as "GL [3]". Use the drop-down icon to edit the list of files. Refer to the Related Data Files Guide for more information on using this feature.
|
|
Using File
|
Enter the name of the file that contains the dictionary items referenced in the export statement.
To use the dictionary file with the same name as the export data file, leave this field empty. For example, if you enter CUSTOMER as the data file and do not enter a using file, the CUSTOMER dictionary file is used.
To specify an alternate dictionary file, enter DICT and the file name.
To specify a data file that contains dictionary items you want to use, enter the file name.
|
|
Export Verb Requires Select List
|
If enabled, then an active select list (or an empty selection criteria) must be present before the export statement will be executed. If disabled, the export statement should be processes even if an active select list is not present.
|
|
Export Options
|
Enter any valid export options.
|
|
|
|
COL.HDR.SUPP
|
Use this option to suppress columnar headings. Syntax is: COL.HDR.SUPP
|
|
EXPORT-REPEAT-VALUES
|
If this option is specified, Kourier will repeat the last non-null value or sub-value of a field. Syntax is: EXPORT-REPEAT-VALUES
|
|
EXPORT-SUBNAME
|
Used by the KEXPORT command to specify the name of the export subroutine associated to the export. Syntax is: EXPORT-SUBNAME "subroutinename".
|
|
XML-FORM-TAG
|
When creating an XML export, this option indicates the form tag of the XML document. Syntax is: XML-FORM-TAG "elementname". This option supports System function and User-defined Using Substitution Tags.
Example: XML-FORM-TAG \form id="OrderID={@ID}"\
|
|
XML-ROOT-TAG
|
When creating an XML export, this option indicates the root element tag of the XML document. Syntax is: XML-ROOT-TAG "elementname". Default value is: Kourier file=export_data_file. This option supports System function and User-defined Using Substitution Tags.
Example: XML-ROOT-TAG \application id="Salesforce"\
|
|
XML-TRANS-TAG
|
When creating an XML export, this option indicates the transaction tag of the XML document. Syntax is: XML-TRANS-TAG "elementname". Default value is: Trans id=@ID. This option supports System function and User-defined Using Substitution Tags.
Example: XML-TRANS-TAG \mytag id="{@ID}"\
|
|
|
Event Handler
|
Select the Event Handler for which you want to view/edit and click the edit icon  .Events that contain code will be displayed in angle brackets (e.g., <Before Read>).
Available Event Handlers are:
Each Event Handler has a specific timing and usage during an import, which is explained in the Export Specification Event Handlers topic
|
