Excel File Command
The Excel file command is designed to execute multiple commands using a single command.
-operation ExcelFile -filepath "C:\temp\CreateDocumentSets.xlsx"
As the Excel File command is new, it currently only supports the CreateDocumentSet operation.
Example: Excel File
An Excel spreadsheet containing multiple CreateDocumentSet commands.
The MacroView Provisioner console app uses specific file system directories at runtime in order to generate and output files. Therefore, concurrent processing is not supported. Only run one instance of Provisioner at any one time.
The Excel File command can be used to execute hundreds of commands by running a single command.
Start by provisioning a handful of document sets, once the end-to-end process has been run and the outcome validated, then scale as required.
Recommended number of Excel File operations
The recommended number of operations per Excel file are:
- Create Document Set (100 to 1000 at a time).
Processing times can vary depending on the environment and performance of the SharePoint farm.
For Office 365 provisioning times and outcomes can vary on a daily basis. It is recommended to start with a small to medium number of operations and then scale based on successful runs and desired timeframes.
Author an Excel file
Please use the provided Excel spreadsheet CreateDocumentSets.xlsx or custom client spreadsheets.
The spreadsheet contains one worksheet (tab), this worksheet is named Operations.
When MVSP Standalone executes an Excel file, it looks for a worksheet named Operations and it reads in the columns and rows.
All cells in the Operations worksheet must be formatted as Text.
If you are going to add numeric values to cells, then you must first format the entire column as Text, prior to entering numeric values into cells.
You will know when a cell that contains a numeric value is formatted correctly by the green icon in the top left corner of the cell (see image below).
Clicking in the 1001 cell above displays a warning icon to the left of the cell.
Clicking on the warning icon displays the following flyout, that lets the user know that the numeric value is stored as text, this is exactly what we want.
Storing everything as text ensures that values are retained and imported correctly.
Storing everything as text stops Excel from changing the value that is stored.
For example, say there are leading zeros on a number, then these leading zeros would be removed by Excel.
Another example is a date time value, to stop Excel from incorrectly storing the date time value, we require that date times are entered as ISO 8601 strings that are stored as text.
Lets create 3 document sets in an existing library.
Open the CreateDocumentSets.xlsx spreadsheet and go to the Operations worksheet (tab).
Enter the values into the provided columns.
Execute the Excel File
The Excel file can then be specified as input for the console command.
Run > Command Prompt
Run a command prompt using the Windows Start button and search for Command Prompt (CMD)
cd "C:\Program Files\MacroView\MVSP\Standalone"
Use the ConsoleCommand.xlsx spreadsheet to author a Excel file command.
Open the spreadsheet and go to the Execute Excel File workbook (tab).
Fill in the provided columns and copy / paste the Excel File Command to the command prompt window.
C:\Program Files\MacroView\MVSP\Standalone>MacroView.Solutions.Provisioning.Console.exe -operation ExcelFile -filepath "C:\temp\CreateDocumentSets.xlsx"
C:\ProgramFiles\MacroView\MVSP\Standalone> MacroView.Solutions.Provisioning.Console.exe -operation ExcelFile -filepath "C:\temp\CreateDocumentSets.xlsx"
Result (Excel file run)
The results of a Excel file run are written to a CSV file.
The output and statistics displayed above are written to the log file.