Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
import_and_export:export_to_dashboard [2021/04/28 10:03] – [16.18. Exporting to the dashboard] Gary Willetts | import_and_export:export_to_dashboard [2023/04/07 09:38] (current) – Gary Willetts | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
- | ====== | + | ====== |
- | <wrap info> | + | <wrap info> |
This information is for sending data from your mSupply database to the mSupply dashboard database. The dashboard has a separate Postgres database so that its use does not slow down or interfere with your use of mSupply. | This information is for sending data from your mSupply database to the mSupply dashboard database. The dashboard has a separate Postgres database so that its use does not slow down or interfere with your use of mSupply. | ||
Line 11: | Line 11: | ||
Click on the **Export Settings** tab and you will see this window: | Click on the **Export Settings** tab and you will see this window: | ||
- | {{ : | + | {{ : |
- | ===== Postgres server section | + | |
+ | |||
+ | ==== Postgres server section ==== | ||
In here you enter the details of the dashboard database server: | In here you enter the details of the dashboard database server: | ||
* **Server:** the URL or IP address of the dashboard database server | * **Server:** the URL or IP address of the dashboard database server | ||
Line 23: | Line 25: | ||
To make sure the details are correct and your copy of mSupply has access to the dashboard database, click on the **Test connection** button. A message will tell you whether the connection is successful or not. | To make sure the details are correct and your copy of mSupply has access to the dashboard database, click on the **Test connection** button. A message will tell you whether the connection is successful or not. | ||
- | Once the dashboard is enabled and the correct Postgres settings entered, there will be an automatic (scheduled) export every 24 hours. The next scheduled export is shown in the //Next scheduled export// field. | + | Once the dashboard is enabled and the correct Postgres settings entered, there will be an automatic (scheduled) export every 24 hours. The next scheduled export is shown in the //Next scheduled export// field. |
- | + | ||
- | To perform an immediate (manual) | + | |
- | * Check the boxes to choose the data you want to manually export to the dashboard (check the **All/ | ||
- | * Click the **Export** button | ||
- | * Enter the authorisation code | ||
- | * Click **OK** | ||
- | By default, **transaction** | + | ==== Export settings section ==== |
+ | This section enables you to manually export data to the dashboard apart from the scheduled dashboard export. | ||
+ | |||
+ | The time and date of the next scheduled export to the dashboard database are shown in the **Next scheduled export** field. | ||
+ | By default, all table data is exported incrementally — that is, only records | ||
+ | |||
+ | The **Run Next Scheduled Export Now** button gives you a way of exporting the data immediately, | ||
+ | |||
+ | The **Full export of Checked Tables** button gives you a way of re-exporting the specific table data from scratch | ||
+ | The table contains a list of all the database tables in mSupply that can be exported to the dashboard. Simply check the checkbox in the Export column to set that table to be exported to the dashboard when you click on The **Full export of Checked Tables** button. The **All/ | ||
+ | |||
+ | When you click on either of them you must enter your authorisation code before the export will be carried out. | ||
+ | |||
+ | Click on the **OK** button to save your changes and the **Cancel** button to cancel any changes you have made. | ||
- | In order to force a //full// export of transactions and/or requisitions, | ||
\\ | \\ |