I recently noticed you can now do e-Receipts in web view - which would be a huge improvement over our current database view e-Receipt process, which is very slow and frequently crashes. However, there are three areas that are thus far insufficiently developed, preventing us from being able to switch to the web view feature yet.

As we all know, email address handling can be complicated, and people over time change emails, or sometimes have multiple addresses they want you to use for different situations. We have invested a lot of time in database view managing these complex issues, and as a result we have an intricate system of Email Types that have historically supported our handling of eReceipts. In database view, the eReceipts parameter gives you great options for email type handling. We have a priority system where first it checks for a type we created called "Email receipt"; then if that's absent, it moves on to Email 1, Email 2, etc. This is very logical, and the database view parameter allows you to do all this. Well... the web view feature has no options whatsoever for handling Email Types. From my testing of the feature, what I have learned is that it looks up the table of Emails listed on the Constituent's Bio 1 tab, and it simply grabs the email listed in the first ROW of that table. I don't know about other orgs, but for us, since we are longtime RE users, these tables can get crowded. Given the usefulness of the Email Type table feature, we have not prioritized paying attention to the literal row order in the email table; in fact, given the way data entry naturally happens, it makes sense that the older or less-likely-to-be-preferred email addresses are likely to occur at the top of the table. So, if you're going to have all these features like a "Primary" checkbox and Email Types, why would you ignore them and default to something that's likely to be the oldest (thus, outdated) record?

Again, it's very encouraging to see that Blackbaud has continued to develop more features in the web view - but in the case of email receipts, it seems like again something very basic was released without sufficient testing or consideration as to what organizations actually need to do with those receipts. Once the filtering and the available merge fields are further developed, I'm sure this will be a useful feature.