I am working with a template provided by another person. I create a new project using that template. All looks empty and pretty standard. I do an import of my source data using the "Named Fields" option, and get the following log with the indicated Warnings
95 Records imported.
PROJECT: 1 records OKPOINT: 1 records OKLAB SPECIMEN: 10 records OKATTERBERG: 4 records OKSIEVE: 3 records OKWC DENSITY: 10 records OKATTB READINGS: 12 records OKSV READINGS: 54 records OK
Warnings:
The following tables allow duplicate keys: ATTERBERG,SIEVE,WC DENSITY.It is not possible to update specific records in these tables.gINT has imported data only to those data sets that were initially empty.If you wish to replace existing data use the 'Overwrite Data Sets' option for these tables.Existing datasets will also be overwritten if the 'Overwrite Records' option is chosen for the entire import.
The following tables have hidden counters: ATTB READINGS.It is not possible to update specific records in these tables.gINT has imported data only to those data sets that were initially empty.If you wish to replace existing data use the 'Overwrite Data Sets' option for these tables.Existing datasets will also be overwritten if the 'Overwrite Records' option is chosen for the entire import.
I look over the data and it is there and visually looks fine.
Now, at times I get into a situation where I need to re-import the source because some values have changed (eg. change in a tare weight)
I do the import and now get the same message, BUT as noted in the error message " ...... gINT has imported data only to those data sets that were initially empty." The bad data has not been replaced by the good data in my revised source file.I have run into this before on other tempates, and I have used the Overwrite Data Sets option as indicated in the Warning Message. When I do this, all is cleared out and the entire source is brought into the target. I do NOT get the "The following tables have hidden counters: " message either.
On this particular project, however, created with the template I mentioned above, if do the import, using the Overwrite Option of "Data Sets, I get a slew of these messages.
WC DENSITY Table:The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again
I do some more testing, and find that even if I delete all the boreholes, and have what looks like a clean blank file, and do an Overwrite Option of Data Sets again, I get the same slew of messages. It is like it is NOT clearing everything out.
Again, with previous templates using the Overwrite Data Sets, things "look like" it has cleaned out all the data, and prevented that "The following tables have hidden counters: ATTB READINGS. message on a newly created project, and also prevented either message if used on an existing project that had data in it already. I have see an earlier response here that seems to be in the same ball field and may be spot on, but my ignorance is keeping me from discerning the "fix". What I do discern form the post is that all the "Data" is NOT cleared out, with an Overwrite Data Sets option, and that although the user interface is blank, there is still some hidden structural placeholders attached to the file (Counters/keysets, etc??)https://communities.bentley.com/products/geotechnical1/f/geotechnical-forum/71792/import-unc-data-over-writing-previously-imported-data/189945#189945What I Want:
a) to understand better what is going on.
b) to get things set up so that if I revise the underlying data in the source, I can import it using the Named Fields option, and it will actually bring in the Named field source data, even into the non-empty fields, thus updating their data.Ideas??
2022_11_10 EDIT/SUPPLEMENT
I did a database compare. Could the "GintVersion" difference as shown below in the "Database Property Differences:" have something to do with it??
DB #1 is the DB that seems to give the problem with the slew of messages on the imports
DB #2 is the DB that does not throw the slew of messages on the imports Property[GintVersion] 1: [4.15.002] 2: [8.30.004]