ProductsAI & AnalyticsOEM

Showing Percentages in a Pie Chart, Limiting an Embedded Element with an Outer Element Value

Last Week in the Forums – 8/6/12

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 continues to fluctuate during the summer, which is expected, but they’re still fairly busy each week. Keep the good questions and answers coming. As always, thanks to those users who help answer questions! It is a great help to the community!

I’ve decided to change the format, slightly. I’ll continue to focus on a couple posts, in more detail, as I’ve always done. Instead of covering an unanswered post, in detail, I’ll just list several unanswered posts, from the previous week, in hopes that a few answers will come out of the extra publicity, for them. I’ll also list some other questions that have been answered, so this post can be a better summary of the forums, in each week. This hope is that this will aid community members in finding past posts that answer their questions. Feel free to let me know if you like or hate the changes.

The first topic I’ll discuss, from last week, is about showing a percentage in a pie chart. The issue was that the dataSet consisted of a jobID and

a status column. The status column was either “Complete” or blank. The solution given was to create a computed column to give the blank rows a value of “Not Complete”, then, to use the computed column for the category and the count of jobs for the slice value. To get the percent, the series label needed to be changed from Value Data to Percentile Value Data. This can be done in the chart wizard. An example is posted in the thread.

The last detailed description post, for this week, is about limiting embedded tables with an outer table value. The issue is, when you embed a table, how can you limit the embedded table with a value from the outer table. There are a couple possibilities, here. One, if you’re using SQL, is to use a dataSet parameter in your inner query, and use the dataSet parameter binding option, which can be found on the binding tab of the inner table, to pass row._outer[“myoutertablevalue”] directly to the inner query. Another available way, if you’re not using SQL, is to use this value in a filter on the inner table, to limit the data. An example of the data set parameter binding way can be found in the thread.

Here are a few more:

And a few unanswered ones:

If you have a suggestion or solution for any of these, please post in the thread.

Thanks for reading this week’s blog. 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