donagha

I had a similar problem where my database and query worked in older version of jasperserver (2.x) but when attempting to upgrade to 3.5 it failed. My data source is view of several tables for simplicity. All data is entered into the relational tables and since my dataset is fairly small I took the liberty to create a View to create a fact table from the other relational tables. It worked a treat until 3.5. The schemas are unchanged and valid in the workbench and upload to the server. What I found out, for my problem, was that the field type of one of my fields after a concatenation of an integer and text field produced a VARBINARY(263) data type. This can be understood by the older version but not with 3.5. Solution: Change the data type on the database to VARCHAR by casting the integer to a CHAR before CONCAT. Bingo it works! Code:Offending code: concat(`P`.`PROJECTNUMBER`,_utf8' : ',`P`.`PROJECTNAME`) AS ACTIVITYto: concat(CAST(`P`.`PROJECTNUMBER` AS CHAR),_utf8' : ',`P`.`PROJECTNAME`) AS ACTIVITYCube: <Dimension name="Activity"> <Hierarchy hasAll="true" allMemberName="All Activities"> <Level name="Project" column="ACTIVITY" type="String" uniqueMembers="true" levelType="Regular" hideMemberIf="Never"> </Level> </Hierarchy> </Dimension>

Correction to my last statement. You do need '!'. In my haste I wasn't thorough in my testing. The '!' transposes the ID_STR string into a list of integers in the query. I'm only supposing this, but it does provide the correct results. Post edited by: donagha, at: 2008/04/22 12:53

I solved it by creating a 2 parameters: ID as java.util.Collection ID_STR as java.lang.String edit ID_STR default and add the following expression: $P{ID}.join(",") use $P{ID_STR} in your query. I was able to execute the report with and without '!'