Enable Mandatory Fields in Raiser's Edge NXT

Karyn Pierce
Karyn Pierce
Ninth Anniversary Kudos 1 Name Dropper Facilitator 1
in Blackbaud Raiser's Edge NXT®: General Discussions

Request to enable admin users with the ability to designate specific fields as mandatory within Raiser's Edge NXT. This functionality would streamline data entry, significantly reducing the time and resources currently dedicated to data cleanup tasks resulting from missing or inconsistent information.

Current Challenges & Impact:

  • Data Cleanup Overhead: Our data team spends 1-2 hours per week rectifying missing data (eg acquisition source on constituent records), including follow-ups with users. This process hinders productivity and delays critical reporting.
  • Inconsistency & Duplication: The absence of mandatory fields and single-selection options for tables (eg address type and email type) leads to data inconsistencies, duplicates, and inaccuracies, further complicating reporting and analysis. This also creates challenges for our integration solution.

Specific Fields:

  • Fields: Custom fields, addressee/salutation fields, valid from date field and others and other fields as determined necessary by the organisation.
  • Tables: Single-selection enforcement for fields like address and email type.

Benefits:

  • Improved Data Quality: Mandatory fields ensure completeness and accuracy, enabling reliable reporting and informed decision-making.
  • Increased Efficiency: Reduced data cleanup tasks free up valuable time for the data team and other users.
  • Enhanced User Experience: Clearer data entry expectations minimise errors and user frustration.

Comments

  • Alan French
    Alan French
    Tenth Anniversary Kudos 5 Name Dropper Participant

    @Karyn Pierce it might be good to post this in the idea bank, or vote for it if there's already a similar suggestion in there? You should see an “Ideas” button near the top of the forum page

  • Devan Bessinger
    Devan Bessinger
    Tenth Anniversary Kudos 4 Name Dropper Participant

    @Karyn Pierce Yes, agreed! We have multiple fields required within the database view, but those configurations don't carry over to the web view (which has created quite a headache for us). As @Alan French mentioned, please take a look at the Idea Bank. There are multiple ideas posted for this that you can vote for. I recommend voting on all of them just to cover all the bases! Hopefully, Blackbaud will get this corrected soon.

  • Karyn Pierce
    Karyn Pierce
    Ninth Anniversary Kudos 1 Name Dropper Facilitator 1

    @Devan Caton Thanks! I’ll definitely post in the Ideas Bank and vote on others too. Fingers crossed Blackbaud addresses this soon!

  • Christine Cooke
    Christine Cooke
    Tenth Anniversary Kudos 5 Name Dropper Participant

    @Karyn Pierce
    Yes! please! it is that way on db view side and we have a lot of required fields just for all the reasons you listed.

    Having to backtrack and cleanup constantly is inefficient and there are times when there is just not the time that you have to set aside because it gets commandeered for something urgent.

Categories