Forum Discussion

Lewis_Beard's avatar
Lewis_Beard
Icon for Professor rankProfessor
21 days ago

Reports custom time range more than 1 month old?

When did it change to where, if I need to whip up a quick report to get a month of data from January for something, that I cant make a report and just run it? I dont often do such things but I had some of my users start complaining, because they do that a lot. Sure enough, in order to just grab some interface bandwidth csv from Jan 1 to Jan 31 or etc, I have to schedule the report, I cant just wait.

When did that kick in? I'm sure it was a footnote somewhere in the patch notes, the question is semi-rhetorical however. The real question is .... WHY?!

Last year, IIRC, we started being more limited on numbers of interfaces or objects that can be shown at once in reports, our portal went through a buggy period that seems to be better now where reports were empty because they were served up before ready (seemingly fixed) and NOW to do ad-hoc reports, we have to schedule them and wait. Between that and everyone disliking UIv4 (I'm constantly getting complaints about it) I'm having lots of disgruntled users.

But this reporting limit on data more than a month old is just more frustration. I get if somehow the reporting back-end needs these things because of limits I'm not aware of, but removing functionality is always a bad idea. It would be nice if the first X reports for old data, run ad-hoc for anything, were let through without hassle. Say 10 ad-hoc reports for OLD data per hour, and THEN bottleneck it. Or something. But this is really irritating.

1 Reply

  • Ian_Marge's avatar
    Ian_Marge
    Icon for Employee rankEmployee
    4 days ago

    Hi Lewis,

    Thanks so much for raising this. We hear you. The change to require scheduling for reports for data over 30 days old was made to ensure that larger, more complex reports always deliver complete and reliable results. While ad-hoc reports are great for recent data, we found that scheduled reports are the best way to handle bigger timeframes consistently.

    We know this adds an extra step, and we are actively exploring ways to bring back more flexibility for quick, one-off historical checks. Your idea about allowing a limited number of ad-hoc reports for older data is a great suggestion, and I’ve shared it with our engineering team.

    In the meantime, one tip other users have found helpful is creating a “template” scheduled report you can quickly duplicate and adjust for different date ranges.

    We really appreciate your feedback, it helps us keep making the platform better.

    - Ian