Field defaults are ignored on Constituent Update Batch and Revenue Update Batch

A Field Default is set on the "Select Fields and Defaults" tab of a Revenue Update Batch or Constituent Update Batch.

This default appears on new rows, but it disappears after a transaction or Constituent is selected for update.
​The Constituent Update Batch does not allow defaults to be set for fields. The value from the constituent record (even if the value is blank) will overwrite any default set on the field in the batch template. Manually enter the value on the field.

The Revenue Update Batch does not allow defaults to be set for fields. This is to protect transactions by avoiding unintentional changes to revenue data. If a field default is set on the batch template, it will be removed when the transaction data is populated. The value from the transaction (even if the value is blank) will overwrite any default set on the field in the batch template. Manually enter the value on the field.

Steps to Duplicate

1) Create a new template for Revenue Update Batch or Constituent Update Batch.
2) On the "Select Fields and Defaults" tab, select a field
3) In the "Field Defaults" section, set a default value
4) Save the template
5) Create a batch with this template
6) See the default value on a new row without a record selected
7) Select a record. Note the default value on its row is now gone.

Environment

 Blackbaud CRM
 4.0
 4.0
 4.0.172

Was this article helpful?