ProductsAI & Analytics

Last Week in the Forums: Selective Crosstab Column Total, Problems with DataSet Parameter Binding When Using a Joint DataSet

This blog series takes a look back at the past week in the forums, recalling how active they were and highlights some of the questions asked that seem to frequent the forums or other interesting topics. Forum traffic remained steady. Not as many new questions last week, but lots of conversations going about other issues. Again, thank you community members for answering questions. It is a great help!

The first question for this week was about adding only values from certain columns of a crosstab and not including other column values that are present in the crosstab. The solution to this was to grab the column dimension name and figure out if it is one that you want to add, if so you add the value from the crosstab cell to your running total you’re keeping in a variable. You then can display this variable in the “total” area at the end of the row. An example is in the thread, but I will make a devShare entry to use the classic models database and link it in here when it’s done.

The next question I’ll cover is about a problem with linking the dataSet parameter of an inner table with a row value of the outer table if the inner table uses a joint dataSet. The question asker was using BIRT 2.5.0. I tried recreating their issue with a simple table and embedded table tied to a joint dataSet and it worked fine. The problem happened when I had another report item tied to the joint dataSet. When this was done, the dataSet parameter binding did not refresh, it returned the first set of values every time. I then went and tried this same thing in BIRT 2.6.0 and it worked as expected, so the end result was the question asker had to upgrade to the newer version to get around this apparent bug.

The last item I’ll cover this week is a question where the poster was getting an extra, blank page at the end of their report. What was figured out was that the poster had defined a value for the grid height that was too large for the usable area of the page. This resulted in the second, blank page. So, if you ever end up with a blank page at the end of your report, be sure to check your heights/widths of your report items and also remember to take into account the padding that there might be.

As I say every week, this is just a small sample of what went through the forums this past week. For more questions and answers that have been posted, check out the forums. As always, if you have a question, feel free to ask it, and if you see a question you know the answer to or have a similar experience to, feel free to post an answer or comment. 

Show More


OpenText is the leader in Enterprise Information Management (EIM). Our EIM products enable businesses to grow faster, lower operational costs, and reduce information governance and security risks by improving business insight, impact and process speed.

Related Posts

Back to top button