Configuring names of previously hard-coded databases

For quite some time there have been three areas which entail mandatory database table names and field names, for different Axiell software to be able to deal with those database tables. A fourth is available from Collections 1.17 and a fifth from version 1.20:

•The reports.inf is the definition file for an optional database table for uploaded output format Word templates per user per data source.
•The missions.inf and request.inf database table definitions are used by the Missions dashboard in Collections.
•The audit.inf is an optional database table definition to log user activities.
•The contexthelp.inf (from Collections 1.17) is an optional database table definition containing all contextual help texts which originally are stored in .adh files.
•The maps.inf (supported in schemas.json from Collections 1.20) is the optional definition file for the maps database table in which GIS base maps and layers are stored.

For each, some or all fields have been hard-coded as well.

In rare cases, when installing or customizing an application when the database is still empty, there may be the wish to rename one or more of these .inf files. From Collections 1.15 you may use different names for these so-called schemas by specifying those in a special schemas.json file which should be stored in the application root folder (so not in c:\model\xplus for example, but in c:\model). A different name for an .inf or field should of course match an actually existing .inf or field definition. You should only change the values of the properties in the file, not add new properties or rename them. You can download schemas.json with the default settings here.

You don't need to use the file if you're happy with the current names of the above mentioned .inf's and its fields, and if the relevant tables already contain data you shouldn't do any renaming at all because changing the name of an .inf in Designer also requires you to rebuild the tables in the SQL database, as they should have the new name too, which is best only done if the relevant tables do not contain any data yet.