I actually track that on an attribute. I use the honor/memorial tab only for things related to money - gifts, trusts, etc. I use attributes as it seems that I'm rarely segmenting people out for just that reason, so it works pretty well.

A somewhat related solution - if your reports are taking a long time, set them to run, using attributes, in queue. And then run the queue overnight. We have our queues set up to dump the reports into buckets (one for income statements, one for project activity, etc.). They are set to export as .pdf files...

Where the more casual style of The Raiser's Edge 7 for Beginners user guide becomes clear is when it is compared to The Raiser’s Edge Help file. The Raiser's Edge Help file defines attributes as follows: To add flexibility to your record keeping, use attributes to define and store special information...

Are you updating existing attributes already present on a record or are you importing brand new attributes on to the record? If you are doing the former you need the Attribute import id to correctly update existing attributes. If you are doing the latter you need your import set to 'Import new records'...

We have several client attributes that we would like to merge with other, almost identical attributes. Is there any way to do this?

I am not aware of any maximum and there are a number of types. (My understanding is only limitations to RE are size/space on server.) I would be very conservative in the # of constituent codes you use. For constituent attributes - if there's any consistency in data you are recording, I would recommend...

When running the monthly departmental income reports, I'm having to pull the college/division from an attribute defined in the project. This means the report pulls very slowly. The reason I'm pulling from the attribute is because our budget is in the unrestricted fund, but the donations are booked...

I also use for why it was changed, alto I also do this in notes aswell with keyword ADDRESSES, just because if a address gets completely deleted it would remove the attribute as well. I use an attribute as (table additional info: if member wishes us to use just a POB and not street and we have both ...

Our organization has an annual gala where an individual or couple is honored for their support and achievements. I have been asked write the proceedure for coding such people (in order to keep track of them) to our databasse. My first thought was to code them under constituent attributes; Attributes...

Hi Lori, The way it's been explained to me in a user group meeting is that a Constituent Code is what the constituent's relationship is to the organization (why s/he is in the database - board member, etc.), and an Attribute is a descriptor of the constituent. Hope this helps. Chris