Exporting and Importing Customizations

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.4.
This help file does not exist in MainBoss 4.2.4, but the index for that version can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

MainBoss users can customize table viewers, editors and reports by selecting a set of options and giving a name to the result. For example, if a user frequently wants an inventory report with a certain set of grouping and sorting options, with specific pieces of information included in the report, the user can set up all the options, then give the result a name like My Standard Inventory Report.

Actions within mbutility make it possible to transfer customizations from one user to another. For example, if user A comes up with a useful set of customizations, mbutility makes it easy for A to send the customizations to user B. This can also be done with operations inside MainBoss itself, but mbutility makes it possible to perform the transfer directly from command lines.

The ExportCustomization verb exports all of a user's customizations into a file. It must be executed while logged in to Windows under the user's login name. The format of the command is

mbutility ExportCustomization option option option

where the options are:

The name of a file where the customizations should be stored.
The name of the maintenance organization (associated with your MainBoss database). This name is case-insensitive; for example, MainBoss is the same as mainboss.
The name of the server that holds the MainBoss database.
The name of the MainBoss database.

The ImportCustomization verb imports a set of customizations that were exported with ExportCustomization. Typically, you would login to a different Windows login name and import customizations created by a different user. However, it may also be useful to import customizations that you yourself exported. For example, if you want to experiment with new customizations, you might use ExportCustomization first to save your existing customizations; then, if you don't like your new customizations, you can use ImportCustomization to import all your old customizations.

ImportCustomization takes the same options as ExportCustomization. In this case, however, /Customizations:file is used as input rather than output.

< Previous section  |  Table of Contents  |  Index  |  Next section >