import_and_export:importing_names

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
import_and_export:importing_names [2022/01/28 19:16] – [Introduction] Mark Gloverimport_and_export:importing_names [2024/04/04 15:07] (current) – [Setting up the import file] Gary Willetts
Line 14: Line 14:
  
  
-<WRAP center round tip 60%> +<WRAP center round important 60%> 
-If you are in a [[other_stuff:virtual_stores|multi store system]], do the names need to be visible in all stores?  If not, consider setting the //Names created in other stores not visible in this store// or //Patients created in other stores not visible in this store// preferences in other stores. See the [[other_stuff:virtual_stores#preferences_tab|Store preferences]] section for details.+  * If you are in a [[other_stuff:virtual_stores|multi store system]], do the names need to be visible in all stores?  If not, consider setting the //Names created in other stores not visible in this store// or //Patients created in other stores not visible in this store// preferences in other stores. See the [[other_stuff:virtual_stores#preferences_tab|Store preferences]] section for details. 
 +  * If the relevant preference is turned on, all new names will be visible in the store you are logged into <wrap em>only</wrap>. If it is turned off, then all new names will be visible in <wrap em>all</wrap> stores.
 </WRAP> </WRAP>
 +
  
 ==== Setting up the import file ==== ==== Setting up the import file ====
Line 34: Line 36:
 | K       | Last name. This column is the difference between a customer and a patient:  A customer will have a blank last name, a patient **must** have a non-blank last name | | K       | Last name. This column is the difference between a customer and a patient:  A customer will have a blank last name, a patient **must** have a non-blank last name |
 | L       | First name (applies only to people)         | | L       | First name (applies only to people)         |
-| M       | Date of birth (please use 4-digit year)     |+| M       | Date of birth (use 4-digit years)     |
 | N       | Gender (enter "F" or "True" for females. All other values taken as male) | | N       | Gender (enter "F" or "True" for females. All other values taken as male) |
 | O       | Custom 1                  | | O       | Custom 1                  |
Line 46: Line 48:
 | W       | Postcode (Zip code)       | | W       | Postcode (Zip code)       |
 | X       | On hold ("T" or "Y" for true, anything else, including blank, for false) | | X       | On hold ("T" or "Y" for true, anything else, including blank, for false) |
 +| Y       | Latitude (positive or negative decimal number)  |
 +| Z       | Longitude (positive or negative decimal number) |
 +| AA      | ID. The ID of the name record in the mSupply database. Optional and ignored unless updating a name. If you're updating a name then it is mandatory. During an update, the name this ID belongs to is compared with the name the code in column A belongs to. If they are the same record then the update will proceed, otherwise this line in the import file will be skipped. |
  
 Column C describes the type of the name being imported. That is, whether it is a customer, supplier, manufacturer, donor or patient. A name could be any one of these or several of them. To indicate which of these the name is, simply include the letter shown in the table below in the type field (letter order is not important): Column C describes the type of the name being imported. That is, whether it is a customer, supplier, manufacturer, donor or patient. A name could be any one of these or several of them. To indicate which of these the name is, simply include the letter shown in the table below in the type field (letter order is not important):
Line 71: Line 76:
     * Ignore the first line.  You will want to if you have used the first row for column headings     * Ignore the first line.  You will want to if you have used the first row for column headings
     * Strip out line feeds and quote characters.  You will want to do if you've used Excel to save the text file.     * Strip out line feeds and quote characters.  You will want to do if you've used Excel to save the text file.
-  * If there are non-printable characters before or after the name, code, last name or first name they will be removed. Any non-printable characters in the name, code, last name or first name will be replaced with an underscore (<wrap em>_</wrap>).+  * If there are non-printable characters before or after the name, code, last name or first name they will be removed. Any non-printable characters in the name, code, last name or first name will be replaced with an underscore (<wrap em>_</wrap>) - but note that spaces in the code will not be affected.
 </WRAP> </WRAP>
  
Line 94: Line 99:
  
 {{ :import_and_export:names_import.png? |}} {{ :import_and_export:names_import.png? |}}
- 
-<WRAP info center round 90%> 
-Please note that the visibility of any new names created will be subject to the state of the //Names created in this store not visible in other store// preference (see [[other_stuff:virtual_stores#the_preferences_tab|Virtual stores, the Preferences tab]] for details) - if the preference is turned on, all new names will be visible in the store you are logged into only. If it is turned off then all new names will be visible in all stores. 
-</WRAP> 
  
 If the first line of your import file contains column headers then check the **First line contains headers** checkbox. This tells mSupply to ignore the first line and start importing form the second line. If the first line of your import file contains column headers then check the **First line contains headers** checkbox. This tells mSupply to ignore the first line and start importing form the second line.
  • Last modified: 2022/01/28 19:16
  • by Mark Glover