Welcome to Online Express Ideas!
Please submit all product enhancement ideas below. We welcome your feedback; your ideas will be reviewed by the Product Manager that oversees the development of that part of the product on an ongoing basis and updated with its current status monthly based on our product planning process. Ideas you submit could help us shape features currently in development or grow our repository of requirements for our next big enhancement. Thank you for taking the time to share your thoughts and expertise with us.
If you believe you are experiencing a defect or have general information that you wish to publish, please submit those within the Online Express Community or contact Support.
The ability to accept and reject donations with bulk processing
This would be useful as when bulk processing donations if you reject and changes but accept others, all the changes are still accepted. Instead of processing one by one it would be faster to reject or accept on a line by line basis.
-
Guest
- Dec 27 2017
Related ideas
Privacy Policy | Safe Harbor Notice | Terms of Use | Acceptable Use Policy | © 2016 Blackbaud, Inc. All Rights Reserved
This is a ridiculous bug on an equally ridiculous "add on" software. We have stopped using Online Express for recurring donations (since it does not automatically process recurring donations). We hardly use it for regular donations because of the limits on the forms and now we are finding out it's not really good at event registration downloads either! I have never used a system that is as backwards as this. There is much better software out there for online forms, email marketing and event registrations.
No one told me this would happen, now 300 donations later I am just learning that all the time I spent accepting and rejecting was lost because I bulk processed. Why would anyone want to manually download 100 donations? Please fix this asap, it doesn't even make sense that the bulk button rejects all info, what is the purpose of that????
I have to be honest, I have no idea why I bug like this would even be shipped in the first place, let alone still an issue. For an organization that gets lets say 100 transactions in a day to have to process each one INDIVIDUALLY to ensure the right info gets into the database is very unacceptable. Please fix this ASAP.