2015 Pledge Receivables Report runs for 10 hours, never completes

Elizabeth Kassoff

Ever since we've run this report for 2015 data the time it takes for this report to complete has only increased. In March it took 7 hours, now we can't get the report to finish while we are at work even allowing for overlapping employee schedules. One employee gets here and starts the report at 6:30 am. After he leaves another employee watches the report and then by 5:30 pm leaves for the day and the report is still running. The report isn't finishing after 10 hours of running.



Mind you, while running the report we can't leave our desks for more than 30 minutes otherwise our connection times out and we lose the progress we've made (we're hosted). Not to mention, that one of our 4 licenses is being used the whole time we're trying to run the report thereby limiting how many other people can use RE. We have been in contact with BB customer service since March and have had NO RESOLUTION to this issue. BTW, the 2014 report runs in 15 minutes, no problems whatsoever.



At this point we can't get the report to complete while we are still at work and are starting to scramble for an alternate solution so our CFO can get the information he needs to manage our financials. Is anyone else having this problem? Does anyone have a good suggestion for a work around?

Debra Holcomb

I use RE Queue to run large projects, some of which take more than 8 hours. I am not hosted so I don’t know if/how it would work in a hosted environment. If you can get out of the user interface and let the backend do its work, it will run much more quickly. It might be something to ask Support about, but they may not be very well versed in RE Queue.  If you use RE Queue, it will take a user license, but you will not need to babysit it while it runs.



As a work around for calculated fields which slow down output for me, I may create an attribute to identify only the records I want and speed up the query.  Just remember to delete the attribute when it's done.  

John Heizer

We're not hosted, so I can't comment on what limitations that might add, but first I'd increase or even remove the timeout setting, which you should be able to do for non-Supervisor users.  If you're running the report under a Supervisor level account (which has a mandatory timeout) ... well, basically, you shouldn't.  People should only be logged in with Supervisor rights when they have to do something "supervisory" (I keep a 2nd JHeizerAdmin user account for those times, otherwise I have an account with almost all rights, but not Supervisor.).



Beyond that ... I'd hold Blackbaud's feet to the fire.  You're paying for hosting and for support.  No report should take that long to run and they need to accept responsibility for getting the report to run in a reasonable time.  Demand the service you pay for!