assets:asset_management

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
assets:asset_management [2021/10/08 09:52] – [Assets in the Dashboard] Gary Willettsassets:asset_management [2023/03/15 23:11] (current) – [Assets in a synchronisation system] Mark Glover
Line 167: Line 167:
   * **Address 2:** A read only field that displays the Main/Billing address 2 field of the location name.   * **Address 2:** A read only field that displays the Main/Billing address 2 field of the location name.
  
-**Asset user:** The asset user is usually the person who uses the asset the most or who you would contact if you needed information about it. But you can use this field (and the Custodian fields) to record the contact information you need. The asset user fields are all read-only because the information is actually recorded as a contact of the location name. See [[names:adding_and_editing#contacts_tab|5.01. Names: using, adding and editing]] for details on how to do this. To tell mSupply the contact is an asset user set the contact's //Category// field to "**Asset user**". +**Asset user/User contact:** The asset user is usually the person who uses the asset the most or who you would contact if you needed information about it. But you can use this field (and the Custodian fields) to record the contact information you need. The asset user field values are read only and come from contacts of the location name. See [[names:adding_and_editing#contacts_tab|5.01. Names: using, adding and editing]] for details on how to add contacts to a name. To tell mSupply the contact is an asset user set the contact's //Category// field to "**Asset user**". 
-  * **Asset user Name:** The contact's //First name// followed by their //Last name// fields.+  * **Asset user Name:** Select one of the location name's contacts that has a category of //Asset user//. The entries in the list are made up of the contact's //First name// followed by their //Last name// fields.
   * **Phone:** The contact's //Phone// field value.   * **Phone:** The contact's //Phone// field value.
   * **email:** The contact's //Email// field value.   * **email:** The contact's //Email// field value.
Line 273: Line 273:
 Asset settings are system data and so they are settable on the primary server only. Any asset settings created or edited here are synchronised to all other sites. Asset settings are system data and so they are settable on the primary server only. Any asset settings created or edited here are synchronised to all other sites.
  
-Assets themselves are store based data so they can only be created and edited in the active copy of a store. Assets will synchronise from here to the central server and any collector copies of the store only.+Assets themselves are store based data so they can only be created and edited in the active copy of a store. Assets will synchronise from here to the central server only.
  
 ===== Assets in the Dashboard ===== ===== Assets in the Dashboard =====
-Asset data can easily be included in the mSupply Dashboard. +Asset data can easily be included in the mSupply Dashboard, as in this simple example here: 
- + 
-An example can be seen here: +
 {{ :assets:2021-06-08_17-15-14.png?600 |}} {{ :assets:2021-06-08_17-15-14.png?600 |}}
 +
 +See the [[https://docs.msupply.foundation/en:dashboard]] pages for details on the mSupply dashboard.
 \\ \\
 \\ \\
  • Last modified: 2021/10/08 09:52
  • by Gary Willetts