dylan.snyder Posted February 13, 2015 Share Posted February 13, 2015 Hi,I am having an issue with a prompted report that I created. I have done the following steps to create a prompted "In List" report. When I go to select the values for the paramaters and run, however, it returns the following message every time: "The report requires that you specify the value for some parameters before running it." 1) Put the Parameter in the Where clause: 2) Create the Parameter: 3) Click on "Preview". I then click the "..." next to the parameter Prompt 3) I select some values in the Parameter List dialog Box: 4) Hit OK 5) When I click the Green Arro "Run Button", I get the following message, and my report doesn't run:"The report requires that you specify the value for some parameters before running it." Link to comment Share on other sites More sharing options...
gert_1 Posted February 13, 2015 Share Posted February 13, 2015 Well I actually had this exact same problem last week hehe. I think the problem is that you have a second (of third etc.) paramter on which you unchecked 'Is For Prompting'. So it keeps asking for the parameter (that is not prompted) to be specified.Go to 'Parameter' section in report outline.Find the other parameter(s) you added (other than companyList)Remove them if not needed or check 'Is For Prompting' in property overview. Then anoter hint:It's Java so your Collection (Class type of your companyList -parameter) probably excists only of Strings right? If so, you can define the 'Nested Type Name' in the paramtere as 'java.lang.String'. This way you don't have to tell every paramater it's type is String :) Link to comment Share on other sites More sharing options...
dylan.snyder Posted February 13, 2015 Author Share Posted February 13, 2015 Thanks for the suggestion. Unfortunately, this is not my issue. companylist is the only parameter I created. All of the others are Jasper's default parameters, and I can't delete those. Thanks for the hint about the nested type. I will use it, once I figure out this other issue. I'm a SQL Programmer/Architect, not a JAva expert (can't you tel?), so I have a lot to learn! Link to comment Share on other sites More sharing options...
dylan.snyder Posted February 13, 2015 Author Share Posted February 13, 2015 I am the Original Poster. Here is a screenshot of my report, in case that is the culprit: Link to comment Share on other sites More sharing options...
dylan.snyder Posted February 14, 2015 Author Share Posted February 14, 2015 Thanks for the String validation on the list type. I tried it and that is a cool trick. Sadly, my issue is still there - I have scrapped the report, and tried to rebuild twice. I followed the instructions exactly as I found them at http://www.rajeshsirsikar.com/creating-a-multi-select-parameter-in-jaspersoft-studio/#comment-7248. This simply will not work on my setup on 6.0.3 on Mac 10.9. Link to comment Share on other sites More sharing options...
dylan.snyder Posted February 14, 2015 Author Share Posted February 14, 2015 I downgraded to 5.6.2 and it works now. Although, I'm not sure if reinstalling the new version set the settings back to defult or not solved this by itself. I Submitted a bug fix. I guess that's the fun/aggravation of using latest version on free software. Link to comment Share on other sites More sharing options...
gert_1 Posted February 16, 2015 Share Posted February 16, 2015 Good to hear this solved your problem. Somewhere on this forum I read that OS X Maverick caused some problems as well (but if that's the cause, it's strange that downgrading worked). Good luck with Jasper Reports, using it for a while and it's a great tool for us:) Link to comment Share on other sites More sharing options...
chicuslavic Posted March 2, 2015 Share Posted March 2, 2015 this bug has been fixed, please retry in next version Link to comment Share on other sites More sharing options...
ddaly Posted March 2, 2015 Share Posted March 2, 2015 It seems that in the current (6.0.3) version of Studio, it needs to have a java.lang.String parameter. Just adding a parameter called 'dummy' with "Is For Prompt" = true and Class Type of java.lang.String got around this problem for me. When I preview the report, I enter some value in the dummy parameter and the report to runs fine. Link to comment Share on other sites More sharing options...
horseman Posted March 27, 2015 Share Posted March 27, 2015 I confirm this is a bug in Studio 6.0.3 if you have a unique prompted parameter for your report it has to be java.lang.sting type otherwise it keeps asking for a value. Link to comment Share on other sites More sharing options...
febiwuzo Posted April 13, 2015 Share Posted April 13, 2015 Confirmed problem with integer parameter in 6.0.3.final Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now