Professor
ProfessorI believe the fix for you large report would be to schedule it for the future. If a report is to large, it just won't properly run. In the old UI it would prompt you for an email and then background it. Unless something changed recently to fix it, that wasn't hasn't been the case since the new UI.
ProfessorI stopped there at the end, but I did go on to make it scheduled for the future. It never completed running and never delivered anything to me in email. But my email isnt blocked. I get other regular reports that are smaller that were set up previously that I get on the regular.
So scheduling it for a couple hours in the future and waiting produced no results. I suspect the amount of data was too much. Several times when I tried to run it adhoc and DID get it to try to do something (after the above) I got the error message that there were too many interfaces, 3600 vs some limit of 2900 or whatever it was. So I scheduled one on a subset (I have some sub folders) and still the data must have choked the back-end.
The only thing I think I can try now is to make 26 reports, one for each letter of the alphabet in my subfolders, or at least make a few, schedule those in advance, and see if I can even get anything at all.
A year or so ago, before the changes to the reporting back-end and the enforcement of UIv4, I would have had this done in 5 minutes. Now I've spend 3 hours trying to coax the system into giving me the same data. Lots of the old reports people used had to be abandoned or completely reworked into broken fragments back when they made some back-end changes to whatever handles the request.
Anyway, appreciate the suggestion. I should have clarified that it was one of the things I tried.
