Importing Data into a MainBoss Table

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.4.
For the latest version of this help file can be found here.

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

MainBoss can import XML data into a table, provided that the data has the correct format. Each table has its own required format for the records the table contains.

There are several ways to determine the required data format for records in a table:

• If you have a good understanding of XML, you can determine the proper format from the table's XML schema. See Obtaining an XML Schema from MainBoss for how to obtain an XML schema for a table.
• Export the current contents of the table into Microsoft Excel in order to see the required format. (If the table is currently empty, create a sample record so there's something to export). Then adjust your XML data so that it matches the format you see in Excel. For more on using Excel in this way, see Viewing Exported Data in Microsoft Excel.

Once you have put your XML data into the proper format, you can import it into MainBoss. To do so, go to the table viewer for the table, click the drop-down arrow on and click Import. MainBoss will open a standard Windows file dialog where you can specify the file that contains the data to be imported.

Important Note: The records in a MainBoss table must all have unique identifiers. For example, every item in the Items table must have a unique "Code"—no two items can have the same code. If you try to import an Items record with the same "Code" as an item that's already in the table, that record will not be imported. You will receive an error message saying that some of the data could not be imported.

Since the importing process requires data to be in exactly the correct format, it may take multiple attempts to get the process to work. This can cause difficulties. If you import a record that has incomplete or erroneous data, the import process will attempt to create a record anyway; then if you correct the data and try to import again, the process won't work because the existing record will have the same identifier as the record you're trying to import.

For this reason, we recommend trying imports with a test database rather than a real one. One way to do this is to backup your existing database, then using the backup to create a test database (as explained in Creating a New Maintenance Organization from a Backup File). Try the import process on the test database; if it doesn't work correctly, adjust the import data appropriately, then delete the test database and create a new one before trying the import again. Once the import process works correctly, you can do the import on your real database.

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