<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>How to Export multiple projects to AGS from HoleBASE 3.1 to import to HBSI</title><link>https://communities.bentley.com/products/geotechnical1/w/wiki/49874/how-to-export-multiple-projects-to-ags-from-holebase-3-1-to-import-to-hbsi</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>How to Export multiple projects to AGS from HoleBASE 3.1 to import to HBSI</title><link>https://communities.bentley.com/products/geotechnical1/w/wiki/49874/how-to-export-multiple-projects-to-ags-from-holebase-3-1-to-import-to-hbsi</link><pubDate>Tue, 09 Jun 2020 23:09:44 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:4ee4af8d-7b63-4d3c-b46e-ca5fd8d734de</guid><dc:creator>wiki.author</dc:creator><comments>https://communities.bentley.com/products/geotechnical1/w/wiki/49874/how-to-export-multiple-projects-to-ags-from-holebase-3-1-to-import-to-hbsi#comments</comments><description>Current Revision posted to gINT | Keynetix Wiki by wiki.author on 6/9/2020 11:09:44 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
	&lt;tbody&gt;
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;Keynetix&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;1.0&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;		
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;Assist&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;		
	&lt;/tbody&gt;
&lt;/table&gt; &lt;br /&gt; 
  
    &lt;p&gt;&lt;/p&gt;
  
  
    &lt;h1&gt;How to Export multiple projects to AGS from HoleBASE 3.1 to import to HBSI&lt;/h1&gt;
    &lt;h2&gt;Explanation&lt;/h2&gt;
    &lt;p&gt;Build 3.1.426.68 of HoleBASE includes a new feature which will allow users to perform a bulk AGS export, issuing data from multiple projects.  Although this is likely to have a general application it is intended to assist users who are seeking to migrate over to HoleBASE SI and require tools to move the data.&lt;/p&gt;
    &lt;h2&gt;Process&lt;/h2&gt;
    &lt;p&gt;To use the feature follow the steps below:&lt;/p&gt;
    &lt;ul&gt;
      &lt;li&gt;Login to HoleBASE 3.1 under a &amp;#39;System Manager&amp;#39; account (if user accounts have been activated) and ensure no projects are open.&lt;/li&gt;
      &lt;li&gt;Go to System | Bulk AGS Exporter&lt;/li&gt;
      &lt;li&gt;Highlight the projects required for export (click to select, click+Ctrl to add to a selection, click+Shift for a multiple selection).  Note the buttons to Select All and Deselect All if required.&lt;/li&gt;
      &lt;li&gt;Click the Create AGS Files... and specify the folder within which the exported data will be created.&lt;/li&gt;
      &lt;li&gt;HoleBASE 3.1 will now perform the export, creating a seperate file for each project.  These will use the PROJ_ID for the file name.  A log file is also created which projects from the selection have (and have not) been exported successfully.  This file, called Bulk_AGS_Record.Log, can be found alongside the new AGS files.&lt;/li&gt;
    &lt;/ul&gt;
    &lt;p&gt;A summary message is presented on completion reporting the result of the export&lt;/p&gt;
    &lt;h2&gt;Further Information&lt;/h2&gt;
    &lt;p&gt;Note there are occasions when the routine may not be able to complete the export, these being reflect both in the message above and the log file.  This is typically the case when changes have been made to the system database which need to be applied to the project in question.  As such changes are applied when the project is opened it should be possible to perform the export manually.  That is, open the project and perform an individual AGS export in the usual manner.&lt;/p&gt;
    &lt;p&gt;The AGS Bulk Exporter does include a couple of additional features.  The order in which the projects are listed can be adjusted using the Sort Order drop down list.  Also, there is a checkbox to Remove Selected Projects after Export.  This will remove projects from the list of those available under HoleBASE3.1 once AGS has been exported successfully.  This can be useful when encouraging users to use the new HoleBASE SI system and helps to avoid two versions of the data to be maintained (although both systems can be run alongside one another; ensure this checkbox is unticked if this is likely to be the case on an individual project).  Note that this option will simply remove the project from the list of those available under HoleBASE 3.1; the project database itself will remain unchanged and can be connected once more under the Project Manager.&lt;/p&gt;
    &lt;p&gt;This feature has been developed primarily with a view to allow users migrating to HoleBASE SI to transfer their data.  As such, certain assumptions have been made about the requirements for the data - the output is similar to an &amp;#39;archive&amp;#39; export from File | AGS Export.  The file produced will be an AGS3.1 file and include all tables and fields from the project, including those which are user defined.&lt;/p&gt;
    &lt;p&gt;&lt;/p&gt;
  
&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Migrated&lt;/div&gt;
</description></item></channel></rss>