Use this module wherever there are databases and you need to synchronize data in PANTHEON. The following are typical examples of this: company with divisions, where each division manages its transactions by itself (issuing and/or receiving invoices), and company with outsourced accounting, where the company manages its material operations and part of its financial operations (e.g. reconciling bank statements and posting subject accounts), but the lion's share of accounting is done for it by an outsourced accounting firm.
You can set in the window for importing/exporting precisely which data are to be transferred. The easiest yet less precise way to mark groups of data to be transferred is by checking the boxes of parent tree structure levels. For precision sake mark the selection on lower sublevels of the tree structure.
It hoolds good that by checking the parent group (e.g. Registers) you mark also all child items (e.g. Subjects registers) to the last level in line (e.g. Subjects, Subejct Types...).
A special characteristic by transferring transactions is that you can transfer each transaction separately. You can do this by checking document types used in transactions. Thus you can transfer only part of issued invoices (e.g. only those of one division).
Select a folder in the upper right sertion where you want to save, that is, where files used in transfer are to be located. Multiple transfer files are created when exporting that is why it is recommended that you ensure the transfer folder is empty before starting transfer.
| Date Changed |
- From - The start date of period when transfer started. Here the date of the last change made is taken into account. Only registers, documents and posts from this period are transferred. If you leave both date fields empty, all records are transferred.
- To - The end date of period when transfer started. Here the date of the last change made is taken into account.
|
| Import Type |
Determine the method used in importing data:
- Add - All records being imported are added to database.
- Add/change - Records already existing in the database are changed to having the status of the imported database. Those not existing will be added.
- Overwrite - Existing data are ovewrwritten. Before trying to import data, you have to confirm the operation (see Are you sure you want to overwrite existing data?).
|
| Status |
When exporting or importing it is displayed which table is actually being exported together with the progress bar. |
| Select directory for export/import |
Select the directory where you want to export data |
| Export |
The main database is exported to the directory for transferring, according to the selected criteria. Before trying to transfer, you have to confirm the operation (see Do you really want to export data to directory XXX).
After exporting, confirm that the operation completed successfully (see Data export complete!). |
| Import |
Data get imported from directory for transferring to the main database, according to the selected criteria. Before trying to transfer, you have to confirm the operation (see Do you really want to import data from directory XXX).
To export data the user is required to be assigned at least delete authorizations vtorizacijo for this functionality, otherwise import is not possible. The following error is returned (see You do not have the required authorization for this operation (xxx!).
If you marked file types to be imported which do not exist in the selected directory, an error list is displayed in the corresponding panel.
After importing, confirm that the operation completed successfully (see Data import complete!).
|
| Export to Database |
Here you can export data from one database and import them in other databases on the server at the same time. All databases on SQL server are checked by default, except for the original database, that is, the database from which you will draw original data.
Check all databases to which you want to export original data.
(see Export to Database).
|