Import UNC data over-writing previously imported data

When I import additional UNC data for Unconfined Compression Testing for a single boring, any previously entered or imported UC data in that same boring is deleted.

For example, I had previously imported and entered data for boring B-1 @8 and B-1 @12. When the remaining 2 unconfined compression tests were completed, I imported the data for the 2 addiitonal files only. When I went to enter the manually entered data, the data for the 1st 2 tests was gone! This only happens when importing data for the same boring number. When I imported data for borings B-2 and B-3, no data was deleted for B-1.

We have offices that do large quantities of UC testing and need to be able to import and complete tests on a daily basis. What can we do to correct data being deleted when additional data for the same boring is imported?

Thanks,

Judy Smith

  • Judy, are you using the File>Import/Export menu option, or another process to import?

    If you are importing using the File menu option, you probably just need to choose a different overwrite option in the dialog. The options are:

    • Never - Only add records whose Keys do not exist in the current database. Existing records will not be changed in any way. All options share this behavior for new records. This is the default, and it is the safest - but it will not allow you to add new data to a table for an existing borehole.

    • Empty fields - Writes data from the source only if the corresponding field in the target is empty. This will allow you to add new data to the UNCONF COMPR and UNC READINGS (UNC) tables for an existing borehole, but only if there is not already test data in the fields. That doesn't sound like it will work for this purpose either - except if you ONLY import the UNC data AND there is different information in the key fields than for the existing test records in the UNC tables, it will not replace the data in the existing records (fields not empty), but will replace the blank fields in a new record of that key.

      For the Lab Testing module, remember you need to make sure there is a matching Key in the LAB SPECIMEN table before you import just the UNC data.

    Other overwrite options are even more destructive:

    • Named fields - Writes data from a field named in the source wherever a matching field exists in the target, overwriting any contents of the target field. Note that if a field is blank in the source it will overwrite any contents in the target field and leave it blank.

    • Records - Erases each target record matched by a source record (same key) and writes the data from the source. Any records in the target that do not have corresponding records in the source will not be affected by the import.

    • Data sets - This does not wipe out all the data in the database. It replaces entire sets of data. The resulting data set will contain only data from the source file. A "Data Set" is defined by the Keyset of the parent table. For example in a table with the PointID, Depth Keyset a Data Set is all records with a particular PointID value, while for a PointID, Depth, Reading table a Data Set is all records that share a PointID and Depth. If a data set in the target file is not included in the source file the data will be left unchanged.

    For the File menu option import process, if you are still having problems after adjusting the overwrite choice, please call Bentley Technical Support.

    If you are using another process to import data, like a gINT Rule, the overwrite option may be coded into the rule's operation.



  • Thanks Pat!

    We using Data Acquisition systems for UU & UC data. We import the data from that equipment into gINT using Add-Ins, then choose "Import UNC", which imports the data from a .trx file. Pretty sure this utilizes a gINT Rule. Any ideas on how to solve the problem or create a work around?

  • I deleted my response because I now realize Pat had already posted more or less the exact same response prior to my post. For some reason I was not able to see her post so I thought mine was original.

  • Thanks for all the info, but when importing from add-ins, you don't get any overwrite options. You simply choose your files and they import, no other choices are given. In checking further, this is definitely part of the gINT rule code.

  • Judy,

    Sorry about my earlier redundant response.

    Anyway the import overwrite option can be changed easily from within the gINT Rules code although I suggest you let someone familiar with gINT Rules do that.

    Or, if the Add-In is importing from another gINT project, Excel or CSV file with a matcing database structure you could simply do the import manually (avoiding the Add-In) and select the overwrite options yourself.

    Johnny