Author Topic: Contact Import successful, records in database but not showing up in front end (Read 1151 times)

franc23 · July 15, 2008, 05:03:49 am

I added two new custom fields to contact("individual") type and tried importing from a utf-8 csv file. The import message says successful after taking approximately 3-4 minutes and the data appears correctly in the defined custom fields in the database. However, when I click on an individual in the civicrm frontend, the custom field returns empty(no data appears). Here is the only situation where it does show up. If I edit the individual, say ABC, and click on update(without modifying the empty custom fields) from the civicrm setup , then go back and re-do the import, the custom fields then pull up the correct data from the database.

So, it only pulls up the custom data after I edit the individual in the civicrm front-end. No other batch update/database edit/ method works. There were already other custom groups defined sometime back and they all work fine with the import if I try updating those fields again. It's only the newer custom groups that I add now that are not reflecting changes in the front end till I edit the contact individually. I have around 5000 contacts.
I use drupal 5.x with civicrm 2.1 release and haven't been able to figure this out. My apologies if I am reposting what has already been asked, searched on google and here and couldn't find this particular topic. Thanks for looking and any suggestions you may want me to try.

franc23 · July 15, 2008, 01:22:37 pm

Could someone please help, really stuck at a roadblock and do not know how to proceed. Any suggestions will be great.

Dave Greenberg · July 16, 2008, 11:03:39 am

I'm assuming you're using CiviCRM 2.0.x since 2.1 has not been release yet... I've not heard of this type of behavior before. Best bet would be if you could take a few of your import rows and anonymize the data (so no real names...) - and then try and recreate on the public demo the problem you're seeing. If it recreates - repost here with the details of the steps to recreate and attach your sample import file.

franc23 · July 16, 2008, 01:36:39 pm

Yes, that was my mistake. It's running on 2.0.1 with drupal 5.7. I tried the same in the demo site and was not able to reproduce the same error. What versions of civicrm and drupal is the demo running on? Just wanted to confirm that is not an issue.

I did a workaround on my system for now and was wondering how it could work like this. I added new custom fields to previously existing custom groups and then imported the files to those fields and it works as expected. Data populates the front-end correctly from the database.

There are four existing custom groups and if I add fields to these groups, it still works correctly. Only if I try to import it into fields under new custom groups, it does not populate the front-end. Does this help? I was afraid that I had crossed the custom field threshold or some cache related issue, but now have no clue as to why this issue maybe occuring.

Thanks Dave for your time and help. It'll be great if you could shed some light on possible reasons.

Dave Greenberg · July 16, 2008, 02:47:03 pm

Demo is running Drupal 5.7 and CiviCRM 2.0.5. You could try upgrading to 2.0.5. Mostly this is just downloading and untarring the latest codebase - but there is one small DB "fix" which is covered here:

http://wiki.civicrm.org/confluence/pages/viewpage.action?pageId=6946910

CiviCRM Community Forums (archive)

News:

Author Topic: Contact Import successful, records in database but not showing up in front end (Read 1151 times)

franc23

Contact Import successful, records in database but not showing up in front end

franc23

Re: Contact Import successful, records in database but not showing up in front e

Dave Greenberg

Re: Contact Import successful, records in database but not showing up in front e

franc23

Re: Contact Import successful, records in database but not showing up in front e

Dave Greenberg

Re: Contact Import successful, records in database but not showing up in front e