Font size

Importing Data from Excel

The scenario data that you plan to import needs to follow certain naming and formatting conventions. To ensure that naming and formatting are correct, you may want to create a scenario template and fill it with your own data.

The coordinates of the objects in the importing scenarios will be automatically filled, unless:

  • The coordinates are already specified in the file (values differ from zero).
  • The file contains more than 200 locations. In this case only local coordinates storage will be used (using an online provider will be too time-consuming). The search through local storage is available by either of the following:
    • Country and City (the Name column is considered if City is not specified).
    • Country and zip Code>

On importing data into the existing scenario, you can add the missing data to it, but be careful.

To import scenario data from MS Excel files

  1. You can import a scenarios by doing either of the following:
    • Drag-and-drop the required scenarios straight onto the anyLogistix window.
    • Choose Import Scenario on the Welcome Screen menu.
    • Click the Add button at the right end of the Scenarios and controls ribbon, and then select Import.

    The Import dialog box will open:

    If you dragged files to the anyLogistix window, the Import dialog box will instantly show them as the files to import. In other cases the list of files to import will be empty.

  2. Leave the Excel tab selected.
  3. If required, add the additional MS Excel files with the scenario data to import by either dragging them onto the dialog box, or by clicking the browse files link, and navigating to the existing files.

    Multiple import / export supports 10 scenarios. If you are importing e.g. 15 scenarios, the importing process will start for 10 of them, while 5 scenarios will be queued.

  4. If required, change the name of the importing scenarios by clicking Rename scenarios. This option is available if at least one scenario is added to the import list.
  5. If required, you can clear the list of the importing files by clicking Remove all. This option is available if at least two scenarios are added to the import list.
  6. Click the Advanced options if you need to modify the import parameters:

    • Import into existing scenario — [not available if multiple scenarios are added to the import list] enable the toggle button to import into one of the currently open scenarios.
    • Select scenario — [available only if the Import into existing scenario option is enabled] click the drop-down list of the currently opened scenarios to specify the scenario to import the data to.

      Prior to importing data into the existing scenario complete the action below:

      1. Explicitly specify the data to be imported in the Sheets to import option, otherwise, all tables will be imported, resulting in data duplication.
      2. Remove the data from the existing scenario that is about to be updated by the imported scenario to avoid data duplication (e.g. when importing demand, clear the existing demand data).
    • Sheets to import — click the drop-down list to select the tables to import. All other tables will not be imported.

      If no table is selected, all tables will be imported.

    • Import experiments — [enabled by default] if disabled, the experiments contained in the MS Excel file will not be imported.
    • Override existing project conversion rules — [enabled by default] the unit conversions from the importing file will overwrite the project's existing unit conversions.
    • Scenario contains formulas — [disabled by default] if enabled, anyLogistix will consider expressions defined in the template cells.
  7. Click Import to close the dialog box and import the scenario data.

    If import takes too long, you can cancel it by right-clicking the scenario's tab and selecting Cancel import. This option is available only during the scenario import.

    The newly created scenario will be located in the tab that corresponds to the type of the imported scenario:

Please note the following possible issues:

  • All the required units (and their corresponding conversions in case of user-defined units) that are missing in the destination project will be imported with the scenario. You will see a warning message with a list of such units.
  • If you are importing from a database that has wrong structure or does not contain an anyLogistix scenario at all, an error message will pop up notifying that the template is missing data.
  • If the importing file has duplicating objects, they will be skipped. The warning message will list such objects
How can we improve this article?