 |
 |
|
|
|
Did you know?
|
Here are some examples of work that has been done in the past. If this inspires you then please do not hesitate to contact us.
1. "We are using The Raiser's Edge quite innovatively where we use otherwise unused fields on a constituent record for other purposes. This make data entry difficult as the fields are spread out on different tabs. Is it possible to consolidate all these fields on to a new constituent tab keeping all the other tabs in place?"
- Unfortunately it is not possible to simply add a new tab to the constituent record. However it is possible to add an extra screen where data can be entered. By tying the screen to a constituent macro it is easy to bring this up from the constituent record while entering data. This was implemented at The Conservative Party
2. "We never know who has made a change to a constituent record or to a gift record. The Raiser’s Edge ought to track this kind of information not only down to the constituent level but also on a field level. It should also tell us what the values were before and after."
- We developed this solution at Barnardos who wanted to have an audit trail of basic biographical and address information. All changes would be recorded. When viewing the data they wanted to be able to filter it by the user who made the change, by a date range or by the constituent the change was made on. This customization took approximately 2 weeks.
3. "There are certain fields that we want mandatory but the Configuration section of The Raiser’s Edge does not offer you this functionality."
- To make a single field mandatory is a very simple customization that can be completed, in the majority of cases, in an hour. One example of this is the package field on a gift. This is not listed in the Config section of The Raiser's Edge but a user can be prevented from saving a gift without it with this quick customization.
4. "When a constituent makes a gift we would like to copy an attribute from the constituent to the gift thereby stamping the gift with the attribute. That way even if the attribute changes on the constituent, we know what it was at the time the gift was made. We do use constituency for this purpose but we have a special attribute we want to track too."
- This is a simple customization that takes about two hours to complete. This is perfect for segmentation purposes. No matter how the attribute changes on the constituent the gift that was given can be tied to that attribute for historical analysis.
5. "I am doing a constituent update import but I do not want to overwrite a full first name on the constituent record with an initial that may be in the file. Equally if there is a full first name in the file but an initial on the constituent record I want it to overwrite it. How can I add this kind of logic to my imports?"
- This type of criteria can be added to any import (not just constituents). It ensures data integrity by only allowing certain types of information to be imported. The customization can also cause an exception where certain criteria are met so that the record is not updated or imported at all. This kind of customization was implemented at Help the Aged. To complete the above example requires about 3 hours of work.
6. "We receive standing order data from our bank and would like to use The Raiser’s Edge’s standing order batch import functionality. Unfortunately our bank is not listed."
- It is possible to write a definition for a specific bank. In the list of data sources there is an entry for “User Format”. This is for a custom format that can be developed. This customization is about two day’s worth of work.
