Reason column absent from Import Errors file Import_Errors.csv

tryer.csvImport_Errors.csv

Tested in 5.35.2 and 5.36.1. The Reason column is absent from the Import_Errors.csv file generated after a Contact import. I believe this is a regression. This column is where Civi would previously explain multiple duplicate contacts, invalid email formatting, invalid State/Province, etc.

changed title from Reason column absent from Import Errors file to Reason column absent from Import Errors file Import_Errors.csv

changed the description

Cross-referencing to a similar issue: https://civicrm.stackexchange.com/questions/39377/reason-column-missing-from-contact-import-error-list

I have a client using Drupal 7 + CiviCRM 5.35.2 reporting a similar issue.

@eileen, if I', not mistaken you worked on this part of the code in the last couple of months, does that ring a bell?

added comp:Import sig:unverified-bug labels

removed sig:unverified-bug label

added sig:bug label

I'm having trouble replicating this - the 2 csvs are from master just now (it has column headings & doesn't require any additional configuration) - I DID replicate the duplicates csv at the end missing a column header but it's unclear if that relates

tryer.csvImport_Errors__3_.csv

added needs:steps to replicate label

I'm able to reproduce it like so:

1. Create two contacts in civi that match one in the import file, so that you already have a duplicate contact before the import.
2. Import tryer.csv, and choose to Update contacts, with a dedupe rule that's going to match.
3. At the end you get the errors file with a missing reason column.

Thank you @DaveD you are correct. The import Reason column does not populate when the Reason is multiple duplicate contacts in CiviCRM. To elaborate on your reproduction.

1. Contact name exists "John Smith john@smith.com"
2. Contact name exists "Jonathan Smith john@smith.com"
3. CSV file contains "john@smith.com"
4. Import using "Email only" duplicate match rule.

It is unfortunate yet expected that duplicate contacts will exist and this should not preclude getting a Reason for the error.

mentioned in commit ca275c67

Encountered this issue on 5.35.2, matching on Name + Email. In line with DaveD & Stoob's comments, it occurs when there are multiple existing contacts that match an import row. As there are steps to replicate now, can we remove label "needs:steps to replicate" ?

removed needs:steps to replicate label

Can replicate here, the issue is the dedupe rule we are using found multiple contacts that match the rule. Instead of telling us that is the reason, it just does the same as the example provided.

In 5.51 there is a significant code cleanup - I don't know if it fixes this (or even makes it worse) but if anyone has time to test the rc it would be much appreciated

Hi @eileen, thanks for following up on this. I just replicated the problem on a local dev instance on 5.47.4, then grabbed civicrm-5.51.beta1-drupal-202206100742.tar.gz and ran the upgrade through the UI. However I got a db error:

DB Error: no such field
UPDATE civicrm_queue SET status = NULL WHERE name = 'CRM_Upgrade' [nativecode=1054 ** Unknown column 'status' in 'field list']

Looks like this query was added recently to CRM_Queue_Runner::runAllViaWeb(), it's not in 5.49.4 for example. I re-tried a couple of times, making sure I had cleared caches / templates_c - same error. So, I'd better file an issue for that! [Edit: done, #3507 (closed)]

I then tried drush cvupdb and that succeeded.

Re-tested the import and this time the Import_Errors file correctly included the reason. I'm attaching the Import_Errors files from 5.47.4 & 5.51.beta1 .

Import_Errors-5.47.4.csv Import_Errors-5.51.beta1.csv

mentioned in issue #3507 (closed)

thanks for testing this @davej - I guess we can close this one - I have pinged @totten re the upgrade issue

closed

changed milestone to %5.51.0