We are a group of users of Blackbaud products and are not affiliated with Blackbaud. We'd love to have you join our community to help and be helped in getting the most from your Blackbaud software.
Register now to join us to get independant advice on your system, connect with 3rd party consultants to help you maximize your database and have a real alternative to the official Blackbaud website.
We record how a member joined and how they renewed under membership attributes (i.e., initial recruitment = website or renewal recruitment = museum store). But we have problems pulling the information into exports once they've renewed twice or more. The export pulls the first "renewal recruitment" rather than the last "renewal recruitment" and doesn't seem to offer an option to pull by date.
Does anyone know how to make an export pull the last attribute when there are multiple options?
OR
Does anyone have a better suggestion for where to record the information. It would be particularly helpful to have it linked to a specific membership action rather than membership in general.
Attributes can be a bit unfriendly in that respect.
When you enter a new membership, renewal, upgrade, etc., there is a field called Reason. If you are not using the field for anything else you could track the transaction location here. This field is accessible in Query and Export under Membership History. If you queried on the information appropriately and sort the query in descending order by the Transaction date, when you preform the export of the Reason field and include the date, it exports the most recent date first. In Configuration you can rename the Reason field to something like Location. This field also has is a drop down, so you could specific these locations and then use this field to query/report on. This would associate the specific location of each transaction on the membership.
The only other place that might give you what you want is the attribue on the gift linked to the renewal...but I really don't like that idea. I am not a fan of burying data because that can become more difficult to reach later for reporting and querying purposes.
Hope this helps!
Sean
__________________ Sean Seabrook Blackbaud Implementation Specialist Make-A-Wish Foundation of America
Thank you, Skippy. I'll give it a trial run and see if that works. I never even noticed that little reason button hiding discretely in the bottom corner.
Do some testing first and see how it works. I would recommend the sample data b/c you cannot mess anything up in it. If you don't have it loaded, you can get a copy from the BB website.
__________________ Sean Seabrook Blackbaud Implementation Specialist Make-A-Wish Foundation of America