This idea has been merged into another idea. To comment or vote on this idea, please visit RENXT-I-10304 Customize New Validation and Control Report in Web view.
For the very new reports in Web View (Batch Validation & Control), it would be lovely if we could edit what we want to see in our reports. There is a bit of extra info. (personal opinion) that my org. wouldn't need and having all of the pre-set info. there makes the reports messy and kind of confusing. Plus the format, in general, for the Control report is odd.
I hope we can have the option to make a template for our reports in WebView soon, for now, I will stick to Data Base View.
Also missing on the Validation Report is Fundraisers and Constituent ID
I am having the same issue as you stated below. The Validation report is so hard to read as there is no spacing between each donor's info. Also, the Post Date and Appeal Code are not on the report, but they are in the batch. Our Finance team needs the Appeal code as it is very important to where this gift came through. There are other things that did not show up on this report even though they are in the batch set up. We need the ability to be able to select which fields are required in the Validation repot.
The Control report - I just approved a Monthly Recurring batch, and on this report, it says under each donor's name 'Pledge Applied to' but this is a Recurring gift, not a Pledge. To be honest, I don't need that on a Control report. The Database reports were so much better and everything was there that we needed.
yes not easy to read, we need to be able to select the column we need. We also need the name and ID constituent It doesn't show in our repart at all. How can we use this report if we d'ont have the important info.
Hi Jason, I agree!
Hi Anne, me too. It has a little bit of every info. that my org. doesn't need but its way better than these new ones
We definitely need to be able to adjust the data and make it exactly as the current control reports are in DBV. The headers overlap onto the next line for the same donor, which does 2 things: 1. increases the length of the report and 2. makes it unnecessarily confusing to read. At least allow it to export/print landscape if there are overlapping headers into the next row, so they are all on the same row. Overall, reduce the amount of whitespace (again - what is with all of the whitespace in EVERYTHING?) to compact this report.
I agree! This does not have a lot of the information that I need. The format is horrible and the report overlaps with the heading. I like the way the database view report looks better.
Hi Liz, I agree. I am the one creating the batch and looking over the control report and it takes a bit to understand what you're looking at (if there are pledge payments in that batch), especially with the way it does the "Pledge applied to" section. A lot of our constituents send in different amounts each month/more than the projected amount for each month so it just looks weird.
I've noticed with the batch validation report, the order of the columns is the same as the way your batch/batch template is set up - regardless, it would be very beneficial to be able to edit and create templates for these reports so they can actually make sense and not have unnecessary info.
Hi Paige, it seems as though we do have Constituents Id as fields with both database view and the control report in webview. I believe Constituent codes in the reports would be very helpful as well!
It would be great to have Constituent ID and Constituent Code as fields.
The old control reports didn't have the information about soft credits and they were easy to read. The new ones add in soft credit information below and look very jumbled when you have many gifts in the batch. It's extremely difficult to understand what you are looking at unless you are the one who entered the gifts. Given the control reports are generally used more by finance, they won't be able to make heads or tails of them.
The validation reports are missing custom fields, soft credit information and tribute information. The order of the columns doesn't make sense to me either. It would be great if we could customize that as we could in database view.