Other Options

Publish Grids and Database Views as a Single Dataset

When publishing Grids or Database Views to AVEVA Integration Service, you can control whether the published output is grouped as a single dataset or published as separate datasets. This is configured using the Single dataset option in the export configuration.

Note: The Single dataset option is available in the Other options group within the General settings of the export configuration, and is only shown when Integration Service is selected as the output type.

Single dataset - checked (default for new configurations): All selected Grids and Database Views are published to AVEVA Integration Service as tables within a single dataset, sharing one acknowledgement ID (ACK ID). A single dataset containing one or more tables is published.

Single dataset - unchecked (default for configurations upgraded from a previous version): Each selected Grid or Database View is published to AVEVA Integration Service as a separate dataset, each containing a single table with its own acknowledgement ID (ACK ID). One or more datasets, each containing one table, are published.

Note: When an existing configuration is upgraded from a previous version, the Single dataset option is set to unchecked by default to preserve the previous publishing behaviour. New configurations have this option checked by default.

When to use Single Dataset

Check Single dataset when you want AVEVA Integration Service clients to receive a single notification for the complete published data set, regardless of how many Grids or Database Views are included. This is useful when the consuming application or workflow should process all published tables together as a unit.

Uncheck Single dataset when each Grid or Database View should trigger an independent notification in AVEVA Integration Service, allowing consuming applications to process each table individually as it arrives.

To configure the Single dataset option:

1. In the General tab, Select the Integration Service option from the Output area.

   

2. Expand Other options to see additional options.

3. Select or clear the Single dataset check box as required.

4. Click Save.

Setting Expiry Duration

The Expiry duration setting controls the data retention period (in hours) for data published to AVEVA Integration Service. This determines how long the published data remains available for clients to retrieve before it expires.

Constraints:

• Default value: 0

• Minimum value: 0

• Maximum value: 744 (equivalent to 31 days)

  Note: The Expiry duration setting defaults to 0 for both new configurations and configurations upgraded from a previous version.

To configure the expiry duration for Integration Service output:

5. In the General tab, Select the Integration Service option from the Output area.

6. Expand Other options to see additional options.

7. Set the Expiry duration[h] value in hours. Enter 0 to use the server-controlled retention period, or enter a value between 1 and 744 to specify a retention period.

8. Click Save.