It's strange that in Receipting > Receipt Series, the receipt number is shown as the receipt series and gift number together, but then, when you go to the gift record, the receipt number is just the number. This needs to be fixed immediately.
There are now mutiple ideas presented about receipt stacks and webview- 5401, 7305, 4691 and 5015. It would be great if Blackbaud could link them or consolidate.
Receipt stacks are important part of receipting and creating a unique receipt number for Canadian receipting requirements. Receipt series in webview is not aligned with receipt stacks in DB view, and leads to Canadian customers having multiple ways of trying to track individual receipt numbers. Automatic gifts processed in webiview do not rollover the receipt stack, which means more work on the backend to add it in a global change.
I would also like to point out that while these ideas may have relatively few votes, this is relative to the ratio of Canadian customers- American customers would likely not have this on their radar to vote for, so I would encourage Blackbaud not to equate number of votes with the the need for this feature. This is once again a feature that is integral in DB view, and is not being translated to webview.
please fix
It's strange that in Receipting > Receipt Series, the receipt number is shown as the receipt series and gift number together, but then, when you go to the gift record, the receipt number is just the number. This needs to be fixed immediately.
There are now mutiple ideas presented about receipt stacks and webview- 5401, 7305, 4691 and 5015. It would be great if Blackbaud could link them or consolidate.
Receipt stacks are important part of receipting and creating a unique receipt number for Canadian receipting requirements. Receipt series in webview is not aligned with receipt stacks in DB view, and leads to Canadian customers having multiple ways of trying to track individual receipt numbers. Automatic gifts processed in webiview do not rollover the receipt stack, which means more work on the backend to add it in a global change.
I would also like to point out that while these ideas may have relatively few votes, this is relative to the ratio of Canadian customers- American customers would likely not have this on their radar to vote for, so I would encourage Blackbaud not to equate number of votes with the the need for this feature. This is once again a feature that is integral in DB view, and is not being translated to webview.