Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Define export process parameters

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 4 minute read

Before you begin

Complete the steps in:

The ImportExportConfig Row Edit dialog box is opened through the Import Export Config table listing in the Advanced Database Editor (ADE). For general information on ADE, refer to the Advanced Database Editor (ADE) Administrator documentation.

To define export process parameters

  1. Navigate to the ImportExportConfig Row Edit dialog box.

  2. Refer to the table below for instructions on configuring Export process parameters.

    Item

    Instruction

    Customer Name

    Enter the Customer Name exactly as it appears in the Customer Name field in the associated dataexchange record.

    Dataset

    Select (...) and select the name of the dataset you want to associate with this record from the Dataset Select dialog box.

    A dataset contains privileges assigned for each system and mode. Once a record is assigned to a data set value, the dataset can only be changed to a value for which the system has a privilege record. A record’s dataset can not be changed in such a way that the system can no longer access the record.

    Operation

    Select Export.

    Folder

    Enter the path to the folder where you want to place the exported files.

    File

    Enter the name of the file to export.

    Note: The name can contain date codes (refer to Date format). For example, "OutputFile1DDhh".

    Frequency

    Enter the frequency (in seconds) at which the application should generate and export the file.

    Note: To be effective, this time must be greater than or equal to the value in the Process Timer Interval field on the ImportExportGen Row Edit dialog box (refer to Define basic application settings). In addition, the time should be greater than the expected amount of time required for the application to perform the operation.

    Format

    Do one of the following:

    • If you want to apply the same formatting to all records in an exported file: enter a format string specifying the format of the records in the file generated for export (refer to File content format string definition).

    • If the format of a record differs based on the tag: enter DATABASE, which instructs the application to use the format string stored in the Dataexchange table for each tag exported for this customer.

    Where clause

    To limit the number of tags in the export file, enter a valid Microsoft SQL statement WHERE clause.

    • If User Xref = yes, the application applies the WHERE clause to the set of data before limiting the output using the Dataexchange table.

    Copy To

    Enter the path to the folder where you want to copy the file (for archive purposes) after the application creates it.

    First Rec Date

    Enter the format of the date string that the application includes as the first record of the exported file. Refer to Date format.

    Normal

    Enter the string to export as Tag Status if the tag status is NORMAL (for example, "GOOD", "VALID", etc.).

    Stale

    Enter the string to export as Tag Status if the tag status is STALE (for example, "BAD", "INVALID", etc.).

    Use Current Date

    This is only applicable for records exported out of the RealTime database (RTDB).

    Select one of the following:

    • yes – The application will write the current computer time in the export file for the record.

    • no – The application will write the time at which the record's value was last updated in the RTDB in the export file for the record.

    Note: This only applies to the timestamp exported from the RTDB. When Export Exceptions is yes, the exported file will contain entries from Historical database, and the timestamp will be the timestamp when the data is collected.

    Use Xref

    Select one of the following:

    • yes – before creating the export file, the application will cross-reference the tags for export with the customer's tags in the dataexchange table (refer to Cross-reference tag names).

    • no – the application uses the AVEVA Enterprise SCADA tag names.

    Export Exceptions

    Select one of the following:

    • yes – Export all values if the value, state, or status of applicable tags change since the last export.

      • If a point value, state, or status changed N times since the last export, there will be N entries in the export file.

        Note: The first export file generated after the ImportExportConfig record is created will include all the changes found in the collect table for each point. If you want to prevent this, you can create the record with Export Exceptions = no, wait for one export file to be generated, and then update Export Exceptions to yes.

      • If a point's last krunch time is newer than the last export time, but the value, state, and status are actually unchanged, the current value will still be exported. There will be only one entry in the export file.

      • If a point's last krunch time is older than the last export time (such as a stale point or manual point), it will not be exported at all.

    • no – Export current values only.

    Export SA

    Enter a comma-separated list of areas containing the groups whose records you want to export. The application appends the areas to the Where clause.

    Export RT

    Select one of the following:

    • yes – the application ignores the Dataexchange table and instead exports the entire RTDB (analog, rate, and status tables). Use the Where clause and Export SA settings to limit the result set. The application uses the names of analog, status, and rate points in the export. For flowTotalConfig points, it uses name.n, where "n" = the array index.

    • no – the application makes use of the dataexchange table.