- On a US demo database
[STEPS TO PREPARE]
1. File >> Import and Export >> Export Contact Records
2. Export to a new file + CSV file
3. All Contact records + Primary
4. Map Accountno and Company
5. Provide a destination path and filename
6. Export the data
7. Open the exported data file and add at the bottom of further row for example "blah blah", "GoldMine Technical Support" and save again
[STEPS TO REPRODUCE]
1. File >> Import and Export >> Import Contact Records
2. Import to a new file + CSV file
3. Select the file created in the steps to prepare
4. Map Label001 to Accountno and Label002 to Company
5. Button Profile Options
6. Select AccountNo in the Select the match-field to be used
7. Select Do not import the record in the Record Matching Options dialog
8. Perform the import
9. Review the Process Monitor
The Process Monitor shows during the Import Process how many records currently where added, updated or skipped
At the end of the Import Process a summary is provided with the final information how many records have been added, updated or skipped
- Is there anyhow a chance to see which records are skipped? Is there more detailed logging for?
- No there is no such possibility from within GoldMine. The only possibility when or where you could see it from within GoldMine would be when using the Ask Me what to do setting in the Import profile.
- In this case the user is prompted when GoldMine identifies a duplicate and you get the information about
a. the Match field (you set in the Import profile)
b. the current value
c. the matching record (RECID) from within GoldMine
d. the import file record number (usually row information (please keep in mind you may have set that your import file as a header row)
- This process might be valuable when you expect not a lot of duplicates appearing in the import file but might be inconvenient if there are a lot of duplicates.
- There might be alternatives depending on which business workflows are necessary or in place, for example export the set profile verification match field and compare externally already prior an import or also import into a secondary database and then via SQL queries try to identify duplicates, or even import duplicates into the current contact set and then via the Merge/Purge wizard try to identify duplicates (which will not be possible when the match field would be for example ACCOUNTNO as this information will not be imported into the ACCOUNTNO field but instead a new ACCOUNTNO will then be generated).
- Another maybe requiring much more effort but might be considered and then optimized would be to run a SQL Trace during the import and verify which records did not trigger an Insert Statement into the CONTACT1 table.