We have a few custom fields on a handful of tables on our main office server. This causes some issues with using the Initialize Locations tool when setting up a new remote ticketing site. If I do a clean install of Apex on the new remote computer, and then try to Initialize Location from the files exported from the Office, the process breaks because of the custom columns.
A few things would be great: either the Initialize Location will prompt to add that column to the table and you define what type of column it is, or we can select columns to ignore when Initializing a Location.
We have also went the route of setting up a new location with a database backup from the Office. But then we have to go through and clear out all info that doesn't pertain to that location such as orders, tickets, scales, etc.