| Category: | Bug report |
Priority: | Normal |
Status: | Assigned |
| Project: | Severity: | Major |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
If the Query Editor is used to edit a query containing a $X expression with semi-colons as parameter separators (as is required if you need to include SQL Functions in an IN clause) when the query is saved the semicolons are replaced with commas. This causes the report to fail when it is run (which is correct behaviour on Jaspers part).
Contrived example:
$X{IN; SUBSTRING(name, 1, CHARINDEX(' ', name) - 1); versions}
Bizarrely the iReport Preview mode seems to handle the invalid report definition fine.
