In a recent project I had to ensure that specific confidential information was being saved as an action. I had a custom screen where this data was going to be viewed and edited. Only certain users had access to that action using security by action types. I had to check to see if the current user was able to view the action and if they could whether or not they were able to edit the details. There are useful methods for this in the API and I assumed it would be a simple task to use them. Continue reading Checking access restrictions in The Raiser’s Edge
I like BlackbaudKnowHow. The blog that consists of many articles on best practise within Blackbaud’s products often inspires me. The posts are written by a lot of different people at Blackbaud with a lot of experience in Blackbaud products. One post written recently, What Should You Consider When Users Leave?, highlighted what users of The Raiser’s Edge should do when one of their users leaves.
One issue it does not cover (there are probably many more that were beyond the scope of the article) was what to do about action reminders that have been assigned to a user. The article suggests either deleting the user or changing their name, giving them prefix of “X”. Neither of these solutions help when a user has actions reminders associated with them.
It is possible to go in and change the assignments one by one. It is also very easy to miss them too. It is quiet easy to see what could happen if you miss a reassignment. A major donor who was due to be reminded about their donation is now forgotten about because the reminder instead of going to David goes to “XDavid” who is not longer at your organisation.
Our free plug-in Action Reminder Updater helps solve this problem. Select a soon-to-be ex-user and select a replacement user. Press start and all of the actions will be reassigned to the replacement user. Simple.
Zeidman Development are pleased to announce the release of our latest plug-in for The Raiser’s Edge – BatchIt:Action
BatchIt:Action allows you to enter actions en masse in a batch. This is the first of a series of modules in the Batch:It range.
Entering actions one by one is slow. Importing actions in one go is not always practical. BatchIt:Action provides the solution to simply and efficiently entering accurate data.
Create templates for different types of actions. For example, do you use actions to represent an event, or a request for information. Populate the template with defaults and hide pre-populated fields just as you would in a gift batch.
For users with advanced requirements set up a custom validation file that implements your organisation’s business rules. Does your event actions always need a t-shirt size? Should a phone action be prevented if the phone number is international? Create custom validation rules to enforce this or let us help you create them. (Requires coding skills, additional custom validation module required)
More information can be found on our website where you can download a fully working version tied to the Sample database. There is also a screen-cast showing BatchIt:Action in use. If you have any questions then please contact us.
I have been working on a project to bring in a large amount of data into The Raiser’s Edge. Everyone else on the project has been using SSIS to do this and previously I would probably have manipulated the data in Excel, Access or for the most complicated data written a small application to convert the data into the format that I wanted before importing it into RE. Having used SSIS for a day now I am say that I am converted!
Continue reading SSIS Convert
A lot of the work that I do involves the integration of third party products with The Raiser’s Edge. It is not always right to develop a custom application to perform this integration. There are many factors including the volume of data transfer, the complexity of data, how quickly the data needs to be integrated and of course what budget is available. This article attempts to outline the options available to Raiser’s Edge managers who need to integrate with non-Blackbaud products.
Continue reading Integrating Raiser’s Edge with non-Blackbaud Products
A few days shy of the end of the year, I hearby present to you the top visited plugins of 2008 (unless of course there is a sudden rush on any of them before midnight in which case the list will be adjusted accordingly). This list is based on the top number of clicks through to the more information about each plug-in supplied by each plug-in author.
Blackbaud NetCommunity Integration
Bank Checker Solution
Clear Invalid Spouse IDs
Constituent Document Linker
Code Insert Custom Part
Convio DataSync Connector RE
Action Reminder Updater
Thank you to all that have added to the directory during the year and to those that have rated the plug-ins.
The title is somewhat dramatic and probably not relevant to many people however for me and a client that I work with it proved to be a disaster. This is not the first time that Blackbaud has changed the API and it certainly won’t be the last but this was annoying. So what am I referring to?
Continue reading Blackbaud broke the API
I have on several occasions expressed my delight about the arrival of the Batch API. I am still enthusiastic but somewhat war weary having spent this passed week trying to solve problems that have appeared. Clearly the Batch API was not rigorously tested before it was released as otherwise the sort of errors I am getting would not have appeared. In case you have been struggling too or in case you thinking about using this functionality here is what I have been up against.
Continue reading Battling on with the Batch API
Here is a strange problem that I encountered. I wanted to show the constituent form with constituent data. I also wanted to know if the user had saved and closed or just closed the form afterwards. If I had not been interested in knowing this information then I would have simply done the following: Continue reading The Case of the Missing Tabs
Inspired by a posting on Wired (which in turn was taken from a Wiki on obsolete technologies) I wanted to give you a list of the top five obsolete areas of the RE:API.
- Continue reading The Obsolete API