CiviCRM Community Forums (archive)

Can anyone provide an update on whether any progress has been on the way that CiviCRM can inappropriately assign more than one email/address/phone (in each of these categories) to "is_primary," either via the API or via the UI's import tool.

I found this from 2012: http://forum.civicrm.org/index.php?topic=22366.0

I ran into this problem this week when my client complained about wrong numbers showing up in the contribution aggregate report.

I did a data migration for the client 6 months ago. I had prepared, in part, by going to two data migration workshops at CiviCon Berkeley, had done previous (albeit simpler) data migrations into Civi, etc., read the help pages in the CiviBook, yet I still fell victim to it.

I wonder how many folks out there have run reports generated by Civi with broken calculations due to this bug, shrugged, and decided to move to another CRM.

And, of course, it's not exactly intuitive for people who don't understand SQL, relational databases, and Civi's architecture to realize that broken contribution aggregate calculations are caused by a data integrity problem related to emails, addresses, and/or phone numbers.

So I'm interested if anybody has any new news on this one.

It seems the least we can do is warn people on the import UI and give them a help page to consult before importing. It feels like importing is kind of an inherently problematic activity, yet most of my clients want to do it on their own... not migrate whole systems, but import contact lists etc.