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) »
  • Data consistency in contact importing
Pages: [1]

Author Topic: Data consistency in contact importing  (Read 785 times)

xcf33

  • I post frequently
  • ***
  • Posts: 181
  • Karma: 7
  • CiviCRM version: 3.3.2
  • CMS version: Drupal 6.19/6.20
  • MySQL version: 5.x
  • PHP version: 5.2.6
Data consistency in contact importing
May 24, 2010, 08:08:13 am
Hi guys,

I've been playing with the import process a bit, some things I found that is interesting I don't know if CiviCRM addresses.

1. When importing custom fields or fields that has set values (say radio button, checkboxes, selection boxes), how do CiviCRM ensure that the importing file values will to consistent to those values set on these fields in

Code: [Select]
civicrm_option_group
civicrm_option_value

Obviously this problem can be solved if the import person takes a look at the import file first and make sure that the values in the import file matches those stored in civicrm, but is any upcoming version going to address this? (Maybe using a field sub-matching??)

2. Some of the fields available for import in the contact importing process is not available when you use the create contact screen or edit an individual contact. In my mind I thought all the importable fields should be reflected in create a contact and edit contact screens.


Any feedback would be appreciated.


Cheers,

Chang

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: Data consistency in contact importing
May 24, 2010, 12:57:51 pm

1. i'm pretty sure we do field level validation on each row before we insert them into the db. if it does not match, we throw an error and ignore that line

2. can u give examples of what fields can be imported but not edited/viewed?

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

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Import (Moderator: Yashodha Chaku) »
  • Data consistency in contact importing

This forum was archived on 2017-11-26.