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) »
  • Custom fields architecture question
Pages: [1]

Author Topic: Custom fields architecture question  (Read 394 times)

permaculturegeek

  • I post occasionally
  • **
  • Posts: 44
  • Karma: 2
    • Permaculture in New Zealand
  • CiviCRM version: 4.4.x
  • CMS version: Drupal 7.x
  • MySQL version: 5.1.x
  • PHP version: 5.3.x
Custom fields architecture question
March 23, 2014, 02:18:57 am
I designed some custom fields for our test integration early on in the process to facilitate data import, but I'm now having second thoughts about the architecture now that I understand better how memberships work.

Am I correct is saying that a membership custom field is suited for storing information relating to a specific memberhip instance/period, and that information which is permanent (such as a member ID number) is better stored as a contact custom field?

If the above is correct, is it possible to change the filed type, or do I need to export data, delete the membership field, add the contact field and re-import data?

Erik Hommel

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1773
  • Karma: 59
    • EE-atWork
  • CiviCRM version: all sorts
  • CMS version: Drupal
  • MySQL version: Ubuntu's latest LTS version
  • PHP version: Ubuntu's latest LTS version
Re: Custom fields architecture question
March 24, 2014, 12:54:39 am
In principe, any information that is specifically related to the membership is stored in a membership custom field, and information specifically related to the contact rather than to the membership (like the member ID you mention) is stored at the contact level?
Consultant/project manager at EEatWork and CiviCooP (http://www.civicoop.org/)

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Custom fields architecture question
March 24, 2014, 01:46:44 pm
Agree w/ Erik that a permanent 'membership ID' attribute should probably be part of the Contact record. Unfortunately you can't change the "Used For" setting for an Custom Data Set so export => import is your best bet.
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) »
  • Custom fields architecture question

This forum was archived on 2017-11-26.