Difference: 0DXSubrXmlImport (3 vs. 4)

Revision 42014-07-28 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="Main.530DataExchange"

.XML IMPORT

Line: 6 to 6

.XML IMPORT

Usage:

Changed:

<
<

      PASS         <key>                      FIELD            SHARE? Y

>
>

      SET      0DX .XML IMPORT                =
      PASS         <key>                      FIELD            SHARE? Y

PASS <XML_file> FIELD SHARE? N PASS <XML_Map> FIELD SHARE? N PASS <Import_Flag> FIELD SHARE? N

Line: 29 to 31

After the API is complete, your extracted data will be available in the 0DX XVALUE file. This is true, regardless of whether the API imported the data or not. The XVALUE file is keyed on the <key> that is returned from the API. Remember that there can be more than one imported file in XVALUE, you should use <key> in a BEG AT/END AT to only read the data records for this import.

XVALUE is a temporary file and the contents will be lost when the session ends.

Added:

>
>

NOTE: This subroutine must be invoked DETACHED, and cannot be invoked via GOSUB. The 0DX .XML IMPORT field must be intialized in your process before invoking the API, or you will not get a return value.

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r11 < r10 < r9 < r8 | More topic actions...