import_and_export:export_locations

Differences

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

Link to this comparison view

Next revision
Previous revision
import_and_export:export_locations [2020/05/14 13:43] – created Gary Willettsimport_and_export:export_locations [2023/01/24 15:57] (current) Gary Willetts
Line 1: Line 1:
-{{indexmenu_n>95}} +{{indexmenu_n>110}} 
-====== 16.10. Exporting locations ======+====== 17.14. Exporting locations ======
 This function allows you to export all of the locations **in the current store** to a text file that can be imported into mSupply. This is very useful if, for example, you want to create the same set of locations in another store or datafile. This function allows you to export all of the locations **in the current store** to a text file that can be imported into mSupply. This is very useful if, for example, you want to create the same set of locations in another store or datafile.
  
Line 7: Line 7:
 If there are no locations in the current store, you will be told there is nothing to export and the process will be cancelled. If there are no locations in the current store, you will be told there is nothing to export and the process will be cancelled.
  
 +The format of the file created can be used with the Location import feature and is described on that page ([[import_and_export:importing_locations|]]).
 \\ \\
 \\ \\
-|  //  Previous:  **[[import_and_export:importing_a_supplier_invoice]]** | | Next: **[[import_and_export:export_names]]** //  |+|  //  Previous:  **[[import_and_export:export_items|]]** | | Next: **[[import_and_export:export_names]]** //  |
 ---- struct data ---- ---- struct data ----
 +pagestatus.status    : 
 ---- ----
  
  • Last modified: 2020/05/14 13:43
  • by Gary Willetts