"Group by" in report causes Security Constraints

[NickBaker]

I have a script include that accepts in a table, field, and custom query and displays duplicate values.   I use this script include within a filter to build certain reports.   The reports display the exact information I'm after, but whenever I try and specify a field to "Group By", I get the Security Constraints message below.

I've tried enabling debugging to highlight what ACL may be missing, but I wasn't able to find anything obvious.   As stated above, if I don't choose a field to "Group by", the report runs perfectly and displays the records I'm looking for.

[Uncle Rob]

"Group By" allows more records to be read at once though, and the security constraint errors ONLY come up once you've reached a point where you can't read.

I've seen lists of 101 records where the security constraint error only appeared after someone paged 5 times to get to the very last record.

First thing I'd test is ungrouping the data, displaying as many records as you can per page, then paging for a bit to see if you get it naturally.

[NickBaker]

In this instance, I'm showing users who have 2 computers assigned to them.   If I try and group by the user, I get the security constraint.   If I ungroup and adjust display to show 50 records, I can see all 32 records with no issue/no security constraint.   Thanks for the reply.   Any other thoughts?

[Uncle Rob]

Iiinteresting.
So, I don't suppose you're having trouble viewing Assigned_to.name, are you?
Maybe run a report against user table (including name column) and see if anything comes up weird?

[NickBaker]

No problem seeing Assigned_to.name.   It doesn't matter what I "Group by", I have the same issue.   I actually have another report targeting a different table entirely and I run in to the same issue when I try and use my script include within the filter.   It works perfectly as long as I don't "Group by".   The second I try and group by any field, I get the security constraint message.