Details
Description
Noted while answering http://civicrm.stackexchange.com/questions/14875/can-you-share-an-example-of-a-complex-csv-file-for-import (and generally when grabbing test data).
It's really nice that CiviCRM picks up on column headers on import if they match what CiviCRM exports or expects. (I think there are some synonyms so it's not just the export headers?) However, the UX isn't completely watertight - you do need to tweak some exported columns.
To reproduce:
- Search for "All individual contacts" (test site is fine)
- All contacts, Action=Export contacts
- Core/basic contact fields (forget the label here) (PD label is Export PRIMARY fields)
- Save CSV
- Go to import contacts
- Import the CSV again, with first row has column headers
- Observe that columns are nicely selected, continue
- Import fails with 100% errors because "Invalid value for field(s): Addressee must be one of the configured format options"
IMO it would be better to not autoselect those addressee columns.
Do the input and output formats differ?