COGNOiSe.com - The IBM Cognos Community

IBM Cognos 10 Platform => Cognos 10 BI => Active Reports => Topic started by: shelby435 on 18 Oct 2015 08:24:52 PM

Title: No data for Visualization breaks Active Report?
Post by: shelby435 on 18 Oct 2015 08:24:52 PM
I have seen this a few times now. If there is no data in a table that is used for a visualization, the MHT fails to render and throws an error. I couldnt reproduce the error at the time of writing this but I remember it was some sort of 'riot.html' error.

This would normally not occur, but since I am doing development the same time as the database folks are, I have seen this quite a bit.

Has anyone else seen this? Is there a setting somewhere I dont know about that might be causing this error?
Title: Re: No data for Visualization breaks Active Report?
Post by: farlein on 30 Oct 2015 09:05:57 AM
Not sure whether you used a customized visualization. The original visualization graphs work fine to me if there is no data, and they just show blank graphs. I modified a visualization from linear scale to log scale, and this graph gives an error when no data is available. I understand the reason, which is log(0) is infinite negative.
Title: Re: No data for Visualization breaks Active Report?
Post by: shelby435 on 03 Nov 2015 09:24:05 AM
Yeah, they were customized. Was there any fix for that?
Title: Re: No data for Visualization breaks Active Report?
Post by: MFGF on 05 Nov 2015 02:34:41 AM
Quote from: shelby435 on 03 Nov 2015 09:24:05 AM
Yeah, they were customized. Was there any fix for that?

The answer is to get the person who customised them to look at the code and figure out why they break when no data is present. Farlein gave you a pointer - in his case the logarithmic scale was the culprit, but there could be any number of reasons why the visualizations break.

If you look at the question above from our perspective, all we can see is this situation:

"We took some code that works fine. We customised it. Now it doesn't work fine. How do we fix it?"

Only the developer who changed the visualization code would be able to provide useful detail on what to do to fix this.

MF.