sfdc-SupportDevelopment / npsp

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

Determine current FY based on Org. FY Settings #336

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
The following code on lines 1175 and 1265 of OpportunityRollups.cls

(http://code.google.com/p/npsp/source/browse/households/trunk/src/classes/Opport
unityRollups.cls#1265)

assumes that the current calendar year is the current fiscal year, but this 
will be incorrect as least some of the time for any organization with a FY 
spanning calendar years (probably most of them)

integer thisYear = system.today().year();

For example, if an organization has a Sept-Aug FY (we do, in fact), then during 
November 2011, this code would identify the current FY as 2011, when in fact 
it's 2012. After New Years, it should role up properly.

Instead, the code should determine the current FY from Organization info:  
https://gist.github.com/2322443

Original issue reported on code.google.com by bk...@healthleadsusa.org on 6 Apr 2012 at 7:53

GoogleCodeExporter commented 9 years ago
Nice find - been trying to quash an issue around that for awhile, I'll 
definitely get that out via patch release shortly.  Thanks for the submit!

Original comment by kbro...@gmail.com on 6 Apr 2012 at 8:02

GoogleCodeExporter commented 9 years ago
I'm also affected by the other problem - was trying to solve that when I found 
this!

Original comment by bk...@healthleadsusa.org on 6 Apr 2012 at 8:05

GoogleCodeExporter commented 9 years ago
Yeah! Great find, indeed! Eager to have the fix.

Original comment by jim.jims...@gmail.com on 13 Apr 2012 at 7:13

GoogleCodeExporter commented 9 years ago

Original comment by kbro...@gmail.com on 26 Apr 2012 at 3:59