TechnologiesAIProductsAI & Analytics

Last Week in the Forums: Replacing Labels in a Chart with a ‘Key’ DataSet, Avoiding Group Header Row Being Last Line in a Page

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. The forums are as busy as ever. There are also more people supplying answers than I’ve seen in a while. Thanks to those members who are helping answer questions. It is a great help to the community!

The first topic I’ll discuss from last week in the forums is about replacing the labels in a chart using values from a “key” dataSet. The poster had a chart that used one dataSet and a second dataSet that offered a “key” that they’d like to change their axis labels to. One way to do this would be to use a joint dataSet to get the “key” values into the dataSet you’re using for the chart. Another way is to use persistent global variables to replace the values. You can set them in the onFetch of the key dataSet and recall them in the chart script. There are examples in the forum post.

The next topic this week is about avoiding having a group header row as the last line of a page. The poster was having an issue with header rows for groups being the last line of a page with no data under it. In 2.5.x, this can be solved with the page break inside setting of “avoid” being chosen in the group editor. If you’re using an earlier version, however, you have to do this on your own. In the thread, there is an example posted that shows a way to use scripting and group aggregations to avoid this issue.

The last topic I’ll cover this week is about using script to add a detail row to your table. The poster had an existing table in their report that they wanted to add extra detail rows to in certain scenarios. They were having a problem with the RowOperationParameters that need to be passed to add a row. The solution is that the first number should always be a 2. The second parameter is the groupID. This is -1 if you’re not dealing with a group row. The last number is the destinationID for the row. This is a 0 based value. If you have a single detail row already, you’d want this value to be 1 to add a row. If you have 2 detail rows already, you’d want it to be 2, and so on.

Again, 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