Pay-cash in webview: Apply pledge campaign, fund, appeal, package, custom fields automatically

When entering a pledge payment in webview batch, after you have linked the pay-cash to the original pledge, the original Campaign, Fund, Appeal, Package, and custom fields from the pledge should automatically populate (like they do in the dbview) into the pay-cash you are entering. It is very inconvenient to have to leave the batch entry, open up the constituent/pledge records, and look up what the information was on the pledge.

  • Erin O'Meara
  • Aug 6 2025
  • Planned
  • Attach files
  • Guest commented
    30 Jul 18:58

    This is an important tool that we have in the database view and should definitely be in the web view as well. It saves time and reduces data processing errors. Hopefully it can be implemented soon!

  • Erin O'Meara commented
    28 Jul 13:36

    Fantastic! Looking forward to it ?

  • Paige Morabito commented
    27 Jul 19:41

    Yes! Not having this makes processing pledge payments much more time consuming in web view grid batch.

  • HEATHER HILF commented
    27 Jul 17:50

    Yes please!

  • Brandon Nieves commented
    15 Jul 13:40

    I was about to create a new idea until I found this one, and thought this was the same. Applying a gift to an existing pledge in Web View Batch should automatically input Fund, Campaign, Appeal, and other data fields from that pledge. It's as simple as saving time, keeping data streamlined and accurate, and being able to achieve the same goal in less clicks. I feel that would be one of many critical purposes for being able to apply a gift to a pledge; is to have all the existing info automatically drop in my batch once it's linked.

  • Guest commented
    15 Apr 15:08

    This is very critical to our operations. I hope this is implemented in WebView similar to Database view.

  • Tara Keith commented
    11 Mar 17:19

    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.

  • Julie Fournier commented
    11 Mar 13:29

    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.

  • Maria Duke commented
    10 Mar 15:59

    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.

  • Whitney Kimmet commented
    08 Jan 19:47

    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.