search

sfdc-SupportDevelopment / npsp

Automatically exported from code.google.com/p/npsp
0 stars 0 forks source link

Incremental Oppty Rollups are incorrect for households #331

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
For households with multiple active donors, if a donation is edited, the 
incremental rollup to the household mainly contains the rollups for the donor 
of the recently modified donation (for most fields at least).

What steps will reproduce the problem?
1. Create a household. Create two contacts for that household
2. Create (closed-won) donations for each contact. (lots of possible test 
cases!)

What is the expected output? What do you see instead?
The household should have complete rollups for both contacts in the household. 
The household in fact only contains data for the contact related to the most 
recently modified opportunity. This is resolved by running the nightly batch 
rollups.

The following fields are incorrect (reflect the rollups for a single contact 
until the nightly rollups run):
Average Donation
All the total donations / number of donations fields

The following fields appear correct:
Smallest donation
Largest donation
First / Last donation date
Last Donation Amount

What version of the packages are you using?
C&O 2.1.2
HH 2.3.11

Please provide any additional information below.

Original issue reported on code.google.com by jamesmel...@gmail.com on 12 Feb 2012 at 7:55

GoogleCodeExporter commented 8 years ago 
I think this is caused by the original code only querying the affected 
Contacts, and since we're manually calcing those values (avg and closed), its 
only including that single Contact. 

I'm going to try and figure out a patch-able workaround for the problem. I'm 
hoping to do a complete rollup re-write for 2.4 (hoepfully late spring 
timeframe), which will definitely address the issue. Thanks for the issue notice

Original comment by kbro...@gmail.com on 13 Feb 2012 at 6:24

GoogleCodeExporter commented 8 years ago

Original comment by kbro...@gmail.com on 26 Apr 2012 at 4:01