Appeal and Package Fields Need to be Drop Down Fields in NXT Gift Entry

We use many appeal and package codes, these fields should be drop-downs in NXT gift entry. We are pretty consistent with appeal naming conventions, but the package codes vary, and it would be impossible to remember each one to use in a search. It should populate as a drop-down based on the appeal code selected, like in DB view.

  • Debra Vogel
  • Jan 8 2026
  • Attach files
  • Diana K commented
    28 Jan 17:01

    Absolutely agree with Debra's comment. This option is essential to have in NXT for all gift processing officers. Surprised this has a low vote # to date, we expect this will increase as more clients begin moving gift processing to NXT in the coming months prior to RE DB sunsetting. Thank you.

  • Michelle Tribe commented
    27 Jan 17:57

    Packages are especially important for direct mail: segmentation, analysis, and budgeting.

  • Debra Vogel commented
    13 Jan 17:13

    Based on the product update this morning indicating that dropdowns may not be supported in NXT gift entry, I want to reiterate the operational impact of this limitation. We use a large number of appeal and package codes to accurately track how gifts are received. While our appeal naming conventions are relatively consistent and fiscal-year based, package codes vary widely by segmentation, audience, channel, and timing. Expecting users to recall or correctly search for each package name is not realistic and significantly increases the risk of mis-coding during gift entry.

    In Database View, the appeal dropdown with a dependent package dropdown provides essential guardrails by showing only valid package options tied to the selected appeal. Removing this functionality in NXT is a regression that shifts complexity and data-quality risk onto users. Even if full dropdowns are not currently planned, some form of filtered or guided selection based on the chosen appeal is necessary to maintain accuracy, efficiency, and confidence in reporting. This is not a preference for legacy workflows, but a critical data-governance need for organizations that rely on appeals and packages for meaningful analysis.