Export
LIMBAS offers three variants for exporting data, which can be selected using the tabs: Partial Export Complete Export Project Export
With the ‘Partial Export’ the data can be stored in Excel, Text or LIMBAS Format. For ‘Complete Export‘ and ‘Project Export’ only the LIMBAS Format is available.
The LIMBAS format consists of one or more Table Definition Files, export.conf (for the ‘Project Export ‘in different subdirectories) and one data file per each table. All files generated when exporting are compressed in one file. If this file is selected for an Import, LIMBAS restores all field types, dependencies and links without any user interactions.
Partial Export
With Partial Export only the selected tables are exported. To export only certain records from a table, a SQL-compliant filter can be applied. The tables to be exported are selected via a ‘Multiple Select’ field.
When the export process is completed, the resulting export file name appears in a success message with the number of exported tables and records, as well as the file name for each exported table. The associated export file can be viewed by clicking on the file name. The exported files are also to be found temporarily in the directory./dependent/USER/ < user id > / temp.
If multiple tables are exported at the same time, the exported files can be grouped together by mouse click on ‘Files summarize!’ in the compressed file ‘export_dump.tar.gz’.
Complete Export
For the ‘Complete export’ all tables with all records are exported.
When the export process is completed, a success message appears with the number of exported tables and records, as well as the name of the generated export file which is filed under ./dependent/BACKUP . By clicking on the file name it can be viewed.
Project Export
When exporting a project, selected tables with all dependencies, e.g. linked tables, are exported.
When the export process is completed, the resulting export file name appears. By clicking on the file name it can be viewed. The file is also temporarily stored in the directory ./dependent/USER/ <user id>/temp.
The project export of forms and reports in the LIMBAS format is currently being carried out. prepared.
Sync Export
The sync export does not export data records, but only the structure or state of the Limbas system.
The individual modules to be exported can be selected with the checkboxes of the first two columns. After an import, System Functions can be selected in the third column. You can additionally set whether source code and Extensions should be copied in the last column, and whether an extension function should be executed after the import.
The button export config exports the configuration above into the PHP file dependent/TEMP/conf/autosync.conf.php, which can be integrated by several own extensions.
The export is started via the button export archive. The generated export file can then be downloaded.
On the other hand, if you do not want to export to a file, but instead transfer the structure of the selected modules directly to a Limbas target system, you can enter the URL (…/dependent/) and the access data of a Limbas account in the lower area. With start remote precheck a comparison of the structure with the target system is created and displayed. If this was successful, the transmission can be confirmed by means of start remote export.
