Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
import_and_export:importing_assets [2021/04/19 15:24] – [Doing the import] Gary Willetts | import_and_export:importing_assets [2021/08/10 15:56] – [Doing the import] Gary Willetts | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{indexmenu_n> | + | {{indexmenu_n> |
====== 16.09. Importing assets ====== | ====== 16.09. Importing assets ====== | ||
Line 7: | Line 7: | ||
The first row of the spreadsheet is for the column headers and is **not** imported. | The first row of the spreadsheet is for the column headers and is **not** imported. | ||
- | The first 32 columns (up to, and including column | + | The first 34 columns (up to, and including column |
< | < | ||
Line 17: | Line 17: | ||
During the import process, if any properties or entities (like asset locations) do not exist, they will be created. If any options for drop down list properties or standard asset drop down lists (categories) are found not to exist, they will also be created. | During the import process, if any properties or entities (like asset locations) do not exist, they will be created. If any options for drop down list properties or standard asset drop down lists (categories) are found not to exist, they will also be created. | ||
- | The import spreadsheet must contain these columns in this order (the first 2, //Code// and //Description// are mandatory, the others are all optional): | + | The import spreadsheet must contain these columns in this order (//Description// and //Current status// are mandatory, the others are all optional): |
^ Column number | ^ Column number | ||
- | | 1 | A | Code | **Mandatory**. | + | | 1 | A | Code | 255 alphanumeric characters. A code that the asset can be recognised by | |
| 2 | B | Description | | 2 | B | Description | ||
| 3 | C | Make | 255 alphanumeric characters | | 3 | C | Make | 255 alphanumeric characters | ||
Line 32: | Line 32: | ||
| 11 | K | Disposal date | Valid date in current operating system format. The date the asset will be or was disposed of | | | 11 | K | Disposal date | Valid date in current operating system format. The date the asset will be or was disposed of | | ||
| 12 | L | Last verification date | Valid date in current operating system format | | | 12 | L | Last verification date | Valid date in current operating system format | | ||
- | | 13 | M | Location code | 20 alphanumeric characters. The code the location name will have. Will be matched against the names currently in the database. If a name with this code does not exist, one will be created. This field is mandatory if you want mSupply to create the name. | | + | | 13 | M | Location code | 20 alphanumeric characters. The code the location name will have. Will be matched against the names currently in the database. If a name with this code does not exist, one will be created |
- | | 14 | N | Asset user name | 255 alphanumeric characters. The name of the asset user in the format "// | + | | 14 | N | Location name | 255 alphanumeric characters. |
- | | 15 | O | Asset user phone number | + | | 15 | O | Asset user name | 255 alphanumeric characters. The name of the asset user in the format "// |
- | | 16 | P | Asset user email | 255 alphanumeric characters | | + | | 16 | P | Asset user phone number |
- | | 17 | Q | Custodian location | + | | 17 | Q | Asset user email | 255 alphanumeric characters | |
- | | 18 | R | Custodian name | 255 alphanumeric characters. The name of the custodian | | + | | 18 | R | Custodian location |
- | | 19 | S | Custodian phone number | + | | 19 | S | Custodian name | 255 alphanumeric characters. The name of the custodian | |
- | | 20 | T | Custodian email | 255 alphanumeric characters | | + | | 20 | T | Custodian phone number |
- | | 21 | U | Current status | + | | 21 | U | Custodian email | 255 alphanumeric characters | |
- | | 22 | V | Proposed status | + | | 22 | V | Current status |
- | | 23 | W | Type | 255 alphanumeric characters. Will be created if it doesn' | + | | 23 | W | Proposed status |
- | | 24 | X | Condition | + | | 24 | X | Type | 255 alphanumeric characters. Will be created if it doesn' |
- | | 25 | Y | Purchase price | Number, currency. The cost of the asset when it was purchased | | + | | 25 | Y | Condition |
- | | 26 | Z | Purchase costs | Number, currency. Any costs that are ot be added ot the purchase proce to arrive at the total value of the asset to be depreciated | | + | | 26 | Z | Purchase price | Number, currency. The cost of the asset when it was purchased | |
- | | 27 | AA | In service date | Valid date in current operating system format. The date the asset starts to depreciate from | | + | | 27 | AA | Purchase costs | Number, currency. Any costs that are ot be added ot the purchase proce to arrive at the total value of the asset to be depreciated | |
- | | 28 | AB | Useful lifespan (months) | + | | 28 | AB | In service date | Valid date in current operating system format. The date the asset starts to depreciate from | |
- | | 29 | AC | Disposal value | Number, currency. The value of the asset at the end of its useful life | | + | | 29 | AC | Useful lifespan (months) |
- | | 30 | AD | Insurer name | 255 alphanumeric characters | | + | | 30 | AD | Disposal value | Number, currency. The value of the asset at the end of its useful life | |
- | | 31 | AE | Insurance policy | + | | 31 | AE | Insurer name | 255 alphanumeric characters | |
- | | 32 | AF | Insurance renewal date | Valid date in current operating system format. The date the insurance should be renewed by | | + | | 32 | AF | Insurance policy |
- | | 33 | AG | Notes | Lots of alphanumeric characters! Any other information that needs to be stored against the asset | | + | | 33 | AG | Insurance renewal date | Valid date in current operating system format. The date the insurance should be renewed by | |
- | | 34 onwards | + | | 34 | AH | Notes | Lots of alphanumeric characters! Any other information that needs to be stored against the asset | |
+ | | 35 onwards | ||
Here is an example spreadsheet you can use (contains no property columns, only the standard mSupply columns): {{ : | Here is an example spreadsheet you can use (contains no property columns, only the standard mSupply columns): {{ : | ||
+ | |||
+ | <WRAP important center round 90%> | ||
+ | When entering dates in the spreadsheet, | ||
+ | </ | ||
===== Doing the import ===== | ===== Doing the import ===== | ||
Line 62: | Line 67: | ||
{{ : | {{ : | ||
- | mSupply uses the code field to determine whether the asset being imported is a duplicate; an asset with the same code as one already in the database is determined to be a duplicate. In the //If duplicate codes are detected// section you tell mSupply what to do if it encounters a duplicate asset during the import: | + | mSupply uses the **code** field to determine whether the asset being imported is a duplicate; an asset with the same code as one already in the database is determined to be a duplicate. Any assets with no code are ignored during duplicate checking i.e. an asset with no code can //never// be a duplicate and will always be imported as a new asset. In the //If duplicate codes are detected// section you tell mSupply what to do if it encounters a duplicate asset during the import: |
* **Import as new asset:** this option will import the duplicate as a new asset | * **Import as new asset:** this option will import the duplicate as a new asset | ||
- | * **Skip the duplicate without asking:** the duplicate will not be imported and that row if the spreadsheet will be ignored | + | * **Skip the duplicate without asking:** the duplicate will not be imported and that row of the spreadsheet will be ignored |
* **Stop the import:** as soon as a duplicate is encountered, | * **Stop the import:** as soon as a duplicate is encountered, | ||
- | * **Update the existing asset:** the asset that already exists with the code in the database will be updated with the new information contained in the spreadsheet row. A new asset will not be created. | + | * **Update the existing asset:** the asset that already exists with the code in the database will be updated with the information contained in the spreadsheet row. A new asset will not be created. BE CAREFUL WITH THIS OPTION: if a cell is blank in the spreadsheet then the corresponding value is removed from the asset (if it had a value set for it), not left as it is. |
The //Field// column of the table shows you all the columns that mSupply has detected in your import file, the //Value// column shows the values it has found in the cells for that row of the spreadsheet. You can move through the rows of the spreadsheet using the **Previous** and **Next** buttons. If you try to go beyond the first or last row of the spreadsheet mSupply will let you know. | The //Field// column of the table shows you all the columns that mSupply has detected in your import file, the //Value// column shows the values it has found in the cells for that row of the spreadsheet. You can move through the rows of the spreadsheet using the **Previous** and **Next** buttons. If you try to go beyond the first or last row of the spreadsheet mSupply will let you know. | ||
Line 74: | Line 79: | ||
When the import has finished you will be shown a message telling you how many assets were imported and how many rows of the spreadsheet were skipped, ignored or failed. | When the import has finished you will be shown a message telling you how many assets were imported and how many rows of the spreadsheet were skipped, ignored or failed. | ||
- | ===== Customer specific variations ===== | + | <WRAP info center round 90%> |
- | + | All the assets created by the import will have the text " | |
+ | </ | ||
\\ | \\ | ||
\\ | \\ | ||
- | | // Previous: | + | | // Previous: |
---- struct data ---- | ---- struct data ---- | ||
pagestatus.status | pagestatus.status | ||
---- | ---- | ||