Incorrect Account System applied to Pledges when committed through an Enhanced Revenue Batch

Users have the ability to default fields in batch and hide these fields with the expected result of the default value being applied to the records added via that batch or batch template.  Currently users are finding that when setting a default for the Account System to something other than the default account system, hiding the field, that some pledges are committed to the system under the default system GL account rather than the account system specified as the default value in the batch template.
We are currently evaluating this issue and will update this article when we have more information.

Environment

 3.0.516 service pack 3

Was this article helpful?