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 Import (Moderator: Yashodha Chaku) »
  • Import errors capped at 250! PLEASE HELP -RESOLVED-
Pages: [1]

Author Topic: Import errors capped at 250! PLEASE HELP -RESOLVED-  (Read 895 times)

Chelcone

  • I post occasionally
  • **
  • Posts: 82
  • Karma: 1
  • CiviCRM version: 3.4.0
  • CMS version: Drupal 6.*
  • MySQL version: MySQL 5.*
Import errors capped at 250! PLEASE HELP -RESOLVED-
March 31, 2011, 03:32:47 am
Hi Everyone

I am doing a an import of 4500 donations into the CiviContribute module and i am getting a lot of errors due to the fact i have no way of knowing if the donations are organisations or individuals so im having to use the error checks to filter the data. On the last import i did it came out at 2800 errors and the spreadsheet with the import errors only contained 250 records. This made me check the donor imports that i did and i have the same problem, when I imported 20,000 donors into the system i got 1,200 errors and i can only see 250 of them.

Please can somone tell me how to fix this?!

Chelcone
« Last Edit: April 01, 2011, 04:43:08 am by Chelcone »

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
Re: Import errors capped at 250! PLEASE HELP
March 31, 2011, 04:22:42 am
Hi,

Not sure about the limit, first time I hear about it, but I don't have that many errors.

When you are dealing with big numbers of contacts/donations, I suggest to develop a simple custom function to import that can do more than the default import (for instance checking automatically if it's an individual or an org that did the donation and process accordingly automatically).

With the API v3, that's even easier and doing it inhouse or hiring someone to do it shouldn't be too expensive.

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Chelcone

  • I post occasionally
  • **
  • Posts: 82
  • Karma: 1
  • CiviCRM version: 3.4.0
  • CMS version: Drupal 6.*
  • MySQL version: MySQL 5.*
Re: Import errors capped at 250! PLEASE HELP
March 31, 2011, 04:37:35 am
Thanks for  the reply. The built in import tool is fine, it just means that i export the spreadsheet with the errors, fix the error and then re import, the tool is more that good enough. We arent using complicated field mappings or anything like that, its all standard stuff.

I just need to get more than 250 errors out of the system. Any idea if there is somewhere in the system that can do that?

Chelcone

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Import errors capped at 250! PLEASE HELP
March 31, 2011, 08:30:18 am

try editing and modifying the constant at this file:

CRM/Contribute/Import/Parser.php

        MAX_ERRORS       = 250,

and change that line

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Chelcone

  • I post occasionally
  • **
  • Posts: 82
  • Karma: 1
  • CiviCRM version: 3.4.0
  • CMS version: Drupal 6.*
  • MySQL version: MySQL 5.*
Re: Import errors capped at 250! PLEASE HELP
April 01, 2011, 04:42:45 am
Thank you!!!! You Sir, are a god!!

Perfect solution.

Chelcone
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Import (Moderator: Yashodha Chaku) »
  • Import errors capped at 250! PLEASE HELP -RESOLVED-

This forum was archived on 2017-11-26.