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 CiviMember (Moderator: Deepak Srivastava) »
  • inherited Memberships and custom fields
Pages: [1]

Author Topic: inherited Memberships and custom fields  (Read 426 times)

jschenck

  • I’m new here
  • *
  • Posts: 4
  • Karma: 0
  • CiviCRM version: 4.4.3
  • CMS version: 7
  • MySQL version: 5.5.34
  • PHP version: 5.4.9
inherited Memberships and custom fields
January 29, 2014, 02:41:52 am
Hey
i've running into a problem with inherited memberships in Civi. We are running the latest CiviVersion on Drupal7.

I've setup an relationship. This relationship is used in a membershiptype to inherit this memberships. I've also created custom fields for this membership type.
When i update the primary membership civi-fields are getting updated in the inherited membership f.e. Startdate etc. But when update a customfield in this membership they're not getting updated to the inherited membership. Is this a bug? Is it this bug: http://issues.civicrm.org/jira/browse/CRM-14031?focusedCommentId=56110&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
Or do i make a mistake? Anyone an idea how to solve this issue?
Thanks
Jan

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: inherited Memberships and custom fields
January 29, 2014, 10:11:42 am
Jan - Your issue is different from Maggies in the issue tracker (CRM-14031). Maggie wants to be able to update custom field values in inherited memberships independently of the primary membership which is currently not allowed.

Expected behavior is that updating custom field values for a primary membership should update that value in inherited memberships - so if that's not happening I think that is a bug.

Please see if you can recreate this on the public 4.4 demo (link above). If so, please open a new issue on the issue tracker with detailed steps to recreate the bug and screenshots.
Protect your investment in CiviCRM by  becoming a Member!
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • inherited Memberships and custom fields

This forum was archived on 2017-11-26.