Rollups Broken with Multiple Currency Org - Household Version 2.3.10

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use a 1x1 account model and an org with multiple currencies. 

2. Create a Contact with a Household, add a Opportunity

3. The OpportunityRollups trigger fails on the rollupHouseholdsFuture method. 
First error: Invalid field CurrencyIsoCode for AggregateResult

4. Manually Run the Opportunity Rollups and the Error also occurs during batch 
processing.

What is the expected output? What do you see instead?
Expect Rollups to be completed for Contacts and Households. Instead they are 
only done for the accounts, and no changes are made to the contacts or 
household records.

What version of the packages are you using?
- Version 2.3.10 (note Version 2.3.8 and 2.3.9 were released at the same time, 
so it could have been introduced during any of these changes)

Please provide any additional information below.
-1x1 relationships are still intact
-Changing Always Rollup to Primary Contact makes no difference
- If there is no household for a contact, the rollups work for the contact 
record.
- Error still occurs with all validation disabled.
-Running the test methods on npo02.OpportunityRollups fails multiple methods 
(see the attached screenshot).
-Contact roles are being created properly on opportunities

Thanks,
Corey

Original issue reported on code.google.com by cjul...@gmail.com on 31 Dec 2011 at 3:14

Attachments:

• households-multiplecurrency-issue.png

[GoogleCodeExporter]

Can you grant me login access to the affected org and email the org ID so I can 
take a closer look? Email is kbromer @ the standard salesforce domain.

Thanks-

Original comment by kbro...@gmail.com on 31 Dec 2011 at 5:15

[GoogleCodeExporter]

I have emailed you the organization ID.

Original comment by cjul...@gmail.com on 2 Jan 2012 at 5:58

[GoogleCodeExporter]

Hey Corey, this is a bug on our end.  It was caused by the workaround we needed 
to implement for this issue:  http://code.google.com/p/npsp/issues/detail?id=316

We'll get it fixed for the next patch release. Sorry for the problems

Original comment by kbro...@gmail.com on 6 Jan 2012 at 7:27

• Changed state: Accepted
• Added labels: 2.3.11, Package-Households, Patch, Priority-High, Type-Defect

[GoogleCodeExporter]

Original comment by kbro...@gmail.com on 19 Jan 2012 at 5:11

• Changed state: Complete-Patch

[GoogleCodeExporter]

Original comment by kbro...@gmail.com on 19 Jan 2012 at 8:44

• Changed state: Fixed