COGNOiSe.com - The IBM Cognos Community

IBM Cognos Analytics Platform => Cognos Analytics => Reporting => Topic started by: robblob on 20 Nov 2019 10:55:54 AM

Title: 11.0 Clustered Bar in Active Report axis label font ellipsis
Post by: robblob on 20 Nov 2019 10:55:54 AM
I have a clustered bar chart in an active report that refuses to display the axis label without ellipsis, regardless of how wide I make the chart or how small I make the font.  The text value isn't even that large that I'm trying to display.  The largest value is 10 characters.  I have another clustered bar in the same deck that has a much larger label that displays the entire contents with no problem whatsoever.  I've checked every property I know to check and nothing seems to fix the issue.  I've even checked the data to see if there are trailing spaces or other characters...nothing.

To make matters worse, some of the labels are displayed in full, yet the ellipsis is still displaying.  I'm at a loss.  Any suggestions?  I uploaded a picture of the ellipsis I'm talking about on the axis in case I didn't explain it well enough.
Title: Re: 11.0 Clustered Bar in Active Report axis label font ellipsis
Post by: robblob on 20 Nov 2019 04:37:25 PM
My boss was able to fix this.  This is a widespread issue with Cognos when using data modules/data sets.  We have been having issues with data being stored in a NVARCHAR format within Cognos that basically says there is an undefined length on the field, which causes Cognos to throw an error.  So Cognos creates an error that it can't handle basically.  Thanks, Cognos!

This situation wasn't exactly the same though, but had the same solution.  The column that was causing an issue was defined as CHAR(20), making it seem like there were more spaces, causing the ellipsis to appear.  We resolved the issue by trimming and casting it to varchar.

Beware of how Cognos defines text fields in data sets and data modules.  We have noticed this particularly in 11.1 R4, but may be an issue in other versions as well.  This has been communicated to IBM, so they're at least aware of the issue.