What if I'm using a gINT SQL Server database?

If your data is stored in a gINT SQL Server Enterprise Database, we've put together an example "Multiple Downsize" Library File with a gINT Rule Add-in that demonstrates how to bulk "downsize" (export) projects to individual GPJ Project Files. This will then allow you to import them into OpenGround with the Batch Import Tool.

The Multiple Downsize Library File can be downloaded here.

Before you begin

You will need a gINT Data Template (.gdt) that models your gINT SQL Server database structure. If you don't have one available, create one by doing the following:

1. Open your gINT Enterprise Database (Enterprise>Open Enterprise Database).
2. Manually downsize any project (Enterprise>Downsize Project).
3. Open the downsized project file (File>Open Project).
4. Create the Data Template. (From INPUT, Tools>Make Data Template).

Instructions

1. Open the Multiple Downsize library (File>Change Library).
2. Open your gINT Enterprise Database from which you want to downsize projects (Enterprise>Open Enterprise Database).
3. Go to Add-Ins>Downsize Multiple Projects
4. Follow the prompts:
   1. Select the projects you want to downsize. Select none for all.
   2. Select your gINT Data Template (see Before you begin above).
   3. Select a folder where you want the results to be saved. A local folder is recommended.
   4. You will get confirmation of the results folder location. Note the date and time is appended to the folder name to avoid duplicate folder names and for tracking purposes. Click OK.
   5. The downsize operation will start automatically and you will see the tasks running. It may take a while so be patient. You will get a Summary Log when everything is complete.
5. Review the Summary Log for errors. "Save As" to see the entire log.(Note: You can ignore the Warnings regarding "Data not found in required lookup lists…". To suppress these messages, merge the gINT Rules into your organization's library using Utilities>Lib Merge/Copy. Search gINT Help for "Lib Merge/Copy" for more info.)
6. Go to the results folder. You will see a subfolder with the downsized GPJ's. You will also see gINT Script file (.gsc) and a subfolder with CSV's used by the gINT Rule. You can ignore/delete these, but they may be useful if any troubleshooting is required.

Additional Notes

1. The gINT Rule is designed for using Windows authentication to access the SQL database. If you are using SQL Server authentication, it might need to be modified.
2. It's recommend running the tool on a local backup of your database and to avoid running this tool over a network or on a production database.
3. All data within a single gINT Enterprise Database will have the same Data Template. However, you may still need to consider other factors when organizing your Submissions, such as grouping your GPJ's by coordinate system or units. You can do this using the Batch Import Helper library, or potentially by modifying the Downsize Multiple Projects Add-in to filter/group the downsized GPJ's accordingly.
4. If you're using a gINT Enterprise Database, there may be other approaches for migrating your gINT data, such as with the OpenGround API, but this article is intended to provide a solution if you'd like to use the Batch Import Tool.
5. The Downsize Multiple Projects Add-in will only export data from the gINT data tables to the "downsized" GPJ's. It will not export Site Maps or Surfaces, for example.
6. Like all gINT Rules Samples, the Batch Import Helper library is provided as an example, free of charge and as-is. Bentley Systems makes no claim or warranty as to the accuracy of the example. It is the responsibility of the user to ensure that the code performs as it should. Comments, suggestions, and error reports are appreciated.