Users cannot successfully import files that contain both new constituents and existing constituents (when the user is using finder numbers to link the revenue records to existing constituents).

When importing revenue records using a header file based on a enhanced revenue batch, users cannot successfully import files that contain both new constituents and existing constituents ( when the user is using finder numbers to link the revenue records to existing constituents).

To provide contrast, if you use lookup ID to associate the revenue record with the existing constituent instead of finder number, an exception message is not displayed and both records will import successfully.

Download and install the latest patch, which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 

Workaround:

If using finder numbers to associate revenue records with existing constituents when importing, do not place these revenue records in the same import file as new constituents.

Environment

 2.9.1001 patch 95
 2.94.1524, patch 14 ; 2.9.1001, patch 114 ; 2.93.2034, patch 32 ; 2.91.1535, patch 76

Was this article helpful?