Flagging gifts as "Posted" to G/L

robert badley

We are in the process of implementing Post-O-Matic to take RE transactions to our GP Dynamics G/L. In preparation I am trying to go back and flag all of my old transactions in RE as "Posted" as opposed to "Not Posted" which they are now. 


I thought it would be simple exercise to create a static gift query capturing the gift types that I wanted to affect and running a global change. What I am finding is that when I start the process up it runs pretty smoothly up until about 400 transactions in and then the progress degrades considerably. When I get into the 1000s of records changed it is taking well over a minute to change one record!! Needless to say I will never finish at this rate. I have tried stopping and restarting the process and again it runs smoothly at first and then slowly grinds down.


Has anyone experienced this? Is there some sort of SQL setting that I need to check to see why this is happening?


Thanks.

Ryan Hyde

I haven't experienced this directly, but instead of troubleshooting this problem, I'm going to suggest you just sidestep it by doing an import instead. From your static query, output the gift Import ID. In excel, add a column called "GL Post Status" and fill it with "Posted." Then set up a gift import, set it to update new records, map your fields, and go to town. Make sure you run it in 'validation' mode first to make sure things are actually updated as expected (no need to do a full run through in validation mode, just a few records to make sure you didn't do something silly like typing "Psoted" instead of "Posted," as the typo version will just return nothing but errors). 


If you've never done an import before, let me know and I'll walk you through it. This is a very simple import, so it wouldn't take too much work.

robert badley

Great idea Ryan. I am familiar with the RE export/import process and will give it a try today. Thanks for the suggestion.


I'm still mystified as to why the simple global change behaves like this. We often use it for other constituent updates and have not experienced this before.

robert badley

By way of update, exporting, editing and re-importing is not proving to be much better as it started out at a reasonable pace and has since slowed down to the point where it has taken almost 4 hours to import/update just over 4000 records. Considering that I have about 2.8 million gift records to update it could take 116 days!!


I am going to have to lean on Blackbaud for another solution.

Elaine Tucker

Not that this is a best case scenario solution, but would it help to break the queries down into smaller chunks?  I'm thinking that there may be a "corruption" somewhere in the back end coding on possibly a single gift that is causing this to hang up. (We had that happen once, and it was a nightmare to find the culprit)