It seems the validation report is showing summary data and not detail. For example, pledge applied to, tributes, soft credit, fundraiser and opportunities are not shown. In DBV, there is a setting under “User Options” to select detail or summary. At the very least, we should have that same option in web view. Otherwise, we cannot efficiently validate the batch using this report.

The information provided on the DB view detail validation report is critical for ensuring gifts are entered correctly before approving. With the current webview validation reports, we are missing pledge applied to, tributes, soft credit, fundraiser, and opportunities. With this information missing, we cannot truly validate the data in our batch is correct and complete.

Please allow us to select page orientation - For recurring gifts there are extra columns that do not fit in the portait orientation. Instead of change to landscape they are pushed to a second row and given field headers. EVERY gift gets headers for the second row of data, making the report many pages longer than it would need to be if it could be in landscape format with all the columns fitting and the headers displayed only once.

Agreed. The current reports are incredibly messy and hard to read.
We have no need for "Pledge applied to" or "solicitor name) fields, they have no relevance whatsoever.
Why can't the report just be laid out the same way as in database view? Simple, clear and easy to read.

Agreed. Admittedly, I am still playing around with creating webview batches so I may find a way to create a batch that fixes all of what I am about to list but I am sharing for now in case someone else has already found a fix. I would add that the Webview Validation Report is very difficult to follow. I would like to see:

1)Shrink to fit and let the Gift Reference cut off so there aren't so many lines generated for one gift record.

2)It shouldn't take 2 lines for every constituent name, and their title (Mr., Dr. etc) doesn't need to be included.

3)The headers for the columns be grouped the same way that they are on the DB view report? It seems that it doesn't matter what how we have the columns configured when we create the batch because when we save it to review it, and then approve it, our column configurement disappears.

4)A gift record should not be split by a page break.

Yes we need this info and the name and ID constituent also. How can we use this report if we don't have the important info.

Yes, please. Absolutely need the batch query auto created and a description field that prints on the control report to name the query.

Yes! There's still work to be done on this report! Left justification of the fields makes the data reviewable. Centre justification is a nightmare. We need the option to use ID instead of description. Also, in DB view, you can select a field, add a default and then hide it from your data entry and it will still appear in the validation report. It appears to me that only the fields selected for viewing are included on the validation report. What does that mean for the fields that are not selected? Are they not populated with the default data?

I agree 100% and can the fields that are shown on the new validation reports be left aligned as they do in database view. It would look much neater.