This is creating huge delays in gift entry and many extra steps. We have been using same packages across different uniquely named FY Appeals for almost 10 years . We get an error in the NXT gift batch if I select the wrong package for the appeal that was entered, however there is no way to know from the huge list of packages what is the correct package. Since NXT can identify it is the wrong package, there has to be a way to limit the package list to only the correct package for the Appeal that is entered first, this already works in DBV, so please figure this out in NXT.

I agree with all the below statements. Package selection in web view needs to work the same as in database view. We repeat package IDs across multiple appeals, and the current way the grid batch functions is not feasible for us.

Totally agree with all the comments, this is a major issue on our side too.

Please remove the option to see all packages. We should only see the packages that correspond to the appeal being used.

Blackbaud suggested a workaround where we make each package description unique . This is not realistic. We manage hundreds of appeals, and this workaround quickly becomes unmanageable. The current setup is unbearable for day‑to‑day use.

Processing gifts with packages shouldn't be this difficult. Additionally, please do not attach packages to one appeal id only. They need to be used year over year with all appeals.

This is essential! When our system switched to grid view, we quickly discovered that we have 130 different packages that are some variation of the word "donation". Trying to find which one matches up with the correct appeal would be impossibly tedious. Our workaround so far has been to save the batch without a package then go in to each donation in database view and add the appropriate package. I appreciate hearing about the workaround from the split gift button!

This is such an important feature that we need, also in the previous batch entries package would be automatically filled out. It will be nice to have that too.

I'm unable to move batch entry into web view until this is fixed.

Gift batch entry in web view is impossible if you don't fix this. I currently have to submit the batch without a package and then go back into each gift individually and add in the package. This is ridiculous. Why update the batch editing and submitting process if it was just going to make everything worse and 10x harder to use? Please fix this ASAP.

This is a major issue! We use the same 5 package codes for each of our monthly renewal appeals, so there are literally hundreds of VF, F, C, CE and P packages out in the RE universe. If this was supposed to mimic our database view grid entry, then please make it actually mimic it (all of it!).

This is a big oversight, and I can't believe it made it through testing with this flaw. This is why we cannot begin using functionality as soon as it rolls out. This is not making us sleep better or making work frictionless. The moment something like this is discovered, users need to go back to database view.

Please correct this ASAP. Forcing users into clicking the split gift button is NOT an acceptable solution. Using packages presents incredibly useful and easy to access insightful reporting metrics.

This is super necessary! Our database is 50 years old, there are sooo many similar inactive appeal codes and packages