Webview batch entry problems

In webview batch entry if a fund is present before assigning an appeal and I select a recently assigned appeal, it will either change the fund to the default for the appeal or, if that is blank, change it to the default for the campaign associated with the appeal, or, if both are blank, just remove the fund from the field. Is this by design? I understand the benefit of assigning a default fund if the field is blank but overwriting what is there seems counter productive. In this case, the fund information is sent over from Almabase so when the fund disappears, I have to go back to that site or my exported list of gifts to find it again. Note: neither the appeal nor the campaign have the “limit data entry to only the funds associated with this appeal/campaign” selected.

The second issue is that after assigning an appeal and then package, when the gift is saved the package disappears. If I save and close the batch, the package will remain. Saving and closing after each gift is very time consuming. Is this a bug? I find it's faster to approve the batch and then go into db view to assign the package.

Comments

  • Dariel Dixon
    Dariel Dixon Community All-Star
    Seventh Anniversary Kudos 5 First Reply PowerUp Challenge #3 Gift Management

    @Xep Campbell I believe it is by design, but it is misleading. It basically is giving you all of the details of the last couple of gifts. In the case that you're talking, the appeals have defaults and the defaults are being applied. I think this is a case where you either have to apply the values manually, or apply the recent appeal templates, and manually change the fund.

    My org doesn't use packages, so I can't speak on that part, but it does feel like a bug. I'd put in a ticket and check the idea bank to see if it has been addressed there.

  • @Xep Campbell
    We put in a ticket last week because we are experiencing some similar issues and I can tell you, it was not always like this. Something changed recently. My ticket with support has been escalated to engineering. I shared your post with them in my ticket to demonstrate that it's not just me and I'm hopeful they can isolate what changed. This happened right before our Day of Giving, so you can imagine the angst we are experiencing, but we have an awesome gifts processor who is on top of it and caught it, but she's touching every transaction from that day. We are halfway through the correction process.

  • @Xep Campbell
    I think there is a bug in the RE NXT side for batches. I have experienced the same issue with packages not being saved. Another issue I have is that the “save” button does not save the work and sometimes the “save and closed” button does not save the work.

  • @Rosalyn Galloway Thank you for the confirmation! I have a ticket open now and will reference your reference. :)

  • @Xep Campbell
    I noticed this also happens when looking at each gift. I would think when entering the Fund, the Appeal would default, but when entering the Appeal, the Fund should stay the same.
    I had to pull the email confirmation we received to find the fund to add it back in.