The Excel to CSPro can be run from the command line, either in an automated way or by bringing up a specification file for modification. Assuming that CSPro was installed to the default directory, the tool is likely found here:
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe"
If you want to open a specification file, simply provide it as the argument to the tool, as in:
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" "My Specifications File.xs2cs"
If you want to open the specification file, run the conversion, and close the tool, use the /run argument:
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" /run "My Specifications File.xs2cs"
It is possible to override the parameters in specification files. Parameters include the names of the files, the starting row for conversion, and the record and item mappings. As Excel to CSPro processes a specification file, it takes the first entry for a file or mapping. In the example below, the input spreadsheet will be Virginia.xlsx:
Parameters specified on the command line are considered before the contents of a specification file. For example, to run the above conversion from the command line on a file called "North Carolina.xlsx":
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" /run "My Specifications File.xs2cs" "Excel=North Carolina.xlsx"
If you had a spreadsheet with two worksheets, Asia and Europe, with the same column specifications, you could use the tool to map the CSPro records and items to one worksheet and then process them using a batch script:
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" /run "Eurasia.xs2cs" "OutputData=Asia.csdb" "Mapping=POPULATION_DATA_REC;;Asia"
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" /run "Eurasia.xs2cs" "OutputData=Europe.csdb" "Mapping=POPULATION_DATA_REC;;Europe"
In the specification file and overrides, the following commands are available:
|Excel=||Specifies the input Excel file.|
|InputDict=||Specifies the CSPro dictionary.|
|OutputData=||Specifies the name of the output data file. The extension of the file indicates the output is a CSPro DB file or a text file.|
|StartingRow=||Specifies the starting row where the data is located.|
|CaseManagement=||Specifies the mode for how cases are added, modified, or deleted.|
|RunOnlyIfNewer=||Specifies if the conversion can conditionally occur.|
|Mapping=||Specifies a mapping between a dictionary record and an Excel worksheet or a dictionary item and an Excel column.|
Dictionary record to worksheet mappings take the form:
@1 as an index meaning that this is the first worksheet in the spreadsheet. People is the name of the worksheet. When processing mappings, Excel to CSPro first tries to find the worksheet using the name. If the name is not present, then the index is used. When overriding values, you can provide either a name, an index, or both.
Dictionary item to column mappings take the form:
Item mappings list only the column number in the worksheet that corresponds to the item. Mapped ID items must be prefaced with the record name, as in:
You can also run production conversions by using the PFF as a command line parameter for Excel2CSPro.exe. For example, if you name your PFF file Convert Data.pff, then you can run the deployment by invoking:
"C:\Program Files (x86)\CSPro 7.1\Excel2CSPro.exe" "Convert Data.pff"
This assumes that CSPro was installed in the default directory. Your PFF file must have a .pff extension.
You can create a PFF file in one of two ways: either  create one with a text editor (such as Notepad or Wordpad), or  have it generated automatically for you when you save a conversion specification file.
The following section shows the options available to you in a conversion PFF file. A PFF file is not case sensitive, so you can use any combination of upper and lower case text.
The [Run Information] block is required and must appear exactly as shown in the example above.
The [Files] block is required and defines the specification file script that will be used during the conversion. The InputData command maps to the Excel command defined above, while InputDict and OutputData are the same as their command line counterparts. If these are not defined, then the conversion will use the values defined in the specification file.
Just as you can override the StartingRow, CaseManagement, RunOnlyIfNewer, and Mapping commands from the command line, you can do the same by specifying them in the [Parameters] block.