I'm having problems importing memberships with a custom field. I'm able to import a alphanumeric text field without an error, but a second custom field, set up as a checkbox, keeps being rejected.
The import CSV file originally had the option label in that field, but after changing this to the option value, the import is still rejected as invalid. What might I be missing here?
The original import error reads 'Invalid value for field(s) : Income; Income'
When I change the relevant fields to the correct value 'LowIncome' (having double checked that it's the value stored in the database), the import error reads:
'1' is not a valid option for field custom_33
Which is technically correct, but none of the fields in the imported file contain '1', so I don't know where it's getting this from!
Because there's only the one option, I'm pretty sure I can swap this out for a Yes/No field and try it again, but I'd rather pin down why this is happening - I also have some activities to import with multi-option checkboxes, and I'd rather know they'll work...
ETA: I've tried adding in another field, where the option label, value and name are all the same ('Test'), and importing it - It gets flagged in the same way - '1' is not a valid option for field custom_34
I also tried adding a yes/no field, and that imports okay, so I'm probably going to switch this particular field to a yes/no, but as I say, I'm concerned that it's going to reject other multichoice fields, and I'd still like to pin down the problem. I will try importing some of the activities, and update this when I know how it's behaving.
ETA2: This seems to be happening for any checkbox field, regardless of what the custom data set is used for, and isn't limited to fields with single checkboxes. I'm able to reproduce the problem in the master demo site, and importing from my new installation to the older version of CiviCRM also comes up with this error.
I've found a issue on the old bug tracker site that seems very similar in 4.7/4.7 - https://issues.civicrm.org/jira/browse/CRM-17493 - and although it's marked as fixed, it looks a little as though the fix was never implemented in 4.7 - the last git pull request is marked as closed with the note 'Unclear if a fix is required or not': https://issues.civicrm.org/jira/browse/CRM-17493 (but it's also not entirely equivalent to the problem I've been having)
Failing any further ideas as to what I might be doing wrong, I'll raise it as a bug.
