Blaine, are you sure the name of the temp table is different when you go from static to dynamic to static again? In my tests it is "STATIC_RECS_####" where "####" corresponds to the Query ID.
With regards to database usage, IMHO the IT dudes need to suck it up and buy a bigger RAID. Disk space is cheap and we got work to do!
Jeff - I am not sure what you mean by hairy and not hairy gifts.
By "hairy" I mean something like a Pledge that has multiple posted payments from a spouse, three different splits and maybe a write off for good measure. If you have one of those and two other simple cash gifts, might be easier to move them all to the destination and re-create the non-hairy records on the source constituent rather than manually recreating the "hairy" gift. Read More...
Technically the answer to your question is "yes", but it only works if there is one gift on the "source" constituent. You can merge the records and select to only merge the gifts. If there is one really hairy gift that you want to move and the rest of the gifts are pretty tame, it might still be worth your while. Good luck! Read More...
I was thinking he could still split it up temporarily just to narrow down which one it was (assuming there is a main culprit), then he could see if that one could be modified/streamlined/enhanced. Come to think of it though, it gives him a guaranteed 20 minute coffee break any time he wants it ("Waitin' for RE7 dashboards to load, whatcha gonna do?"), maybe he could share the configuration with the rest of us so we could get the same?
Is it possible to narrow it down and see if one or two dashboards in particular are causing the most delay? If so, perhaps those could be left off and checked less frequently?
Hello All,
We will need to submit the claim electronically due to the volume of gifts
Hi Alison and Lisa,
Are you required to submit electronically? Looks like this HMRC guide (is.gd/CKvvk7) says that "can" submit electronically, but doesn't seem to command it:
[quote]If there are more than 200 separate entries you <strong>can</strong> submit the information on a disc, although you must enter the totals from each schedule on the disc onto the Read More...
We've been considering creating a solution to handle just that. Would love to hear what sort of requirements you would have for such a system. If you get a chance, please stop by our booth (#300).
While you're there, we're also giving away the best RE7 Appeal Analysis and Fund Goal Performance Reports the world has ever seen (pretty sure about that anyway - you be the judge). Hope to see ya!
I'm struck by this question: "What leverage do you have over the event coordinator to ensure that he/she doesn't create duplicates, makes the fewest mistakes possible, captures new information?"
We recently worked with a large healthcare client to solve just that issue of leverage! Their events folks complained that entering/updating data in the Events module took too long due to the multiple windows/tabs that need to be navigated to, for instance, add 8 placeholder guests when someo Read More...
Did you build someting? Looking for banner-re solutions.
Hi Tara,
A number of universities use Import-O-Matic to process Banner data into Raiser's Edge 7 automatically. As a large portion of our clients are higher-ed, we've invested a lot of time implementing the features they need (like matching to existing Education relationships based on user-defined criteria, importing multiple family relationships [with duplicate-matching] simultaneous Read More...
Some interesting reading from the BB KB (see below)... apparently RE:Open and RODBA are now rolled into EDA, or "Extended Database Assistance", that is a function of the Advantage Maintenance plans. If you have Open/RODBA, you should be able to access KB item BB125883 which will define what is covered under support maintenance to help you write queries against the DB.
What are Extended Database Assistance (EDA), RODBA, a Read More...
Glad to hear it. We just added Gift Amendments to the forthcoming version of Import-O-Matic for the Raiser's Edge, so if I was stumped while looking at the code I was going to rummage around in our code to see how we did it. Read More...