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.
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. 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.