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

455
NV9000-SE Utilities
User’s Guide
Theory
There are 3 basic reasons to use the ‘Export to File’ command:
• To create an Excel file (or similar) in which to edit device data more easily. That data can then
be imported to another configuration.
It makes little sense to import the data back into the file from which it came. (But you can do
it if you are careful.)
• To prepare a report of the device data in some publishing software, that is to make the data
readable, digestible, or “pretty.”
• To create an empty Excel file in the proper format — with the proper column headers. You
can then load your configuration data into the Excel file more easily.
There are 2 basic reasons to use the ‘Import Data File’ command:
• To add data to device, category, or physical connection tables that already have data.
The assumption here is that you are modifying an existing configuration.
• To add data to empty device, category, or physical connection tables.
The assumption here is that you are creating a new configuration.
Guidelines for Importing
1 Almost always omit the principal database ID column (or make it blank) when importing.
If, for example, database IDs are present in the Excel file, and a matching database ID exists in
the configuration, the import of that row of the file will fail and the existing item in the con-
figuration will not be changed.
NV9000-SE Utilities creates database IDs whenever it needs them.
2 Unless you are adding new data to a table, clear the table (or the relevant portion of it) into
which you are importing.
(If you delete devices, NV9000-SE Utilities deletes the related physical connections also.)
3 Generally, you cannot import data into a completely empty configuration.
Creating device entries requires there to be a containing level set. A level set requires a
router partition. So at a minimum, the configuration you are creating (or modifying) should
have a complete set of router definitions and level set definitions. Little else is required for
imports.
4 If you are importing previously exported data, remember how you exported it. For example,
if the data were exported using tabs as field delimiters instead of commas, the import
should also use tabs. Also, if the export produced a row of column headers, the import
should recognize the headers (and skip over them).