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) »
  • What happens to custom fields on merging (dedupe) records?
Pages: [1]

Author Topic: What happens to custom fields on merging (dedupe) records?  (Read 609 times)

myles

  • I post frequently
  • ***
  • Posts: 263
  • Karma: 11
What happens to custom fields on merging (dedupe) records?
January 27, 2012, 02:11:55 am
Does the process for merging duplicate contact records move custom fields from the duplicate to the original record before deleting the duplicate?

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: What happens to custom fields on merging (dedupe) records?
January 27, 2012, 11:31:52 am
Quote
Does the process for merging duplicate contact records move custom fields from the duplicate to the original record before deleting the duplicate?

Yes.

Kurund
Found this reply helpful? Support CiviCRM
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using Core CiviCRM Functions (Moderator: Yashodha Chaku) »
  • What happens to custom fields on merging (dedupe) records?

This forum was archived on 2017-11-26.