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 Import (Moderator: Yashodha Chaku) »
  • Import Member Bug and CiviCRM 2.0
Pages: [1]

Author Topic: Import Member Bug and CiviCRM 2.0  (Read 1355 times)

farmrchrys

  • I post occasionally
  • **
  • Posts: 92
  • Karma: 2
    • Spokane Moves to Amend the Constitution (under development)
  • CiviCRM version: CiviCRM 4.4.6
  • CMS version: Drupal 7.31
  • MySQL version: MySQL 5.5.37
  • PHP version: PHP 5.3.28
Import Member Bug and CiviCRM 2.0
January 25, 2009, 08:47:30 pm
Hello,

I upgraded from CiviCRM 1.9/Drupal 5.7 to CiviCRM 2.0/Drupal5.12 in order to get past the broken price set feature in 1.9. I also had to re-import all my contact data as, despite the best attempts of the upgrade script, the database schema of 2.0 being so different from 1.9 the data did not transfer over correctly. So, I deleted all my contact info and now I am in the middle of the re-import. I completed importing the contact data and have moved on to import the membership data. Here's where I hit a snag.


My import file has a field with a unique number for each record and I've used this as the external identifier when importing the contacts. I have set CiviCRM's contact matching to match using the external identifier only. When importing membership data I get the error message "Missing required contact matching field: Contact ID" and I've read both
http://forum.civicrm.org/index.php/topic,4056.0.html
and
http://issues.civicrm.org/jira/browse/CRM-3038?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel.

Here's my question: Do I understand correctly that there is no fix for this bug in 2.0 but that it is fixed in 2.1 and that to upgrade to 2.1 I will also need to upgrade to Drupal 6?

Thanks,

Chrys

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: Import Member Bug and CiviCRM 2.0
January 26, 2009, 07:55:59 am
Quote from: farmrchrys on January 25, 2009, 08:47:30 pm
Here's my question: Do I understand correctly that there is no fix for this bug in 2.0 but that it is fixed in 2.1 and that to upgrade to 2.1 I will also need to upgrade to Drupal 6?

yes

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 Import (Moderator: Yashodha Chaku) »
  • Import Member Bug and CiviCRM 2.0

This forum was archived on 2017-11-26.