Ability to modify goal and campaign performance dashboards on the home page
Campaign dashboards do not reflect disbursements or write offs, resulting in the amount raised being overstated. We have multi-year pledges that are being fulfilled by gifts from third parties, including foundations and donor advised funds. eTapestry recommends that these payments be applied as soft credits to the donor who made the pledge, then disbursement that amount and reapply as a pledge payment. This results in that amount being recognized twice; once by the party that made the payment and also by the pledging party. Write-offs are also not adjusted out of the "raised" amount. A second option would be to allow soft credits to be applied to outstanding pledges, but that would not deal with the write-off issue.
-
Guest
- Nov 14 2016
This is a big issue for my org as well and makes the dashboard useless. As donations are often provided as securities, it doesn't make it easier to have to remember how much needs to be deducted, and to train the different users in how to do this simple doesn't work.
My only option to make the dashboard usable is to manually reduce pledges when paid by a different entity, such as a company or DAF, and this changes the historical reference.
I agree with @Robert Burch - it's not acceptable to simply say it's a bug and there's no option to fix it.
I reported fact that disbursements do not affect Goal totals in any of the dashboard widgets as a but. Blackbaud came back with this:
"The team have evaluated this issue as a bug and have determined it will not be addressed in the program in its current state, because the tiles weren't designed to include disbursements.
We strive to select the most impactful changes and issues to address with each release to accelerate the rate at which we deliver new features while sustaining the highest level of quality for our customers."
This really is not very satisfactory. The eTap dashboard really needs a proper redevelopment to allow multiple reports of the same type as well as address this bug. I understood that this was being worked on two years ago but we have not seen anything yet.