Cognos 8.3 无数据内容问题
从 8.2 升级到 8.3 并测试新的无数据内容功能。 如果返回结果,报告将按顺序排列。 不会出现“无数据”消息。 但是,如果我们测试报告(传递参数,期望没有结果),我们会返回一个空白页面(pdf、html、excel 输出)。 甚至页眉或页脚也不会出现在页面上。 并且“无数据内容”消息也不会出现。
我们使用 Oracle SQL 生成非常复杂的报告,并且在大多数情况下,标题内容链接到 SQL 语句以呈现数据库的输出并列出传入的参数。问题似乎与嵌入的数据对象有关,即我们有嵌入表对象中的列表对象。 我已经尝试去除多余的层,但到目前为止没有成功。
在8.2中,我们使用样式变量,即RowNumber()=0或RowNumber()为null来有条件地隐藏报表正文中的数据对象。 我们从未使用任何条件来隐藏或显示页眉或页脚,现在在 8.3 中这似乎是一个问题。
这看起来是 8.3 中非常有用的增强功能,但我们还没有让它发挥作用。 有什么想法或建议可以尝试吗?
感谢您阅读本文。 我很感激任何建议。
乔
Upgrading from 8.2 to 8.3 and testing out the new No Data Content functionality. Report looks in order if results are returned. The No Data message does not appear. However if we test the report (pass in parameters expecting no results), we are returned a blank page (pdf, html, excel output). Not even the header or footer appear on the page. And the No Data Content message does not appear as well.
We have very complex reports using Oracle SQL and in most cases the Header content is linked to a SQL statement to render output from the database as well as list the parameters passed in. The issue seems to be related to embedded data objects, i.e. we have a list object embedded within a table object. I've tried stripping out the extra layers with no success thus far.
In 8.2 we used style variables, i.e. RowNumber()=0 or RowNumber() is null to conditionally hide data objects in the body of the report. We've never used any conditions to hide or display the header or the footer and in 8.3 now this seems to be an issue.
This seemed like such a useful enhancement in 8.3 but we haven't gotten it working yet. Any thoughts or suggestions to try?
Thanks for reading this. I appreciate any advice.
Joe
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
从 8.2 升级报告时我们遇到了同样的问题 => 8.4. 我们将其作为错误报告给 Cognos —— 不确定他们是否为其分配了错误跟踪器 ID,但我们的印象是它不会很快得到修复。 (显然,如果它存在于8.3中并且已经被延续到下一个版本,那么它不是一个高优先级。)
很抱歉,我目前没有关于如何修复它的答案,但我正在计划下周研究解决办法。 我将用我想到的任何想法来编辑这篇文章。
更新:
不确定这是否是 8.3 的可用功能,但在 8.4 中,数据容器(列表、块等)有一个新的“无数据内容”属性。 将此值设置为 yes 会在页面顶部创建两个选项卡,一个用于返回数据时显示的页面,另一个用于在未找到记录时显示的页面。 您可以自定义要使用第二页显示的消息。 实际上很酷,但是隐藏在文档中。
希望有帮助。 如果仍有问题,请查看索引主题“无数据 > 指定数据容器显示的内容”。
We ran into this same problem when upgrading reports from 8.2 => 8.4. We reported it to Cognos as a bug -- Not sure if they've assigned a bug tracker id to it, but we got the impression it wasn't going to be fixed soon. (Obviously, if it exists in 8.3 and it has been carried forward to the next version, it's not a high priority.)
I'm sorry I don't have an answer at the moment on how to fix it, but I was planning to look into work arounds next week. I'll edit this post with any ideas I come up with.
UPDATE:
Not sure if this is an available feature of 8.3, but in 8.4 there is a new "No Data Contents" property for data containers (lists, blocks, etc.). Setting this value to yes creates two tabs at the top of the page, one for a page to be displayed if data is returned, and another for instances when no records are found. You can customize a message to be displayed using that second page. Pretty cool, actually, but buried in the documentation.
Hope that helps. If you still have problems, check out the Index topic "no data > specify what appears for a data container."
是的,似乎返回了一个空白的 pdf...但实际上,如果没有数据,cognos 查看器会在第二个提示页面出现错误。 页眉和页脚以及不需要数据渲染的项目......也没有显示。
这存在于 8.2 中,我们总是能够做一些工作来让它至少显示出来。 现在在 8.3 中似乎更加流行。
我也想要一个解决方案! 停! >_<
编辑:似乎有一个轻微的解决方法是在 8.3 中创建一个新报告并复制每个组件,从查询开始...然后是变量..然后是页面上的对象..然后是页面集和主详细信息关系。 为了简单起见,按这个顺序。 从本质上讲,在 8.3 中从头开始重新创建报告似乎可以解决该问题。
这适用于我们大约 90% 的报告。
yea it appears that a blank pdf is returned... but in fact the cognos viewer bugs out at the second prompt page if there is no data. Headers and footers and items in which didnt need data to render ... as not showing up as well.
This existed in 8.2 and we were always able to do some sort of work around to get it to atleast show. Seems much more prevalent in 8.3 now.
Id like a solution on this as well! halp! >_<
Edit: seems a slight work around is to create a new report in 8.3 and copy each component starting with queries... then variables.. then objects on the page.. followed by page sets and master detail relationships. in that order for simplicity. Essentially recreating the report from scratch in 8.3 seems to fix the problem.
This works for about 90% of our reports.