HomeНаука и техникаRelated VideosMore From: Jaspersoft Embedded BI

Conditional display of a column based on its data

25 ratings | 13311 views
This video how-to shows basic concepts around conditional display of a column in a Table object, based on its data. This example is based on Jaspersoft Studio 6.0.1 but it should work (possibly with little editing) on recent releases, such as 5.x. See: http://community.jaspersoft.com/wiki/conditional-display-column-based-its-data
Html code for embedding videos on your blog
Text Comments (6)
Poonam K (2 months ago)
thank you so much... that was indeed helpful :)
Software Box (1 year ago)
Nice tutorial... I would like you to read also this post and get me the quality level of this post. I think you are the right person who can get me the right feedback. Here is the link: https://www.pinterest.com/learnprogramming/learn-jasper-reports-ireport/ Thanks
dipti pradhan (1 year ago)
"Print When Expression" is it work in case of dashboard
Sourav Rabbi (2 years ago)
thanks boss.......by the help of your this video,,,,,a biggest problem was solved by me ..... not like this video,,,,,,but i take a concept from here,,,,,,,,,thank you sooo much,,,,bro
Linden (3 years ago)
does this still work if the table is not in the summary band? I assume you put it there so it only evaluates at the report level. wondering if its possible to set the evaluation time of the print when condition in any kind of band somehow also I'm wondering if this would still work if you have a larger number of rows returned from the query. I see you put it at limit 20, was that intentional? I seem to recall that the summary band doesn't paginate like a regular detail band
TIBCO Software (3 years ago)
Hi Linden, thanks for your questions! Answer to Q1: We have just tested it with the Table in the Title Band and it works. The main report query always runs before the queries in the other datasets. Answer to Q2: The evaluation time applies at a dataset level (either in the main report or the sub-datasets). Answer to Q3: Very good point! It would still work, but there will be a performance impact as you run the query twice (that obviously applies to any situations where you run a query twice instead of once). If this functionality is really required and the dataset is large, we recommend using some datastore-specific optimization (depending on the technology you're using) instead of the generic COUNT example we've shown. The LIMIT of 20 was intentional to simplify the example. Answer to Q4: Again, excellent point! The summary band would paginate differently indeed. Note that in this case, if you make sure the main report query returns one row only, you could still put the Table in the Detail Band (we just tested it and it works). If you have any other questions, please do let us know! :)

Would you like to comment?

Join YouTube for a free account, or sign in if you are already a member.