To import or export collections in E3, users must select the corresponding option in a template. There is no way to exclude only some collections, either all of them are imported or exported, or none at all.

Columns in each collection depend on the properties of that collection. This is handled the same way as object's property columns.

In case of collections and collection items, properties must be included in an INI file manually. It is not possible to select these properties via template settings.

Collections can be imported, and their properties can be updated. Since collections always exist, and there is no way to create another collection of the same type, users are asked whether they want to ignore or overwrite the existing collection.

If the collection item being imported already exists, users are asked whether they want to ignore it, overwrite it, or create a new one. In case users select the later option:

•In case of Pens and Axes, their names are properly auto-incremented

•In case of Table Link rows, they are created at the end of a table

•In case of Legend columns, an error message is displayed informing that either their names are not valid, or that column already exists and its name cannot be auto-incremented (Legend columns have pre-defined names and users cannot create columns with different names)

In an object's name, users must inform its complete path, in the format Object.Collection.Name. Example:

E3Chart1.Pens.Pen1

On the Type column, one of the following keywords must appear:

•IDispChartPen: E3Chart Pens

•ILegendColumn: E3Chart Legends

•IAxis: E3Chart Axes

•ITableBindRow: Table Link rows