With the current limitation for pledges, it is easier to continue doing batch in database view until the campaign, fund, appeal, and package auto populate.

Issue:
In WebView batch entry, when entering a pledge paiement linked to an existing pledge, the Campaign, Fund, Appeal, Package, and custom fields from the original pledge do not automatically populate. This creates inconsistency with Database View, where these fields are correctly carried over.

Impact:
With the new batch grid, this limitation is still present. Additionally, once a pledge is selected, there is no visibility into which Campaign, Fund, Appeal, or Package are associated with the original pledge. Users must leave the batch, navigate to the constituent record, and manually look up this information which is inefficient and increases the risk of data‑entry errors.

Requested improvement:
WebView Grid Batch should work like Database View and automatically populate all fields (Campaign, Fund, Appeal, Package, and custom fields) from the pledge when a payment is linked to it.
This would improve accuracy, reduce manual lookup, and streamline batch processing.

On DBV, I appreciate setting and forgetting the appeal, fund, campaign, gift split, and more on a pledge, knowing that as payments came in, they would auto-fill in my gift batch or in manual entry. On Web View, I've noticed that neither individual gifts nor gifts entered in grid view seem to pull that information. I would appreciate this feature. We have many donors who send monthly checks personally or through Donor Advised Funds, and it would be very beneficial to save time hunting down this information on each individual donors individual pledge.

This should be happening automatically. The fact that we have to vote on it instead of it already being there demonstrates a lack of understanding of the work gift processors do.