Closed GoogleCodeExporter closed 8 years ago
This relates to the Recurring Donations module
Original comment by nnewbro...@gmail.com
on 13 Dec 2010 at 4:48
Original comment by gok...@gmail.com
on 13 Dec 2010 at 4:20
I second this!! This is a great enhancement request.
Original comment by dwhi...@gmail.com
on 23 Feb 2011 at 11:18
Just wanted to toss my $.02 on this.
I think you're 100% correct, this is a much needed improvement. However,
because of the way recurring donations are currently setup, it actually makes
it a bit of a sticky problem to properly create rollups for paid and
uncollected pledges, and based on time/need, it probably won't be added in a
future release.
More likely, we'll use some sort of child payments object to solve this problem
in future releases, so you can define your own payment rollups to the
opportunity, and calculate the recurrence, payments types, etc. independently.
Not sure what the roadmap for this looks like yet, but it's definitely on the
list. Thanks for the feedback - would love your continued thoughts on this.
Original comment by kbro...@gmail.com
on 23 Feb 2011 at 11:30
Thank you and great to hear from you. I'm not sure i entirely understand the
second paragraph (child payments object, etc.). Does that mean that we would
no longer need the Recurring Donations module, and instead we can assign child
payments to a regular opportunity? If so, that sounds superb like the start of
a really superb solution. Any rough guess as to a timeline for that?
Original comment by nnewbro...@gmail.com
on 23 Feb 2011 at 11:40
That sounds great - I think that would work well. In the meantime could you
not add something to your current triggers that run when an opportunity is
added and also at night that sums all the opportunities that are closed won by
Recurring Donation and then write this to a currency field on the Recurring
Donation much like you do on the Contact? Maybe I'm over simplifying it - I'm
not a developer so I don't know what it would take to do this.
Original comment by dwhi...@gmail.com
on 24 Feb 2011 at 12:05
The payments would be part of that module along with the existing recurring
donations model, we want to be able to support either method (or both, you
could imagine a use-case for a recurring pledge, a multi-year method of tying
together certain opp types, etc.) But yes, it would involve child payments
assigned to a single opp instead of multiple opps assigned to a single
donation.
A good portion of the code is out there already, it would just be a case of
needing to integrate it into the existing NPSP setup. I'm hoping the next
major release we do would include an updated recurring donations package as
well, but I don't yet have a timeline for that
Unfortunately, its not quite as easy as tweaking a trigger, but I'll look into
some possible short term fixes in the interim.
Original comment by kbro...@gmail.com
on 24 Feb 2011 at 1:16
Just finished implementing this in our system. A bit of apex code, a new
"oustanding amount" field in the recurring pledge, and a Apex schedule that
runs once a day = calculated field that sums all pledged donations that are
outstanding. Happy to share the code if you want it.
Original comment by coreybro...@islandschool.org
on 4 Sep 2011 at 4:50
That sounds amazing - would absolutely love to include it in the next release!
The best way it to either mark-up SVN live in Google Code, or feel free to
email it to me as well if that's easier. (kbromer @ sfdc) Thanks, looking
forward to checking it out!
Original comment by kbro...@gmail.com
on 4 Sep 2011 at 9:17
Code is on its way.
Original comment by coreybro...@islandschool.org
on 22 Sep 2011 at 2:10
Original comment by kbro...@gmail.com
on 22 Mar 2012 at 9:38
Original comment by kbro...@gmail.com
on 22 Mar 2012 at 9:40
Original comment by kbro...@gmail.com
on 26 Apr 2012 at 3:57
Original issue reported on code.google.com by
nnewbro...@gmail.com
on 11 Dec 2010 at 9:50