The Sage ACT! import log has been improved to give counts of successful records imported and details of what records failed. This is now accessible and can be viewed at the final stage of the Import Wizard:
To view the log, click the link for View import log link on the Import Complete screen of the import wizard.
This log will display a count of records that were successfully imported by type. If there are any errors during the import of data, the log will show details about the error. The log is for all import source types, database to database imports, .csv/.txt, and Microsoft® Excel® imports. This will help in troubleshooting issues related to data migration.
Below are some examples of exceptions you may see in the log if any errors were encountered during the import.
Sample Exception Message 1:
An Activity failed to merge.
Activity: Sales Training
Exception message: Error Inserting Activity: Violation of PRIMARY KEY constraint 'TBL_ACTIVITY_PK'. Cannot insert duplicate key in object 'dbo.TBL_ACTIVITY'.
The statement has been terminated.
Potential causes:
- The activity may already be in the Sage ACT! database you're importing to.
- The activity may be shared amongst multiple main entities (Contact, Group, Company, and/or Opportunity) in your Sage ACT! database. For example: User A has an activity associated with a Company and a Contact. After importing the Contact, this exception is displayed when importing the Company.
- The activity is a recurring activity.
- The activity was erased and no longer displayed to the user, but not removed completely from the database.
Sample Exception Message 2:
A Note failed to merge.
Note: Interested in Sage ACT! Connect. Need to follow up.
Exception message: Error Inserting Note: Violation of PRIMARY KEY constraint 'TBL_NOTE_PK'. Cannot insert duplicate key in object 'dbo.TBL_NOTE'.
The statement has been terminated.
Potential causes:
- The Note may already be in the Sage ACT! database you're importing to.
- The Note may be shared amongst multiple main entities (Contact, Group, Company, and/or Opportunity) in your Sage ACT! database. For example: User A has a note associated with a Company and a Contact. After importing the Contact, this exception is displayed when importing the Company.
Sample Exception Message 3:
A History failed to merge.
Note: Call Bob Smith
Exception message: Error Inserting History: Violation of PRIMARY KEY constraint 'TBL_HISTORY_PK'. Cannot insert duplicate key in object 'dbo.TBL_HISTORY'.
The statement has been terminated.
Potential causes:
- The History may already be in the Sage ACT! database you're importing to.
- The History may be shared amongst multiple main entities (Contact, Group, Company, and/or Opportunity) in your Sage ACT! database. For example: User A has a history associated with a Company and a Contact. After importing the Contact, this exception is displayed when importing the Company.
If you would like to view the XML import log files, you can find them in one of the following locations on your computer, depending on your operating system:
- Windows® XP/Windows Server® 2003: C:\Documents and Settings\*username*\Application Data\Act\Act Data
- Windows Vista®/Windows 7/Windows Server 2008: : C:\Users\*username*\AppData\Roaming\Act\Act Data
There are two files: IMPORT_EXPORT_LOG.xml for successful imports, and IMPORT_EXPORT_FAILLOG.xml for imports with errors. To view these logs, you can open them in a text editor like Notepad or with your Internet browser.