Used by DBSetup.exe
- This file is up until 8.1 used during the setup phase - it describes which prime data files are to be loaded into the newly created or upgraded database.
- Before 8.1 the file is created automatically during the setup process with links to our priming data. From 8.1 the priming data is part of our dictionary steps and the files are no longer used.
- You may manually edit this file to import additional data.
Before SuperOffice 8.1 and the continuous database this file would also have some sections that where always loaded after a fresh install, when creating a new database. These are not available from the dropdown menu inside DBSetup.exe to avoid running them unintentionally.
Some sections may be re-run to update or add additional data, and you may also create your own section to add your own import files.
Sections in this file
Init - Register - Upgrade are hidden from the Load or re-load initial data into a 8.1+ database dropdown in SuperOffice CRM Database Maintenance (DBsetup.exe) menu.
You may add your own import files and add a section inside brackets, like:
The prefix before =path.and.filename just needs to be unique.
UNIQEPREFIX_A=c:\program files (x86)\SuperOffice\SuperOffice Server\Init\MyImportFile.imp
Creating your own imp file
The impfile must match the table you want to import, starting with table name inside brackets. On the line below you may specify what you want to do with the current data in this table.
Truncate_table: This will delete all data in the table before it imports what is found in the impfile.
Truncate_BuiltIn and Set_BuiltIn: Special data marked as belonging to SuperOffice may be updated in later releases, this is done by us flagging our data with 1 inside the IsBuildIn field of the database table. Then we can later tell DBSetup that we only want to delete our data, but leave customer and partner rows behind in the database.
Note - if you set the primary key of a table to 0 then DBSetup with automatically set the primary key to the next available value. If you want to set it hard to a specific id, like we do in SORPublish table in the I_STDReportsNew.imp file.
If you need to reuse a privacy key later, in another table you may use variables like #MyTableEntry_id1, #MyTableEntry_id2 and so on. Then in a later table in the same imp-file, you may pick up the value and assign it as a foreignKey.