Grass Valley NV9000-SE v.5.0 - Manual (Page 472)

454
Importing and Exporting
Introduction
Some data fields require you to specify whether to emit the database ID of the field or the
mnemonic that appears in the field. There are reasons for either case.
• Devices and their Physical Connections
With this option, you specify a level set and whether to emit input devices, output devices,
or both. The export command then emits the devices (and the correspond port data) that
belong to the specified level set.
Import Data File
The ‘Import Data File’ command has two similar options:
• Target Table
If you select this option, you can select one of a few tables to which to import data. For the
selected table, you can specify which data fields (identified by column headers) to import
and which to omit.
Some data fields require you to specify whether the data field contains a database ID or a
mnemonic. (There are reasons for either case.)
• Devices and their Physical Connections
With this option, you specify a level set and whether to import input devices or output
devices. (You cannot import both at the same time.) The command then imports the device
data (and the correspond port data) that belong to the specified level set.
A third option, ‘Import Mapping File’, exists. In the process of exporting and importing data, you
might have created and saved “mappings.” This command loads one of your saved mappings.
 Note: NV9000-SE Utilities wants to save and retrieve the mapping files in the configuration
repository on your computer. That is
C:\user\‹username›\CtrlSysConfigs under
Windows 7.
The mapping file contains no configuration data.
Points to Remember
1 The import and export commands affect one of 3 specific sets of data.
Devices.
Categories and category details.
Physical connections.
These data generally form the bulk of configuration data at any particular installation. Not
included are salvos and tieline data among other data.
2 The ‘Import Data File’ command is perilous.
You can seriously damage your configuration by importing data the wrong way. And import-
ing data the right way is extremely tricky. It is our hope that that guidelines in this chapter
will help you avoid the pitfalls.
In fact, because of the perils, there is a ‘Test’ button in the last page of the import command
sequence that lets you try out an import before performing an actual import.
 Make a backup copy of your configuration before using the ‘Import Data File’ command.
(There are no perils when you are exporting data, but while exporting, you should keep in
mind the perils of importing that same data.)