The exact error came about due to the inclusion of the Net Present Value field in the gift mapping. This field should not be mapped directly as it causes the error. The wording of the error may be something similar to the following:


General ODBC Error: [Microsoft][ODBC SQL Server Driver][SQL Server]The column name 'PlannedGiftID' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name 'PlannedGiftID' may appear twice in the view definition.

Native error:264


This was fixed in version 2.6 of Importacular.