|
Required format of .csv (Comma Separated Values) file for use with ImportUnitCSV:
| 1. | File must be comma delimited format |
| 2. | Each field must be Quoted (Surrounded by quotation characters) if the field contains a comma, a return, empty space or a quotation mark character |
| 3. | Every line must contain at least the first three fields and end in a return character. |
| a. | The first 3 fields are required and import can not be done without them, the remainder is optional. |
| 4. | All the normal AyaNova rules for Unit objects apply; duplicate units (same serial number) will not be imported, fields that exceed the maximum length in AyaNova will be truncated. |
| 5. | The csv file must not contain field names in the first row or any header or footer, data only. |
| 6. | The PurchasedDate field will be interpreted in the date format set on the computer the import program is running on. |
| a. | So to confirm what format you should use do an export first on the computer you intend to import on and examine the format of the PurchasedDate field in the Units.csv file. |
| b. | You can change your computers date format in the control panel settings if you need to match a format in the import .csv that isn't your computer's normal date format. |
| 7. | The csv file field order is: |
Serial, Client, UnitModel, Notes, PurchasedFromVendor, SalesReceiptNumber, PurchasedDate, Description, Metered
Review these recommendations and information before importing:
| • | Check the AyaNova Support Forum’s Known Issues & Updates for known issues with any of the import utilities. Easiest is to do a search for the import utility name i.e. ImportUnitCSV |
| • | If a PurchasedFromVendor field is empty then the unit will be imported with the Bought here checkbox checked. |
| o | It will be assumed that the unit was not bought from another vendor but from your company. |
| • | PurchasedFromVendor, Client and UnitModel will be compared case insensitive against their counter parts name field in AyaNova to see if they already exist. |
| o | If they do, the imported unit will be set to use that existing record. |
| o | If they are not found in AyaNova then a new record will be created for them using the name in the import file. |
| o | So it is important to ensure that the import file contains names of these objects *exactly* as they are spelled in AyaNova if you intend to match an existing record. |
| • | PurchasedFromVendors that need to be created on import will be set as WholeSaler vendor type in AyaNova. |
| o | Be sure the purchased date is set correctly in the import .csv file if you care about warranty tracking. |
| o | Since the Unit warranty information is not imported on a case by case basis be sure you have the UnitModel field correct in your CSV file before importing. |
| o | This ensures units will be imported under the correct unit model and you can then set the warranty for all imported units in one shot by setting the unit model warranty. |
| • | Use the export feature to export your current units in AyaNova to a comma separate values file which you can then refer to, to see the correct format. |
| • | Comma Separated Values files (.csv files) can be created and opened directly using Microsoft Access, this is handy if you wish to "massage" the data before importing or examine or work with an exported Units.csv file |
| • | Backup your current AyaNova database before importing, there is no undo feature and it's easy to accidentally have a field in the wrong position. |
| • | When you open the csv file before importing, carefully examine the grid of records displayed to ensure each field is in the correct column before importing. |
| • | For better performance when importing a large number of units, do the import from the fastest connection to the database possible, i.e. don't import units via a dataportal unless performance is not a concern. |
| • | Duplicate units will not be imported, the unit serial number is examined before each unit is imported and if the unit serial number is found to be in AyaNova already then that record is not imported. This means you can re-import the same data safely without getting duplicate records. |
| • | After importing open AyaNova and examine the imported records and ensure fields were imported to the correct area of the unit record. |
NOTE: Using Microsoft Excel to create or edit CSV files may cause errors and be unable to be imported.
A CSV file created or saved by Excel will 99% of the time cause an error to occur as it will not include quotes, sometimes will not make allowances for empty fields, may misinterpret returns or comma’s in the field as being a separate field.
If you presently have an Excel file that is in correctly formatted for the number of fields and placement of fields, and for data – once that is completed, than it is suggested and recommended to import it into a table in Microsoft Access. Right click on the table, select Export…, select CSV from the drop down list and the CSV file will be created correctly with quotes and commas.
Steps to Import Unit Records Once Import File is Created
| 1. | Create the csv file that contains the unit records that you wish to import into AyaNova v3 |
| 2. | Create a backup of the AyaNova v3 database file before continuing. |
| a. | Refer to the Backup & Recovery section of this manual for information on backing up the database for your configuration. |
| 3. | No other users can be accessing AyaNova |
| a. | It is recommended that you perform the import on the same computer where the database resides, and where the csv file is. |
| 4. | Double-click on the ImportUnitCSV.exe file to open the program |
| 5. | Enter an AyaNova Administrator username and password |
| a. | (default is “manager” with password “letmein” if you have not yet changed it as recommended) |
| 6. | Note the messages that occur |
| 7. | Select the menu option Open CSV File |
| 8. | Move to the location of the csv file, select the file, select Open |
| 9. | The ImportUnitCSV utility will read the file and display a message identifying the number if records it finds, and a reminder to confirm the fields and check data before continuing |
| a. | Note – data can not be edited in the ImportUnitCSV utility. It is for viewing only before importing. |
| 10. | The data will now display with a header for each column so that you can confirm data is in the correct field |
| 11. | Once you have confirmed the data, select the menu option Import Data |
| 12. | Data will be imported into AyaNova v3 |
| a. | The time it will take will depend on the number of records to import |
| b. | Duplicate units will not be imported based on the unit serial number. |
| 13. | When the import is finished, a message will display identifying the number of unit records imported. Select OK to close. |
| 14. | Exit out of the ImportUnitCSV utility by selecting the X in the upper right-hand corner |
| 15. | After importing, log into AyaNova v3 and confirm unit records imported and data imported to correct fields |
|