How to Import Data into a Workspace via Dashboard (STD Manual Import)
Prerequisites
We assume you have all prerequisites you may need, including:
- If needed: the VPN is configured to access the Finmars resources
- If needed: access to the Virtual Machine to work with the sensitive information
- Must have: registered in Finmars in the needed region environment (self-registered or registered by Finmars)
- Must have: having permissions set to allow continue with the Action in the Guide
- Must have: to create a new Workspace you must have a License Key (provided by Finmars)
- Must have: installed Standard Configuration package from the marketplace
Import Data into a Workspace via Dashboard (STD Manual Import)
-
Go to the Dashboard menu tab. STD Manual Import tab should be selected. If it's selected, proceed from the step 5. If it's not selected, follow the steps below.
- After you have finished the installation (right upper corner had success popup), you should go to the Dashboard menu tab. Depending on your default layout settings, it may have different layout selected, you need to click on the layout name to navigate to the needed layout.
-
Once the menu is opened, you will be presented a choice of selecting multiple menus. Select STD Manual Import layout.
-
Workflow field denotes which workflow will handle the input. For now, use the default com.finmars.standard-workflow:std-import-pipeline. If you see this import, skip steps 5-6 and go to Step 7.
-
If you do not see this import, double check that you have installed Standard - Workflows module as a part of the Standard Configuration package by following the steps below. This can be done by going to the Configuration → Configuration → Manage
-
Standard - Workflow should be installed there
- The basic way to use STD Import Pipeline is to add all of the needed files yourself.
- That includes currencies, accounts, portfolios, instruments, instruments factor scheduled, instruments accrual scheduled, responsibles, strategies1, transactions, prices, fx-rates, for files see instruction: How to Prepare Standard Template Files for Import.
- You can add multiple files at once in one field.
- Any combination of previously mentioned files is possible. Which means that some fields can be left without any file selected, but it's your responsibility to make sure that you won't be lacking any data.
- Parse Entities from Transactions & Positions checkbox is used when you don’t have simple entities already imported or in the corresponding files (not including Instruments, they need to be in the corresponding file with instruments).
- After adding all those files, you should click Import.
-
-
After clicking Import, information about the workflow status will appear. Refresh status button will refresh the status of the workflow.
-
Open Workflow link will open a more detailed view of the workflow progress. This view shows all of the workflows that will be executed by std-import-pipeline.
-
Zooming in, more information about each separate workflow is shown. Clicking on the workflow, detailed information is shown on the right, including status, created at and finished at, logs, as well as results. Status field has following values: Progress, Success, Nested-Progress, Error. Nested-Progress denotes that a workflow inside the Nested-Progress workflow is being executed.
-
std-import-pipeline executes multiple other workflows. After all of them are completed, the workflow progress will be Success.
-
More details about each workflow can be obtained by clicking on the id of that workflow.
-
After all other workflows have finished Successfully “Status: success” will be shown.
- However, this only confirms that the data transfer was completed, not that the data is free of errors. To check that import has no errors you need to click on Open Workflow after the import is marked as successful.
- The workflow visualization will open. Locate the last executed block in the workflow and click on it, as shown in the screenshot.
- On the right panel, find the Result section. In this section, the top row will indicate whether any errors were encountered. Below, a detailed list of errors will be displayed, specifying the affected files.
- If errors are present, review them carefully and take corrective actions as needed before re-running the import.