New Gift Batch Template - Custom Fields default value
When building a Gift batch template, it does not allow setting values to the Custom Fields; such information needs to be added manually for each gift, which adds more time to the batch entry. We use at least 4 Gift Attributes per gift.
Yes! Please allow to set which custom field is being used in a batch and allow for default values both for custom field description and type. We have quite a few custom fields that we use. Some are drop downs, some are yes/now (a check box in dbv), and some are free form entry. Not all are used in every batch (some depend on gift type).
For my organization, allowing for default custom fields in gift batch sooner than later will speed up our moving at least some gift batch entry to the unified view sooner.
I've built one template in unified view, and if I were able to set default custom fields rather than just a column for all custom fields that requires scrolling through a long list to choose the field and then fill in the values for it, I would have been able to have our gift entry person move some of her gift entry to web view now.
As it stands, I have to wait till this is implemented before making the move.
I would really really appreciate if this was implemented. It already takes much longer to do batch in NXT compared to database view, its critical that we find efficiencies where we can. Also, each custom field should be a column and not a + click on. Way to many clicks.
I agree! The flexibility and customization of database view--including the incredibly powerful custom fields--is what justified the price tag of RE. We need an efficient way to enter custom fields as described in the original idea post.
I would also like to see pre-filled custom attributes that come in from an online donation form each in their own column in the webview batch. This assists us with some manual allocations that happen in batch, such as fundraiser credit. It is tedious to have to click into each gift's list of custom attributes and scroll to find data that used to be available at a glance.
This is a huge one- we have a required custom field that there is a value for on all our gifts. Manually adding this in one by one is very time consuming. This addition is needed to truly bring webview batch to parity with database view by Sept 2026 as has been promised.
Yes! Please allow to set which custom field is being used in a batch and allow for default values both for custom field description and type. We have quite a few custom fields that we use. Some are drop downs, some are yes/now (a check box in dbv), and some are free form entry. Not all are used in every batch (some depend on gift type).
For my organization, allowing for default custom fields in gift batch sooner than later will speed up our moving at least some gift batch entry to the unified view sooner.
I've built one template in unified view, and if I were able to set default custom fields rather than just a column for all custom fields that requires scrolling through a long list to choose the field and then fill in the values for it, I would have been able to have our gift entry person move some of her gift entry to web view now.
As it stands, I have to wait till this is implemented before making the move.
I would really really appreciate if this was implemented. It already takes much longer to do batch in NXT compared to database view, its critical that we find efficiencies where we can. Also, each custom field should be a column and not a + click on. Way to many clicks.
Yes!
We need this very much. It is WAY to time consuming to do this manually for each gift. To many clicks to get there.
Yes!
YES. I also agree with Olivia... they need to be separate columns instead of clicking into it each time!!
Yes. Yes. Yes.
I agree! The flexibility and customization of database view--including the incredibly powerful custom fields--is what justified the price tag of RE. We need an efficient way to enter custom fields as described in the original idea post.
I would also like to see pre-filled custom attributes that come in from an online donation form each in their own column in the webview batch. This assists us with some manual allocations that happen in batch, such as fundraiser credit. It is tedious to have to click into each gift's list of custom attributes and scroll to find data that used to be available at a glance.
This is a huge one- we have a required custom field that there is a value for on all our gifts. Manually adding this in one by one is very time consuming. This addition is needed to truly bring webview batch to parity with database view by Sept 2026 as has been promised.