CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • 1.7 Import with Update/Fill Errors...bugs?
Pages: [1]

Author Topic: 1.7 Import with Update/Fill Errors...bugs?  (Read 1596 times)

emilyf

  • Ask me questions
  • ****
  • Posts: 696
  • Karma: 54
  • CiviCRM version: 2.x - 4.x
  • CMS version: Drupal 5, 6, 7
1.7 Import with Update/Fill Errors...bugs?
June 01, 2007, 09:06:31 am
Hi,

The error I'm getting is kind of similar to this topic http://forum.civicrm.org/index.php/topic,139.0.html but it differs enough that I am starting a new post.

I am running CiviCRM 1.7.9379. I am doing imports, so I have a csv file with
177 records in in. The way that the import directions are worded, it appears
that with duplicate checking I can also have new contacts that don't already
exist be in my import file when I am doing an update or fill. At least
that's how I'm reading it.

I have tried using update and fill, and both of these options preview
everything properly. They acknowledge there are 177 rows, and according to
the final box, they import 177 rows successfully. However, the last 4 rows
are not coming in. Originally I had a file with 173 rows, and the 173rd row
did not come in. So I added a few more rows to see if that made a
difference. It didn't. Then I copied everything into a completely new file,
but that didn't make a difference. So neither Update or Fill will bring in
these last 4 rows.

Here's what will work:
If I cut just the last 4 rows and paste them into a new file, update and
fill work. Or if I use Skip Duplicates, then the original 177-row file
works.

The issue is, I don't know what OTHER rows update/fill ignored; I just
happened to check on the last row. But the first time I tried doing a Skip
option instead, it supposedly put 29 new rows into the DB of the same 177
that I was trying with Update/Fill. But I can't say this is accurate either
because the number it skipped added to the 29 it said it imported came out
to be close to 200 rows, so it must have included some blank rows somewhere.
But if the insert number is accurate, it sounds like 29 records were not
seen with update/fill. Perhaps these 29 records didn't already exist in the
db, and update/fill only imports duplicates. But if this is the case, I
would think that the valid rows that it puts out at the end should be
accurate and tell me that a certain number of rows were skipped.

So the issues:
Update and Fill not importing all records
Reporting tools seem to be including empty rows at bottom of file sometimes

Anyone else having this issue? Shall I report as a bug? Recreating on demo
at present seems difficult because there are a lot of variables, and
currently my data is real data. Insight is appreciated.

idealso

  • Guest
Re: 1.7 Import with Update/Fill Errors...bugs?
June 03, 2007, 02:14:23 pm
My first thought for this is that you're running into a memory limit or execution time limit.  The import has a javascript status bar, so if you hit one of these limits, it just stops.  You don't get the white screen of death, because there's already a page displayed.

If this is the case, you should see something in your webserver error logs.  Also, try increasing these values and see how far your script gets.  Use phpinfo() to confirm that the new settings are seen.

emilyf

  • Ask me questions
  • ****
  • Posts: 696
  • Karma: 54
  • CiviCRM version: 2.x - 4.x
  • CMS version: Drupal 5, 6, 7
Re: 1.7 Import with Update/Fill Errors...bugs?
June 04, 2007, 04:55:59 am
As I mentioned before, everything appears absolutely normal with this. The progress bar goes to 100%, and the final import screen says that 177 rows were imported successfully. There is nothing in my logs; all appears fine, and my memory limit is already at 64M. Had I exhausted that, I should have seen errors in my logs.

Given these circumstances, I think it is a glitch/bug in CiviCRM. I welcome other ideas/comments...otherwise I will post this as a bug.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: 1.7 Import with Update/Fill Errors...bugs?
June 04, 2007, 10:41:45 am
Emily - It would be most helpful if you can recreate this for us on demo with same de-sensitized version of your data. If we have a sample import file that recreates this and an exact description of the the import settings/mappings you're using - we should be able to nail down th problem nicely. Otherwise, it will be difficult / impossible to track down given the number of possible variables.

I'm a bit suspicious that the mix of NEW contact records and MATCHING records to be updated is causing an issue - so you might try a simple case of that first. Thx!
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • 1.7 Import with Update/Fill Errors...bugs?

This forum was archived on 2017-11-26.