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) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • Inherited memberships
Pages: [1]

Author Topic: Inherited memberships  (Read 3462 times)

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Inherited memberships
July 30, 2008, 10:51:14 pm
I ran into a significant issue in how the inherited memberships system works in 2.0 --

Basically, in addition to the membership record inheriting to the employees of the organization, the contribution record has also inherited. So if ABC Company becomes a member and pays $200, all employees of ABC Company have a membership record (good) but also a contribution record for the $200 payment (very bad). That's very problematic because it basically throws all contribution records/searches off.

Anyway, I tried to reproduce on 2.1 sandbox before submitting an issue, but the membership inheritance mechanism appears to be broken altogether. (which is why I'm posting here)

The following demo data is identical on both 2.0 and 2.1 sandboxes:
Membership org = Demo Membership Org
Company = ACME Company
Employee = John Doe
Employee = Jane Doe
Membership Type = Indiv inherits Org

Membership + Payment is assigned to ACME Company. In 2.0 sandbox, both membership and contribution inherit. In 2.1 sandbox, no inheritance takes place.

Jira: http://issues.civicrm.org/jira/browse/CRM-3371
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

geilhufe

  • I post frequently
  • ***
  • Posts: 293
  • Karma: 33
    • Social Source Software
Re: Inherited memberships
July 31, 2008, 09:32:56 am
This is the clasic case for a soft credit... the real contribution belongs to the organization and the soft credit can be associated with other constituents without an accounting impact and with a clear reporting impact.
Drupal and CiviCRM consulting, strategy and configuration
http://www.social-source.com/

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Inherited memberships
July 31, 2008, 11:53:29 am
I "think" Brian's issue is that multiple contribution records have been erroneously created (and we are looking at that based on the issue tracker item). Soft credit functionality requires a new way of linking a contribution record to "additional contacts" beyond the one that actually "made" the contribution. We don't yet have that in our data model (although I suspect we will in the future :-) ).
Protect your investment in CiviCRM by  becoming a Member!

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: Inherited memberships
August 01, 2008, 06:57:58 am
Dave is correct -- an actual contribution record is erroneously being created for individuals who inherit membership from another contact via relationships (not just a connection to the real contribution record). Kurund posted a fix on the issue tracker which looks like an easy issue to backport to 2.0 for those who need an immediate fix (like me!).

There might be value in a soft credit structure, but you'd need to make sure the interface and search tools made it *very* clear what you were looking at.

-Brian
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

geilhufe

  • I post frequently
  • ***
  • Posts: 293
  • Karma: 33
    • Social Source Software
Re: Inherited memberships
August 01, 2008, 07:40:34 am
Yeah the very clear part is the killer. I have yet to see a system that handles it well...
Drupal and CiviCRM consulting, strategy and configuration
http://www.social-source.com/

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: Inherited memberships
August 01, 2008, 08:26:00 am
Ok, I lied about there being an easy backport to 2.0. The BAO/Membership.php file is significantly reworked in 2.1.
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

lcdweb

  • Forum Godess / God
  • I live on this forum
  • *****
  • Posts: 1620
  • Karma: 116
    • www.lcdservices.biz
  • CiviCRM version: many versions...
  • CMS version: Joomla/Drupal
  • MySQL version: 5.1+
  • PHP version: 5.2+
Re: Inherited memberships
August 01, 2008, 08:36:07 am
Backport to 2.0 is easy -- things are just moved around in 2.1, which threw me off.

If you need this issue fixed in 2.0, in CRM/Member/Form/Membership.php, around line 507 (see two "ADDED" lines):

Code: [Select]
                    $params['status_id'] = CRM_Core_DAO::getFieldValue('CRM_Member_DAO_MembershipStatus', '0', 'id', 'is_current_member' );
                }
// we should not created contribution record for related contacts, CRM-3371 //ADDED
                unset( $params['contribution_status_id'] ); //ADDED

                $relatedMembership = CRM_Member_BAO_Membership::create( $params, CRM_Core_DAO::$_nullArray );
            }
        }
support CiviCRM through 'make it happen' initiatives!
http://civicrm.org/mih

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Alpha and Beta Release Testing »
  • 2.1 Release Testing »
  • Inherited memberships

This forum was archived on 2017-11-26.