One of the methods of populating the grid with call handlers you wish to add to edit is browsing to a CSV file and loading those handlers based on their alias or extension number.  The format of the CSV file only needs to follow two rules:

 

1. The values need to be separated by commas.  Tab or CrLf or semicolon separated files will not be parsed correctly.

2. It needs to include a column header in the first line of “extension” and/or “alias”.  This is not case sensitive and can be padded on  the left or right (or both) with spaces.

 

For instance, a file that starts like this will be parsed without a problem:

 

display name, alias, extension, recipient

Opening greeting, openinggreetingch,,Eadministrator

Sales Info Line,ch_salesinfoline,1174,Eadministrator

...

 

If the CSV file contains a column for both Extension and Alias, the extension column is used to search first.  If a match is not found then the alias column value will be used.

 

Each row of the CSV file will be read in and the corresponding column that contains “extension” (column #3 above) or “alias” in the first line (column #2 above) will be used to search for the call handler.  If a match is found, that handler will be added to the grid.  If more than one match is found for that extension (which should never happen) or alias, an error dialog will pop up alerting you to that fact and that row will be skipped in the file.

 

In the example above, the first row tells the parser that column #3 contains the handler’s extensions and column #2 contains the alias.  The next row would cause the parser to search for an alias of “openinggreetinch” among all call handlers on the local box for a match since no extension value is provided.  The 3rd row does have an extension number of 1174 which will be searched for first.  It no match is found then the alias of “ch_saesinfoline” will be searched for.

 

Again, only call handlers associated with the local Unity server will be loaded.  If you have multiple Unity servers in the same Exchange site, only those handlers associated with the local Unity server the BulkEdit tool is being run on will be loaded into the grid.