CiviCRM Community Forums (archive)

While running through my tried and true import procedure I ran into a problem that I'm almost positive was not there before.

Upon doing a membership import via CSV:

0. Set membership import type to organization, column headers, YYYYMMDD, fill.
1. First run validation turns up a few memberships with unhandled membership types (expected) and no other errors.
2. Upon "true import", all of the memberships fail with "Invalid Membership Status ID".

Here is an example:

"Line Number","Reason","Organization Name (match to contact)","Membership Status Id","Membership Type Id","Membership Start Date"

"2","Invalid Membership Status Id","Acme Inc","Current","Corporate","20110120"

Current Member Status is set to start at "start date" and end at "end date". When I enter 20110120 as the start date for this membership manually, the end date comes out to be Feb, 19th 2012, which means I shouldn't have any conflicts as far as the status rule is concerned...

So, heres the bit that sent me running to these forums:

The error in the import_errors CSV says : 
Invalid value for the field "Membership Status Id"  when I provide a member status such as "Current".
Invalid value for the field "Membership Status" when I provide a member status id such as "2".

It fails both ways, for every single record in the CSV, but the error message seems to change to complain about IDs if I provide names, and names if I provide ID's.

Any ideas on how to get to the bottom of this one?

I was able to recreate the error on sandbox.drupal.civicrm.org ( I don't know if this is 4.1 though).

I created a 3 row csv file attached and imported it using field mapping "testabc" which should still be on there. It matches to organization name, membership type (string), membership status (string), membership start date (yyyymmdd), and member since (yyyymmdd).

The returned import_errors.csv is also attached.

Definitely a regression bug. Thanks for catching and reporting.
http://issues.civicrm.org/jira/browse/CRM-9301

As noted in the issue report, "The existing membership import web test (WebTest_Import_MemberTest) should be extended to include passing in membership statuses prior to closing this issue." We need more folks to get involved in improving the test suites - so would be great if you could jump in and extend that test. Ping us on IRC if you need help getting started.