"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.

[Chris P_]

Well this is it:

metric.category=a06e607d37fcd600ac0b84f643990eea^metric=7c6e607d37fcd600ac0b84f643990eeb^string_valueISNOTEMPTY

So basically a metric category + a specific metric + string_value not empty

Adding a group by on:

instance->task->assignment group

[Chris P_]

We found a workaround...

We created the report as admin and then shared it with the user, at that point the group by is visible for the user.

[santhana mari]

Hello Chris,

Can you please explain the workaround? I am also having the same issue on my report.

Thanks.