There are times when we need to perform database maintenance on The Raiser's Edge running on SQL Server 2008 R2. This maintenance includes tasks such as having a third party reconcile the mailing addresses and update them as appropriate. At presen...

This functionality has been broken for quite a while and is crucial to seeing which users are idle in the system. Please fix!

In order to keep of the donors who give through a 3rd party vendor, it would beneficial to set up a recurring gift on the true donor's record and apply the payment from the 3rd party vendor towards their's recurring gift.

Each time you create a new email you have to input the pms colors for branding. Having the ability to add them once allows you easy access to them with each new email.

When updating the 'online presence' information in CORE, it will not synchronize into RE through Connect RE. It must then be added manually in RE. This is important information for us to have in our database and would be useful for it to sync thro...

I would like there to be an automatic 'email checker' function that would immediately indicate to you whether the email address you have entered in a constituent record is valid or not. It would prevent inaccurate data from being put in, which c...

I need to put a lot of old batches that I do not want to delete AND also do not want to see in my general listing. Currently you can only move one at a time. It would be helpful to move a series of batches all at once to a folder to 'archive'

A client would like to be able to display the names of everyone who registered for an event on their website. They want people to be able to see who all is registered when they go to the registration tab for the event on their website.

The total for the Solicitor is not available in Export in the Summary information section. We have had to use Honour/Memorial Totals to get this information. SolicitorID is in the Gift info so it should be available for summaries.

Apply ALL Registration fees through NetCommunity to registrants instead of dividing among participants. The current scheme woks moderately well when selling tickets where 1 unit=1 ticket, but when selling tables where 1 unit=10 seats, you wind up ...