cognos-bi | 易学教程

Save Cognos report as .xlsx on local drive

阅读更多关于 Save Cognos report as .xlsx on local drive

问题 I'm trying to figure out if it is possible to save a Cognos report as a .xlsx file to a local drive, and how to do it. We are using CA 11.1.6, on-premise. Who can help me out? Thanks in advance, Edwin 回答1: You do it via the run as menu option. If you are editing a report, there's a button for run as. If the report is saved, it exists as a menu item on the context menu. https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ug_cr_rptstd.doc/c_cr_rptstd_intrd_producing

Convert IBM Cognos SQL which contains a filter to Microsoft SQL Server Query

阅读更多关于 Convert IBM Cognos SQL which contains a filter to Microsoft SQL Server Query

问题 I'm trying to convert IBM Cognos SQL which contains a filter to Microsoft SQL Server Query. I tried to apply the filter in the Microsoft SQL Server Query, but it didn't work. Here the IBM Cognos Query: IBM Cognos SQL select rank() over ( at client__iacode.ia_code order by XCOUNT(client_document.client_document_id for client__iacode.ia_code ) desc nulls last) as Rank_IA, client__iacode.ia_code as IA_Code, client__iacode.ia_short_descr as IA_Short_Descr, XCOUNT(client_document.client_document

XQE-GEN-0018 QUERY SERVICE INTERNAL ERROR HAS OCCURRED, PLEASE SEE THE LOG FOR DETAILS WHEN QUERYING DMR

阅读更多关于 XQE-GEN-0018 QUERY SERVICE INTERNAL ERROR HAS OCCURRED, PLEASE SEE THE LOG FOR DETAILS WHEN QUERYING DMR

问题 I am getting error as XQE-GEN-0018 QUERY SERVICE INTERNAL ERROR HAS OCCURRED, PLEASE SEE THE LOG FOR DETAILS. We have published our CQM package to DQM package . When I point to old package which has type compatible , report run both in Cognos 10 and 11 environment but when I point my report in Cognos 11 environment to Dynamic Type Package , report throws error after I submit prompt values. Any help is highly appreciated. 回答1: The first thing you ought to do is go to the log directory, open

Cognos Report Studio (case statement) - Syntax error

阅读更多关于 Cognos Report Studio (case statement) - Syntax error

问题 I have a case statement in Cognos report studio in which if the date is 1st of the current month of previous year then it should fetch data for last whole month (1 to the last date) data of the previous year. I think it is a syntax error. Below is the code that I'm sharing.Thanks in advance! Please let me know in case of concerns. case when [Corporate Calendar_BL].[Receive Date Details].[Receive Date - RD] = _first_of_month(_add_years(current_date,-1)) then [Corporate Calendar_BL].[Receive

Cross-Tabulate Non-Numeric Data in Cognos BI

阅读更多关于 Cross-Tabulate Non-Numeric Data in Cognos BI

IBM Cognos Report Studio: Arbitrary errors when using IF / CASE on an TM1 cube

阅读更多关于 IBM Cognos Report Studio: Arbitrary errors when using IF / CASE on an TM1 cube

问题 I am having some trouble with an IF / CASE expression when consuming a TM1 cube in Report Studio. I am "filtering" a crosstab with a tuple function that includes an element from the "branch" dimension. The users can navigate through this branch hierarchy by a value prompt I have made. Hence, the users have requested that they at every time can see where they are in the branch hierarchy (i.e. see the path from root to current node). I have therefore tried to make two query expressions which at

Cognos Calculate Variance Crosstab (Dimensional)

阅读更多关于 Cognos Calculate Variance Crosstab (Dimensional)

问题 This is very similar to Cognos Calculate Variance Crosstab (Relational), but my data source is dimensional. I have a simple crosstab such as this: | 04-13-2013 | 04-13-2014 --------------------------------------- Sold | 75 | 50 Purchased | 10 | 15 Repaired | 33 | 44 Filter: The user selects 1 date and then we include that date plus 1 year ago. Dimension: The date is the day level in a YQMD Hierarchy. Measures: We are showing various measures from a Measure Dimension. Sold Purchased Repaired

Cognos Calculate Variance Crosstab (Dimensional)

阅读更多关于 Cognos Calculate Variance Crosstab (Dimensional)

This is very similar to Cognos Calculate Variance Crosstab (Relational) , but my data source is dimensional. I have a simple crosstab such as this: | 04-13-2013 | 04-13-2014 --------------------------------------- Sold | 75 | 50 Purchased | 10 | 15 Repaired | 33 | 44 Filter: The user selects 1 date and then we include that date plus 1 year ago. Dimension: The date is the day level in a YQMD Hierarchy. Measures: We are showing various measures from a Measure Dimension. Sold Purchased Repaired Here is what is looks like in report studio: | <#Day#> | <#Day#> --------------------------------------

In cognos, could we avoid an optional prompt asking a value when its parameter is used in a data item in a query?

阅读更多关于 In cognos, could we avoid an optional prompt asking a value when its parameter is used in a data item in a query?

问题 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? 回答1: 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

In cognos, could we avoid an optional prompt asking a value when its parameter is used in a data item in a query?

阅读更多关于 In cognos, could we avoid an optional prompt asking a value when its parameter is used in a data item in a query?

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? 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()