Our integration with HubSpot came about because they thought it would be a great idea. Well who wouldn’t think it a good idea to integrate with The Raiser’s Edge. HubSpot said that they had a number clients who use both systems and being able to transfer data from HubSpot back into The Raiser’s Edge would make both systems work better together.
Continue reading The Raiser’s Edge Integrated with HubSpot… A series of case studies (3)
We are really excited to release Biographica. This application integrates The RAiser’s Edge with Gmail (or Google Apps). This means that from within your Gmail inbox you can see details of a supporter as their email arrives. At the current time we show the biographical details (name, address, email and phone), constituent code, solicitor/canvasser, a gift summary and recently attended events. We only show this information if it is available for the constituent (so we don’t leave a lot of blank headers and take up a lot of space). Check out the product and view the screencast on our Zeidman Development site: http://www.zeidman.info/Integration/biographica.php
Continue reading Release of Biographica – Integrating The Raiser’s Edge and GMail
We develop a number of different types of solutions that connect The Raiser’s Edge with third party applications. When this is done for one organisation the hardest challenge is getting the requirements to match the end user’s as closely as possible. However we also develop a lot for third party applications directly. Most recently we released Chimpegration but there have been many others that integrate many different areas of the application. With these clients the important point is not so much as to match one set of requirements exactly but to match as many requirements exactly!
I have yet to come across two organisations that have set up RE the same way. Sometimes the differences are small but sometimes they are very large. One recurring theme is that of phone/email types. The Raiser’s Edge seems to be relatively unique in its setup of these values. Not only are phones and emails stored in the same location but you can store them according to address type too. How does this match up with a third party web application that uses email address as a primary key? They may have one field for home phone, one for mobile and possibly one other. How do you get that tie in with the possibility of any combination of phone and email types? I have seen a whole plethora of regular phone types e.g.
Home
Business
Preferred
Home 1
Home 2
(etc)
Primary
Work
Company
Those are just the ones I can think of as I write this. And of course each of these could have a number after them.
Then of course there is the proliferation of email (or is it e-mail, etc) addresses.
What techniques do we use to overcome these issues? When we are working with a third party developer directly it is often in their interest to develop the configuration piece. This saves them a lot of development cost. This means that we simply say to them if you want us to update a phone number you need to tell us which type it is. This is then supplied in the file/webservice. Likewise when we supply that piece of data, we also send the phone type too.
Another solution is to build a configuration part to the application. This is what we did with Chimpegration. We allow the end user to map the fields that they want to synchronise so that they specify which fields on MailChimp map to the fields on The Raiser’s Edge.
The last solution is the least desirable. It is possible to simply say that the home phone number should be called “Home” and email address should be called “Email” – end of story. This is clearly the simplest and cheapest but unless you have a lot of sway over the organisations that you are selling to it is unlikely that you are going to get many buyers.
Phone and email types are perhaps the most obvious but what other issues can arise?
Where you are collecting business details, should these be added to an organisation or to a business address on the constituent record? Should you create a new constituent for the organisation? How can you be sure that it does not already exist in the system but under a slightly different name. One solution is to allow the end user to review the matches that have been made but this again adds to the development cost. It could also be prohibitive if the volume of data you are bringing in is large.
What about fields that do not have an obvious place in The Raiser’s Edge. One application that we worked with had an anniversary date. There is no such field in RE. We gave the end user the option to ignore the field, store it has the spouse relationship from date or store it as an attribute.
What happens if one organisation makes a field mandatory? When I work with an organisation directly I will ask them what mandatory fields they have set up on their system. If, as part of the process, I have to create a new constituent then I will ask them to give me a default value for that field. For a generic solution this has to be worked into the application configuration.
You can see much of this in action in Chimpegration where we account for mandatory fields and different combinations of phone types and emails. Check out the synchronisation screencast for a glimpse of this in action.
So all said and done is this type of solution to be avoided? Absolutely not! It is not cheap because of the extra work involved in making the application work for all types of organisations. When people complain about NetCommunity or Patron Edge integrating badly with The Raiser’s Edge hopefully this article will have given you some insight as to the skills required by Blackbaud in getting the integration to work well. (Update 15th Dec 2011: I should clarify that given the difficulty in developing generic solutions I actually believe that Blackbaud have done a good job with these integrations)
If you are a third party application wondering how to integrate with The Raiser’s Edge then speak so us. We are skilled at doing this and have done it a lot. We can either do it for your or we can share the development. When done well it is a great asset to your company and will bring Raiser’s Edge users to your application.
The past two weeks have been packed with all things Blackbaud. Last week was the Blackbaud conference in Washington DC and then this week in London. Being a big fan of all most things Blackbaud, I had a great time, met some great people, got to meet the all new star cast at the top of the company and was pleasantly surprised by the announcements made.
Waiting for RE8 has gone from waiting with great anticipation and expectations in previous years to how we find ourselves now. We now know that RE8 will happen at some point (albeit probably under a different name) but the wait is over. We are no longer waiting for the next big thing, but for the little things. In past years we have been wowed by what was to come on the Infinity platform. This was exciting but left us wanting it without it ever arriving for the majority. Now however, looking at the new functionality in RE7; query lists, new lookup functionality, better dedupe features and being able to easily mark participants as attended, shows that despite its name (and its UI), RE7 is moving forward. Blackbaud is moving forward for everyone.
This was demonstrated so much more so in Blackbaud Mobile. The application allows you to promote campaigns through channels that may have been previously inaccessable to the majority of organisations. Allowing organisations to promote and give supporters the mechanism to donate through text message and mirrored on a Facebook app, brings their technology offerings into this decade.
After being burned by the anticipation of the Infinity platform’s greatness for The Raiser’s Edge users, Blackbaud are quite rightly avoiding the risk of repeated vaporware. One such thread could, in previous years, come from the exciting news of Raiser’s Edge Mobile. This application will be native to iPhone, Android and possibly Blackberry, will allow users to access their RE database directly from their mobiles. After having looked at a prototype version, I am quietly confident that this application will make it in the near future. This is another step in Blackbaud’s progression of the RE7 platform into the modern age.
What is really exciting however is the technology required to enable this. There will need to be a webservice layer for The Raiser’s Edge. There has been this web service layer for a while now with the NetCommunity integration. However it has always been restricted to NetCommunity specific tasks with limited use for other applications. If Blackbaud do the right thing this time around and make the web service layer generic and open to all applications, all of a sudden we will integration with The Raiser’s Edge like never before from all sorts of web based applications.
It does not matter what it is called (RE7 or RE8, Infinity or not) it is the perception that Blackbaud’s offerings are going forward and not stagnating. With the wait for RE8, RE7 was left languishing. The risk was great that organisations would move away from Blackbaud to other platforms offering what Blackbaud should have been doing years ago. Now at least they are moving into the modern era.
If you had not noticed, our website zeidman.info has had a make over. We have also added a new section of everything to do with Blackbaud Enterprise CRM and the Infinity platform. Some of the screencasts there were previously embedded in conference presentations so now they have a home of their own. We are really excited by what the Inifinity platform has to offer (even if it is slow coming to the majority of users). Now you can see for yourself the kinds of customisations that can be developed and just how powerful the platform can be.
Have you been working on any BBEC customisations that you would like to share? Have you seen any others out there in the wild. Leave a comment and let us know.
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!