Differences

This shows you the differences between two versions of the page.

--- import_and_export:importing_assets [2021/05/03 08:05] – [Import spreadsheet format] Gary Willetts
+++ import_and_export:importing_assets [2021/10/08 09:31] – Gary Willetts
@@ Line 1: / Line 1: @@
 {{indexmenu_n>90}}
+====== 17.09. Importing assets ======
-====== 16.09. Importing assets ======
 Assets are imported directly from Excel spredsheets so there is no need to export data from the spreadsheet to a tab delimited text file first (as you need to do for other imports).
@@ Line 42: / Line 41: @@
 | 21             | U              | Custodian email                 | 255 alphanumeric characters |
 | 22             | V              | Current status                  | **Mandatory**. 255 alphanumeric characters. Will be created if it doesn't exist |
-| 23             | W              | Proposed status                 | 255 alphanumeric characters. The proposed next status of the asset. Will be created if it doesn't exist. Please note that there is no way of telling mSupply what proposed statuses are allowed to follow which current statuses during import. This can only be done manually in the asset settings (see the [[assets:assets_setup|]] page for details). There is also no validaiton carried out on the proposed status during import - if you put a status in here, it will be imported and set for the asset, so make sure the proposed status values are accurate. |
+| 23             | W              | Proposed status                 | 255 alphanumeric characters. The proposed next status of the asset. Will be created if it doesn't exist. Please note that there is no way of telling mSupply what proposed statuses are allowed to follow which current statuses during import. This can only be done manually in the asset settings (see the [[assets:assets_setup|]] page for details). During import all proposed statuses are assumed to be valid and will not be checked. There are, however, some important exceptions:\\ 1. If the current status of an asset is designated to be a final status, any proposed status will be ignored.\\ 2. If an imported asset has a current status which has some possible proposed statuses assigned, if the proposed status is not included in these, it will be added to them.\\ \\ So, be careful with the proposed statuses in the import file: you could make a mess if you have already set up which statuses can follow which and you don't follow that in the import file. |
 | 24             | X              | Type                            | 255 alphanumeric characters. Will be created if it doesn't exist |
 | 25             | Y              | Condition                       | 255 alphanumeric characters. Will be created if it doesn't exist |
@@ Line 51: / Line 50: @@
 | 30             | AD             | Disposal value                  | Number, currency. The value of the asset at the end of its useful life |
 | 31             | AE             | Insurer name                    | 255 alphanumeric characters |
-| 32             | AF             | Insurance policy nummber        | 255 alphanumeric characters |
+| 32             | AF             | Insurance policy number        | 255 alphanumeric characters |
 | 33             | AG             | Insurance renewal date          | Valid date in current operating system format. The date the insurance should be renewed by |
 | 34             | AH             | Notes                           | Lots of alphanumeric characters! Any other information that needs to be stored against the asset |
@@ Line 85: / Line 84: @@
 \\
 \\
-|  //  Previous:  **[[import_and_export:importing_a_supplier_invoice]]** | | Next: **[[import_and_export:export_items]]** //  |
+|  //  Previous:  **[[import_and_export:importing_a_supplier_invoice]]** | | Next: **[[import_and_export:importing_regions]]** //  |
 ---- struct data ----
 pagestatus.status    :
 ----