Are there particular filter limitations that would cause excessive load times/failures?
As we mature in the operational reporting space, we are finding that most of our reports are taking longer and longer to load. Not only do they take several minutes to load, they take even longer to export or send directly. Has anyone else experienced this issue and if so, is there a workaround? I am wondering if there are certain limitations to how many filters can be used on a single report (we use many exists filters and references).The only documentation I found was for a limit on objects referenced, but not anything on AND/OR limitations. I understand the more columns and more filters you have, the longer it takes to process, but some of these reports return less than 1,000 rows which seems like that should be acceptable.
I am all ears people. Let me know if anyone has some restrictions or guidelines they have put in place for a better reporting experience!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @BrandonNW,
Back in the day, we conducted some thorough benchmarking and determined that after the fourth OR clause, performance degraded significantly. It might have improved since then (worth re-testing, for those who use 5+ ORs...), but one workaround is to create a calculated parameter that resolves and persists to the same result as the ORs (e.g. My Special Calc Parm = IF(A OR B OR C OR D OR E... , true, false) so that you can instead then update your report filter to "hit directly" on that one scalar, persistent value (e.g. My Special Calc Parm = true).
For geeks...another way to figure out where the slow bits are is to leverage the Developer Tools "Network" tab: and in case it's new to you, here's a primer for Chrome browser users.
Good luck, and I'd be interested to hear what you learn.
Regards,
Doug
I've never been able to get a solid answer from Adobe Support on this. My last instance had major page load issues (for reports and other areas all over the place). All Adobe would ever say is that it's within their normal "range".
There are limits to sending reports, but it's all based on the size of the file, etc., and doesn't seem to apply to page loads.
Views
Replies
Total Likes
Hi @BrandonNW,
Back in the day, we conducted some thorough benchmarking and determined that after the fourth OR clause, performance degraded significantly. It might have improved since then (worth re-testing, for those who use 5+ ORs...), but one workaround is to create a calculated parameter that resolves and persists to the same result as the ORs (e.g. My Special Calc Parm = IF(A OR B OR C OR D OR E... , true, false) so that you can instead then update your report filter to "hit directly" on that one scalar, persistent value (e.g. My Special Calc Parm = true).
For geeks...another way to figure out where the slow bits are is to leverage the Developer Tools "Network" tab: and in case it's new to you, here's a primer for Chrome browser users.
Good luck, and I'd be interested to hear what you learn.
Regards,
Doug
To add to Doug's correct answer; the more you sort or group, the slower it goes—more collection columns=more processing time, more calc fields=slower display times, etc.
Views
Replies
Total Likes
Thanks @Doug_Den_Hoed__AtAppStore !
I kind of assumed that would be the answer, but I was hoping for some magical solution to avoid creating more admin fields.
Views
Likes
Replies