We use quite a few custom fields for reporting across multiple departments. Having to go into each gift to select each attribute is very time consuming and negates any time saved by the new approval method. Using Global changes after the fact as suggested by RE representatives is counter productive to having good point of entry data practices and also not a time saving as our current gift entry practices. I understand the rational that in the long run this could potentially be a time saver - but not as its currently structured AND it reduces the ability to be flexible and adaptable as well

PLEASE -- we need this badly

I definitely need this to be able to generate the correct fields for my letter templates. Please add the ability to set a default custom fields in grid batch view. It would also be great to add a custom field to hidden fields in the online donation form.

Being able to set a default custom value in a template would save a lot of time - which was the whole purpose of you adding grid view. We use a few custom fields during gift entry and it's important to have the option and not have to go and select it from a drop down for every single entry in a batch.

Our organization requires quite a few custom fields and selecting them each individually for every gift will be an issue. Please make it that multiple custom fields can be selected in templates as defaults in the webview.

Yes, please mirror the functionality that was in DBV batch! :D

To mirror the functionality that was in DBV batch, it would be helpful to be able to choose some custom fields to treat as separate columns for quick review when scanning down the list of gifts. We need to be able to quickly review that certain required custom data is there or data that may affect what we put in other fields (acknowledgement letter code, appeal, package, etc). This is particularly important for data that is imported into batch (often dozens or hundreds or transaction rows) or that come in through standard NXT online donation forms that use custom fields to collect information from the donor.

In the meantime, a compromise might be to show a preview when hovering over the custom field link so we can review the fields data without wasting time clicking on every row's custom field link.

This is absolutely necessary

The ability to assign default values to custom fields within batch templates is essential for effective tracking. This functionality would streamline the data entry process and improve overall efficiency.

We have several custom gift fields that must be added to each gift. Having the option to add as default in a template would be a game changer, until then we can not adopt use of NXT batch in a way that streamlines our gift processing. This is essential to our gift coding process.

We use gift custom fields to capture details that are specific to each gift. For example, when an incentive is tied to a gift, we record information such as the requested shirt size using a gift custom field.

During large appeals, when many gifts are received by mail and include incentive selections, being able to enter this information directly within the batch grid would significantly improve efficiency. This capability would streamline data entry and better support high-volume processing.

We have 1 custom field we add to EVERY gift as it is needed for our finance department. It is the deposit name the gift is tied to. It is very cumbersome to pick this field and enter the value on every row.

We need the ability to set default values for custom fields within batch templates. We rely on these fields to track critical information including campaigns, matching gift descriptions, and third-party gift indicators — without this functionality, our data entry process is unnecessarily manual and prone to error.

Gifts may have more than one custom field applied to it; we need to be able to add preselected custom fields, so their drop downs can be easier to enter. Custom fields were the answer to a lot off things in RE, and now it feels nearly expendable. We have at least 5 standard custom fields associated with remits that we track and report on, and our donors are accustomed to using, however the GBV now requires the data entry person to go through several steps: (DAF fund name, Prayer request, Special Purpose (cannot be used as packages), IRA institution, and I want to know more about planned giving."

Nice to have the option to favourite the regularly used ones too, to keep them at the top of the list you can use to config any template.

We have one or two fields we regularly use and others are special case-by-case bases, and so this would be really helpful to be able to add just the one or two we need regularly in the batch with less steps to add them. (We have one that is for our business office, often used to denote if something is an IRA QCD or if it's a planned gift. This is currently built into our batch template it's used regularly enough.

This is essential to our process