Fig. 1 “Import Data” link.
The first step is simply to select the appropriate table to be populated in the SIMPLer system. (Initial development has been focused on refining the system for customer data imports. Additional tables will be made available at a future date.) Selecting the appropriate table and clicking on the “Load Interface” button will redirect the user to the next stage (Fig. 2).
Fig. 2. Phase no. 1
The second phase of the import involves selecting a list of fields from those available to be imported for the given table. There is a list of mandatory fields and optional fields. User can select optional fields by selecting the fields specified in the left list and moving them into the list on the right side. To move the entries between lists use the blue arrows or double click on the selected entry. The red arrows allow the user to rearrange the selected entries (Fig. 3). Note: The order of the mandatory fields can not be modified.
Fig. 3. Field Selection & CSV Upload
NOTE: Order of fields is important as it must reflect the order of columns in the CSV file.
After preparing the fields the user must upload a CSV file. A standard CSV file contains fields as shown on the example on the page, i.e. fields must be double qouted (i.e.: “field”) and must be separated by comma (,). Programs like Excel give uses the option to save a spreadsheet as a CSV file which makes it easier to generate the file to upload.
On the bottom of the page there is a select list which provides values for fields that have limited values allowed for importing (Fig. 4). This table shows valid entries for these fields. For example a user can not upload just any value into the “payment method” field. The only valid entries are: cash, cheque, credit card, debit card, direct debit, online transfer or standing order. Attempts to load anything else will cause an error which the system will force the user to resolve.
Some fields may require some initial setup in SIMPLer before a value can be specified for a customer. These fields have text represented in red: “The field is empty”. This tells the user that they can not upload data to this field until this field is setup elsewhere in SIMPLer. For example the “Master Agent” field is empty, because there are no master agents setup in this SIMPLer instance. A user would first have to go to the “users->Master Agent” page and create master agents.
Fig. 4. Information about pre-populated fields
During the next phase of the import (Fig. 5) all data is presented with errors that needs to be corrected. Short description of error pointing to a given field in matrix is seen on the top of the page. Clicking on the description of error will redirect User to the field where error occured. All errorenous fields are covered by red rectangle so it is very easy to spot them. In case that order of fields is wrong, User can also update it using “Change order of fields” feature.
There is “Return to top” link on the right bottom of the page which will redirect User back to the top of the page.
On the bottom of the page there is information about columns used and data that must be inserted into given field (if it is required).
This phase must be reloaded as long as all errors are corrected.
Fig. 5. Error Correction
After all errors are corrected an “IMPORT” button will be available that allows the user to go to the next step of the import process (Fig. 6).
Fig. 6. “IMPORT” button
Fig. 7. Final Confirmation
After clicking “CONFIRM” all mapped data will be imported into the SIMPLer database. This is the final confirmation that all went well (Fig. 8)
Fig. 8. Import Success Message
Azotel | River House | Blackpool Park | Cork | Ireland
US +1-312-239-0680 | IE +353-21-234-8100 | UK +44-207-193-4170 | SA +27-11-083-6900