article

The excel Interface is accessed from the main toolbar or from the Toolbox. (View menu > Toolbox > Add > Import > excel Import/Export).

The excel Interface was designed to make importing and exporting multiple worksheets from more than one workbook very fast and easy to do. You can also create your own custom Import/Export code.

Overview

Multiple Table excel Import (MTEI)

The MTEI is capable of automating much of the import process in terms of the table size and cell data type. If you allow the MTEI to be more automated in its implementation, it is extremely useful for importing data that will change over time.

Multiple Table excel Export (MTEE)

The MTEE allows you to export multiple tables to multiple different excel workbooks. The controls and features of this page are the same as the MTEI page. See the documentation above for more information on this page.

Custom Import/Export

The custom Import/Export page allows you to write your own custom code to import and export to excel workbooks. There is sample code in the picklists on importing and exporting from excel.

excel Interface Pages

• Import Page
• Export Page
• Custom Page

Import Page

Import Lines (list)- Displays all of the import lines for the MTEI. You can use the Add and Remove buttons to add additional lines. You may also rearrange lines to group import lines that are importing from the same excel workbook (this will improve speeds greatly as opposed to trying to switch back and forth between the same workbooks).

Import Tables - The MTEI will go in order (from the top) through each checked line of the Import Lines window and execute the import based on its properties specified on the right side.

Note: The MTEI and MTEE may also be started by calling excelmultitableimport() or excelmultitableexport() respectively in a flexscript node.

Import Name - The import name is only used in the Import Lines window to help identify the line.

excel Workbook

The excel Workbook is where you define the name of the excel workbook file that contains the information that you want to import. There are four ways to enter information into this column.

• Unknown workbook name or location ("NEW") If the name or location of the workbook that you want to use are unknown or will change over time then you can select the "NEW" option. Using "NEW" in this field will cause the browse window to open, prompting the user to find the excel file they want to use when executing the import. This is an extremely useful option when the input data will change with different runs or users.
• Same as the previous location (Blank) If you want to continue to use the same workbook as the previous import line then you can leave this field blank. This is the recommended option when you are importing information from multiple sheets in the same workbook. You can reorder import lines using the arrows on the left side of the window in order to group imports that use the same workbook.
• Absolute Path (ABSOLUTE) If the location and the name of the workbook will not change for the entire use of the model then you can enter the absolute path of the excel workbook. For example "C:/tempdirectory/myfile.xls"
  If the file is unable to be found, the import will be stopped and you'll have the option to skip the file or manually select a file to import.

Note: The ".xls" extension is essential in order for FlexSim to find the right excel spreadsheets. You can also use ".xlsx" to import excel 2007 or newer spreadsheets.

• Relative Path (RELATIVE) If your excel file is in the same directory as your model, or in a sub directory, you can enter the relative path of the excel file, or browsing for the file will give the relative path to the file. Alternitvely, you can enter the relative path with respect to the install directory of FlexSim. For example "userprojects/myproject/myfile.xls"
  If the file is unable to be found, the import will be stopped and you will have the option to skip the file or manually select a file to import.

• excel Sheet Name - The name of the excel sheet that contains the import information. For example "Sheet1". If the MTEI does not find the name of the sheet because it does not exist in the workbook or has been entered incorrectly, the import will pause and alert you of the problem. You will then be given the option to exit the import completely or skip the offending import row and continue with the next one. Hint: Look for spaces at the beginning and end of the name if you are alerted that a sheet name does not exist.

  Table Type - Select the type of table in FlexSim that should receive the data from the import. There are 8 table types:

  1. Combiner Component Table
  2. Conveyor Layout Table
  3. Global Table
  4. Pipe Layout Table
  5. Source Table
  6. Time Table
  7. Traffic Control Table
  8. Other

  Headers - Implementing headers will cause the MTEI to import the column and or row names for the table. This is useful for helping you to identify the columns and rows later in FlexSim. The row or column for the header information is automatically calculated. The header information should always come before any data distinction information or actual data.

  Starting Row and Starting Column - The starting row and starting column fields determine where the MTEI will look on the excel sheet for the data it needs to import. Enter the starting location for your data in these cells not the location of the headers or data distinction information. If you leave the values for these cells at 0, the MTEI will automatically adjust where it imports the data from. If you always leave your data at the top left of the worksheet you will never need to enter a value other than 0 in these cells regardless of whether or not you have headers or data distinction information in front of the data.

  Total Rows and Total Columns - The Total Rows and Total Columns fields determine the amount of rows and columns that the MTEI will import. If you set these entries to 0 the MTEI will automatically calculate the number of rows or columns for you. Letting the MTEI calculate the number of rows or columns for you is a great way to allow the developer and or user of the model to add or delete rows and/or columns from the table as necessary without having to worry about changing any other values.

  Note on automatic resizing: The MTEI automatically sizes the FlexSim table that it is importing into to fit the size of the table that it is importing.

  Data Distinction - Data distinction determines how the MTEI will extract values from the excel workbook. There are three commands that the MTEI can use to read excel data:

  • excelreadnum() - If the specified cell contains number data, this command returns the number. Otherwise, it returns 0.
  • excelreadstr() - If the specified cell contains text data, this command returns the text. Otherwise, it returns the value displayed in the cell as text.
  • excelrangeread() - This command reads all cells in a specified range. If a cell in that range contains text data, this command extracts the text. Otherwise, it extracts the value as a number.

  When you import a spreadsheet, you must choose a data distinction mode. The mode you choose will tell the MTEI which of the three commands (or what combination) it should use to extract data from a spreadsheet. The modes are described in the following list:

  1. Numeric - The MTEI uses the excelreadnum() command to extract each cell's value.
  2. Automatic (default) - The MTEI uses both excelreadnum() and excelreadstr() to extract each cell's value. It then analyzes both results to determine whether the cell contains string or number data, and based on that, which result to put in the table.
  3. Per Column - For all the cells in a given column, the MTEI gets the value in the first non-header row (the beginning of the column), which must be a number. Depending on that value, the MTEI will use excelreadnum() or excelreadstr() to extract the data in that column. The cell containing this value is excluded from the final table in FlexSim.
  4. Per Row - For all the cells in a given row, the MTEI gets the value in the first non-header column (the beginning of the row), which must be a number. Depending on that value, the MTEI will use excelreadnum() or excelreadstr() to extract the data in that row. The cell containing this value is excluded from the final table in FlexSim.
  5. Text - The MTEI uses the excelreadstr() command to extract each cell's value.
  6. Values Only (very fast) - The MTEI will use the excelrangeread() command to read in all values of the table.

  For the Automatic mode, the MTEI will attempt to determine whether the cell contains text or number data. While this process works fairly well, the MTEI will occasionally be wrong. For example, a cell with number data, formatted as a fraction, will be imported as text like "1/5" rather than a number like 0.20. Empty cells will be read in as a string. In order to correctly import a worksheet, you may need to change the formatting in excel or the data distinction mode.

  For the Per Column and Per Row modes, the MTEI reads the first value in a row or column and uses that value to determine how to extract the remaining values in that row or column. The MTEI recognizes four possible values:

  1. Numeric Data - The MTEI will extract the data in this row/column using excelreadnum()
  2. Text Data - The MTEI will extract the data in this row/column using excelreadstr()
  3. Flexscript Data - The MTEI will extract the data in this row/column using excelreadstr(). If importing into a table, the MTEI will toggle this cell's node as FlexScript.
  4. C++ Data - The MTEI will extract the data in this row/column using excelreadstr(). If importing into a table, the MTEI will toggle this cell's node as C++. If this occurs, you will be prompted to compile the model after the import is complete.

  The Values Only mode uses the excelrangeread() command. This command imports text cells the same way excelreadstr() does. However, all other values, including dates and times, are interpreted as raw numbers. You can use the VALUE() function in excel to see the raw number for any non-text cell.

  The following table shows some examples of how an excel cell might be extracted with each of the three commands:

  Cell Value	Cell Format	excelreadnum()	excelreadstr()	excelrangeread()
  1.54	Number	1.54	"1.54"	1.54
  10	Number	10.0	"10"	10.0
  2/8/2016	Date	42408.0	"2/8/2016"	42408.0
  some text	Text	0	"some text"	"some text"
  1/5	Fraction	0.20	"1/5"	0.20

  Note on excel Import Performance: For small tables, the data distinction mode has very little effect on the import speed; small tables are usually imported very quickly. For larger tables, however, the data distinction mode can have a dramatic effect on import speed. To ensure the fastest speed possible, choose a data distinction mode that only uses excelreadstr() to read cells with text data. For example, if you have a column of text data and a column of number data in a spreadsheet, use the Per Column distinction mode (with the correct data distinction values), or the Values Only mode.

  Import Dates and Times as Numbers - This option is only available for the Automatic Data Distinction setting. When checked, the importer will import cells from excel that are formatted as dates and times as numbers. It will also convert the number to be useable by FlexSim which is the number of seconds since Jan 1 1601.

  Import Table on Model Reset - If checked, FlexSim will re-import this table when the model is reset. This will ONLY occur if the excel file has been changed since the last time the table was imported.

  Post Import Code - After all the import lines are executed, the MTEI can execute Post Import Code. You can write custom code in this trigger to do any additional operations after all tables have been imported.

  Execute Post Import Code - If checked, the Post Import Code will be executed once all tables have been imported.

  Importing to a Bundle

  Global Tables may be set to use a bundle to store their data. Or, when using the Other table type, you can select a node in the tree that has bundle data. In these cases the import will create the correct fields in the bundle for the imported data. Due to the way bundles work, there are a few restrictions when importing to a bundle.

  Automatic Data Distinction - When automatic data distinction is used, the importer will only look at the datatype of the first cell in a column and set the entire column's data type to that type. This is because each column of a bundle must either be all numeric or all string data.

  Column Data Distinction - Selecting Column will cause the importer to behave as if using Automatic Data Distinction. This is because rows in a bundle column may not have differing data types.

  Row Headers - As bundles do not have row headers, checking Use Row Headers has no affect on the import.

  Column Headers - Bundles must have a Column (or field) name. Therefore, Use Column Headers is always used whether checked or unchecked.

  Flexscript/C++ Data - Bundles can only have string and numeric data.

  Export Page

  

  Unlike the MTEI, the MTEE does not use any data distinction when writing to the excel file. The data type is taken from the FlexSim node data type.

  Starting Row and Starting Column - The starting row and starting column fields specify which cell in excel the data from FlexSim will start being exported to.

  There is no Number of Rows or Number of Columns fields. The export will take the entire table.

  Exporting Bundle Data

  When using the Other table type, you can select any node in the tree to export your data from. If the node has bundle data, the bundle's data will be exported to excel. Because there are no Row Headers in a bundle, selecting Use Row Headers has no effect.

  Custom Page

  

  Description - This field has no impact on the custom import/export. It is purely for the user's information.

  Code - Enter your own code to import/export from excel.

  To execute your custom import or export code through a flexscript node or trigger, call the following:

  treenode excelauto = node("/Tools/excelAuto", model());  executefsnode(getvarnode(excelauto, "CustomImport"),NULL);  // or  executefsnode(getvarnode(excelauto, "CustomExport"),NULL);