Global Delete a Record from an Attribute

Options
Brent Parrish
Brent Parrish ✭
Ancient Membership Photogenic
in Blackbaud Raiser's Edge NXT®: General Discussion
I would like to delete constituent records that carry a particular attribute ID, regardless of the table description. I can't seem to figure how to do a global delete based on this.
Tagged:

Comments

  • JoAnn Strommen
    JoAnn Strommen ✭✭✭✭✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic
    Brent Parrish:
    I would like to delete constituent records that carry a particular attribute ID, regardless of the table description. I can't seem to figure how to do a global delete based on this.

    I was going to ask if you truely mean to delete the records or just delete the attribute, but when your post came up it looks like by the tags you want to delete the records.  It also looks like you're new to RE this year.  So, here's the standard cautions: deleting is permanent.  Are you sure you want to delete the records, any giving history, any relationships etc. that they may have.  To globally delete records in most orgs, it requires supervisor rights.  Definitely not something every user should have ability to do.

    First I would back up database before attempting any type of global record delete.  If you have the rights to do it, global delete records is under Admin.  You will first need to create a query of the records that have that particular attribute ID.  Then use that query as the records to include in your global delete.

    Are you sure you don't want to do a global delete of an attribute?  (Just checking because I don't think many RE users utilize global record delete very often.)

  • Christine Cooke 2
    Christine Cooke 2 ✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic
    Brent Parrish:
    I would like to delete constituent records that carry a particular attribute ID, regardless of the table description. I can't seem to figure how to do a global delete based on this.

     Everything JoAnn Strommen said !   It is VERY rare that you delete actual constituent records.  If you are housekeeping and feel the need to completely delete an Attribute from the Table and the records consider this.

     Is this information that someone will need historically on those records down the road?  And If so -- is there a better place for it than the Attributes?  I have found in my many years and many RE databases that folks tend to put things in Attributes that should be in Events or Actions or Prospect Tabs.  If you move the info, then I could see deleting.  Deleting is forever so be sure!

     If the attribute or something in a table is in your way -- what I have done is rename the item in the table with a z in front of it.  Example: Garden Committee turns into zGarden Committee.  That way the table can be sorted and the ones with z will drop to the bottom of the list and it indicates that it is not an Active item in the list, along with unchecking the Active box.  I do that with all the Tables until I am absolutely sure that what I am inheriting is truly not relevant or possibly in the wrong place/wrong table in the database.  It has worked fantastically to "z" items, because they always drop to the bottom and therefore do not scramble the brains of those trying to read a person's record, all the items they should pay attention to are at the top.

     My suggestion, especially when you are new, but always really, is to "z" and deactivate, but not to delete.

  • Laura Caswell
    Laura Caswell ✭
    Ancient Membership Facilitator 1 Photogenic
    Brent Parrish:
    I would like to delete constituent records that carry a particular attribute ID, regardless of the table description. I can't seem to figure how to do a global delete based on this.

     If these records are duplicates, deleting is a good option. If these records are of constituents you will never ever contact again in any way, shape or form, marking them inactive is a good option. Or at least that's how we use the Inactive option. Is there is any chance these constituents would come to your attention again and someone would re-add them to your database? And then you would want to remove them a second time? If they were marked Inactive (or some other code) you would know not to add them again.

    Just food for thought before deleting. 

     

    laura

     

Categories