You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<divclass="note">Status log reasons are managed from the Open mSupply central server. <ahref="/docs/getting_started/central">Click here to find out out more</a>.</div>
98
+
<divclass="note">Status log reasons are managed from the <ahref="/docs/getting_started/central">Open mSupply central server</a>.</div>
97
99
98
100
When users add a new status log against a particular asset, more detail can be provided with a reason associated with the new status. For example, an asset which has been labled `NON_FUNCTIONING` could be assigned a reason of `power supply broken`. These reasons are customisable, and associated with a particular status.
When importing assets from a store, they will be assigned to that store.
85
+
Assets are automatically assigned to the logged in store.
86
86
87
-
<!--
88
-
TODO: Add link to central server docs when they are created
89
-
-->
90
-
91
-
When importing assets on the central server, an additional field of `store` will be required which will assign assets to their respective stores.
87
+
This differs when importing assets on the Open mSupply Central Server - an additional field of `Store` will be required to assign assets to their respective stores.
92
88
93
89
Information will need to be entered in the format provided by the csv template in order for Open mSupply to be able to process and upload this data.
Sometimes errors occur when importing CCE assets. Here are some common errors you might encounter:
115
+
116
+
##### Upload Errors
117
+
118
+
After uploading your CSV file, your data will be validated and displayed to you to review. At this step, if the data in your uploaded file is not valid, you will see an error message and won't be able to continue to the import step.
119
+
120
+
121
+
122
+
Common mistakes here are uploading a file type other than CSV, or if you included some duplicate asset numbers in your file. You'll see these errors in the `Error message` column.
123
+
124
+
You can use the `Export` button at the bottom of the upload window to download a CSV file which includes the error messages, to investigate what went wrong.
125
+
126
+
Once you have corrected the errors, you can go back to the `Upload` tab to upload the corrected file.
127
+
128
+
##### Upload Warnings
129
+
130
+
If certain data is missing or incorrect (such as the installation date and other date columns) you'll see a warning message rather than an error. This is because the asset can still be created without these date fields, but it's recommended to include them.
There will be a `Warning` column, which will alert you to which fields are missing or incorrect. You can still proceed with the import with this missing data if you wish.
135
+
136
+
<divclass="note">Sometimes spreadsheet software can reformat dates, into a format we can't process. If your dates are missing on import, check your CSV file and ensure the dates are in DD/MM/YYYY format!</div>
137
+
138
+
##### Import Errors
139
+
140
+
The import step is where the new cold chain assets are actually created in the system. If there are any errors at this step, you'll see a message like this:
This usually happens when you have an asset in your import file which has the same asset number as an existing asset. You'll see the error message in the `Error message` column. Again, you can export a CSV file with the error messages to investigate what went wrong.
145
+
110
146
#### Export
111
147
112
-
A list of assets can be exported as a csv using the `Export` button.
148
+
A list of existing assets can be exported as a csv using the `Export` button.
0 commit comments