Direct URL don't work properly after jasper server CE upgrade to v. 5.2

Posted on October 2, 2013 at 3:03am
Hello to all,
 
I upgraded jasper server communinty from v. 4.7 to v. 5.2.
Opening this URL:
 
http://app01:8080/jasperserver/flow.html_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2FGep&reportUnit=%2Freports%2FGep%2FGepAndamentoOperatore&DataDa=2013-09-01&DataA=2013-09-30&IdGruppo=3&IdUtente=48&j_username=jasperadmin&j_password=jasperadmin&decorate=no
 
It displays a page with the header (Page n., next page, previous page) but with nothing inside.
 
In the previous version it works fine and also in v. 5.1 test environment.
 
The report has some parameters that are not visible. 
 
I made some checks: I make those parameters visible.
 
Running the report, parameters are proposed and confirming, report works fine.
 
It can be a version bug?
 
Any suggestion will be appreciated
 
N.B.: running above URL in Chrome, opening the developer tools (F12) I found an error with this desciption: "Uncaught TypeError: Cannot call method 'find' of null "
 
JasperReports® Server
federico.bartolini's picture
federico.bartolini
38
Joined: Apr 29 2013 - 2:15am
Last seen: 8 years 6 months ago

6 Answers:

Posted on October 2, 2013 at 4:45pm

Hi,

 

I'm pretty sure there were changes to the way that some of the workflows (ie flow.html_flowId) operate in 5.2. But I can check with the UI developers and see what they have to say about changes that could effect direct URLs.

 

tkavanagh's picture
tkavanagh
14480
Joined: Jul 7 2006 - 8:54am
Last seen: 8 years 6 months ago
Posted on October 3, 2013 at 1:31am

Hi tkavanagh,

I seen that if I use direct url with reports without parameters or with visible parameters, It works fine...

eg.:

http://app01:8080/jasperserver/flow.html?_flowId=viewReportFlow&standAlone=true&_flowId=viewReportFlow&ParentFolderUri=%2Freports%2Fsamples&reportUnit=%2Freports%2Fsamples%2FAllAccounts&j_username=jasperadmin&j_password=jasperadmin&decorate=no

I think the problem is linked to not visible parameters

 

 

federico.bartolini's picture
federico.bartolini
38
Joined: Apr 29 2013 - 2:15am
Last seen: 8 years 6 months ago

.

federico.bartolini - 9 years 5 months ago
add comment
Posted on October 3, 2013 at 2:24am

More info:

Opening a direct URL with not visible parameters, the report body appear if I click the refresh button.

federico.bartolini's picture
federico.bartolini
38
Joined: Apr 29 2013 - 2:15am
Last seen: 8 years 6 months ago
Posted on October 3, 2013 at 11:52am

Hi,

A couple of things to try:

  • Use the datetime format, i.e. 1998-10-01 00:00:00
  • In the developer console does it say which js file and what line is affected?

 

geraldtruong's picture
geraldtruong
277
Joined: Mar 1 2012 - 8:24am
Last seen: 9 years 5 months ago
Posted on October 4, 2013 at 4:00am

I tryed the date format above but It's the same thing, also I found the same issue in other reports with non date type parameters

For more info about the developer console, I attach a print screen.

federico.bartolini's picture
federico.bartolini
38
Joined: Apr 29 2013 - 2:15am
Last seen: 8 years 6 months ago
Posted on October 10, 2013 at 6:51am

some suggestion?

federico.bartolini's picture
federico.bartolini
38
Joined: Apr 29 2013 - 2:15am
Last seen: 8 years 6 months ago
Feedback
randomness