SQL error in reporting
When running a report, if any filters are added then the report does not work and throws up an SQL error. The suggested workaround is to use the filter editor which also does not work well, as when a new filter is added in the editor, the list of report headings which you can filter by are all invisible. You therefore have to guess which report heading you are selecting in the list, which looks blank but each row in the list does actually correspond to a report heading.
It would be good to have the SQL error fixed or at least have the list of report headings be visible in the filter editor so we can work around this.
Jake Day
shared this idea
-
Nicholas Reid
commented
This is a real issue in my team. As we have multiple offices and departments, not being able to use filters means we cannot use reporting.