Allow the Constituent ID field to be locked.

As it stands, anyone who has access to the Bio 1 tab can change the constituent ID. What is the point of an ID field if anyone can change it?

It would be best if access was restricted in Security (by user group), but as a Business Rule (as it is in The Education Edge and other BKB products) would work too.

  • Guest
  • Jun 20 2012
  • Shipped
  • Attach files
  • Guest commented
    March 17, 2016 23:06

    AMEN!

  • Rose Kelly commented
    March 17, 2016 23:06

    we hid the constituent ID so no one can change it (config, fields). We changed the user settings so that the title bar uses the listing from config (addressee/salutation list) where it shows idnumber, first and last name. when you add a new user, you just have to make sure you copy another user settings so that they can see the title bar this way.

  • Guest commented
    March 17, 2016 23:06

    Brilliant, Rose!

  • Guest commented
    March 17, 2016 23:06

    We actually look at the const. ID a lot during clean up. So I don't want to hid it. But I also don't want to unintentionally change it.

  • Guest commented
    March 17, 2016 23:06

    Yes the Constit ID should be lockable. The same goes for other ID fields such as Gift ID, Membership ID & Event IDs etc.

  • Guest commented
    March 17, 2016 23:06

    And deceased, has no valid address, and inactive!

  • Guest commented
    March 17, 2016 23:06

    YAY!

  • Sandra Thomas commented
    March 17, 2016 23:06

    This is wonderful. I like Rose's idea, but we have users who change the title field to see the name a different way, so that ended up not working out.

  • Alex Wong commented
    March 17, 2016 23:06

    This would have been a great update to the software IF after making the Constituent ID field view only, that you can still select it for copying and pasting elsewhere

  • Guest commented
    March 17, 2016 23:06

    Yes the consituent Id should be lockable as a Business Rule and where access should be limited. For example one who does merging of duplicate records should have this consid unlocked as there could be cases where the merged from and merge to record needs to be changes. In short staff will supervisory access should have this field unlocked, but for all other users this field should be locked.