You can edit the exported data in a number of ways:
In a text editor that supports Unicode (Notepad, for example). Save the file with Unicode encoding.
In Excel with the DeltaV Bulk Edit Add-In (limit of 255 parameters per cell).
In an ODBC data source with Microsoft Access.
The sections that follow provide the information you need to implement user-defined imports and exports. The first sections explain in detail how to create format specification files, export a configuration object, edit the exported data, and import the edited data. The sections following that outline how to bulk edit configuration objects that Bulk Edit supports. The remaining sections outline how bulk edit more complex configuration objects.
Throughout these sections, import and export operations are also described as transfers and the data in the spreadsheet, text file, or relational database is called external data.
It is recommended that you create a backup copy of the configuration database before bulk importing data.
You can specify one object type for each import or export operation. For example, if you build a spreadsheet of channel data, the associated cards and controllers must already exist in the configuration database for the channel data to import correctly. The imported file can contain the card and controller names as well as the channel data, but these items are only used during the import to map the channel data correctly in the configuration database.
You can also export and import using ODBC data.
Bulk Edit does not support import or export of PROVOX or RS3 I/O.