CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Dupe handling of imported contributions
Pages: [1]

Author Topic: Dupe handling of imported contributions  (Read 577 times)

m.e.

  • I post frequently
  • ***
  • Posts: 157
  • Karma: 5
  • CiviCRM version: 4.0.9
  • CMS version: Drupal 7.9
Dupe handling of imported contributions
April 19, 2010, 02:37:08 pm
I need a way to run contribution data (in a .csv file) through the import process a second time without creating problems. I don't have available to me the file of rejected rows from the first import.

There are lots of options for handling dupes when contacts are imported, but for contributions there is only one choice:  Insert new contributions, or Update existing contributions. The explanation isn't clear about how dupes are handled. It reads

For each import, you can either INSERT new contribution records, or UPDATE existing records. You can not do both types of operations in a single import session. If you are UPDATING existing contributions, you will need to include a unique identifer to match to the existing records. This can be either the CiviCRM-assigned contribution ID, a unique Invoice ID, or a unique Transaction ID.

What happens if I choose "INSERT new contribution records" - and I import my file that's already been run through the import once? Will it assume all contributions are new, and end up creating duplicates for the ones that inserted the first time? (We don't want this.)

Or, what happens if I choose "UPDATE existing records," and it comes across contribution data that didn't import the first time, because of errors? Will those contribution records be skipped, since there is no existing record to update? (We don't want this either.)

Not sure how to proceed.

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Dupe handling of imported contributions
April 19, 2010, 03:40:38 pm

might be best to do this with dummy data either on your test server or on drupal.demo

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Dupe handling of imported contributions

This forum was archived on 2017-11-26.