Actually, I'm working in Cognos 10.1 report studio. In my report, I have two prompts, one is optional and another prompt is required. I've used both the prompt parameters inside the data item for some condition. So, the optional prompt has also turned to required. What should we do to avoid this?
相关问题
- Convert IBM Cognos SQL which contains a filter to
- Cognos 8 Query to find all Report and Column Names
- Cognos popout label for selected item
- Migration from Cognos cubes to SSAS
- How do I update the password for a Cognos Data Sou
相关文章
- 在Java中解析高度嵌套的XML DOM不(Parsing Highly Nested XML wi
- IBM Cognos报表工作室:使用IF / CASE当任意错误上的TM1多维数据集(IBM Cog
- 如何更新的COGNOS数据源的密码?(How do I update the password fo
- 我怎么可以拆分页脚/头到多个单元格在Cognos?(How can I split a footer
- 我怎样才能在COGNOS查询表达式的当前日期?(How can I get the Current
- 转换Cognos报告到SSRS,什么XSUM命令呢?(Converting Cognos repor
- Cognos popout label for selected item
- Migration from Cognos cubes to SSAS
We can use #prompt()# for this. Usually, #prompt()# is used to deliberately force the parameter to hold some value. Instead of using the parameter directly, we should use the #prompt()#.
For example,
Suppose, ?Parameter1? is used in a data item and it holds a integer value, replace it with a #prompt()# like this #prompt('Parameter1','integer')#.
Suppose, if the condition is like
it should be,
If we use #prompt()#, we can use the parameter inside the data item, without affecting the prompt's usage.
Regular Prompt Used in Data items calculations/logic always become required regardless because the data item in query must be presented and is not optional as in presentation items so the calculation has to resolve. Like the other poster stated in comes prompt macros ## which truely serves in my opinion 2 real-world purposes and argueable some others that we won't talk about.