I can't believe this does not exist in Cognos or maybe I am missing something.

In a Bar Chart, how do I display cumulative Bars?

Scenario:

I have a Date Dimension in a dimensional package which has Months as the 2nd level, Year being the 1st level. Months are Jan, Feb etc.. Objective is to make a cumulative Bar Chart for one year so the 1st bar would be for Jan, 2nd bar would be for Jan+Feb and so on.

I don't see any option to make that kind of a chart.   

Any ideas?

Thanks in advance
Steve

Hi !

I need help setting up roles and permissions in SCI.
What should I do with the "Everyone" and "Anonymous" roles?
When I'm connected via Azure AD SSO, my profile appears as "not provided." Why?

Thank you MF for the reply.

I tried. But that alone is not taking out the partition condition. Instead I tried in another way which removed the partitioned extra column in the query.
Instead of hardcoded 1, I used a column "DUMMY_COUNT"; which is a dummy column in database having a value of '1' for all rows.
 Not sure why it is behaving this way. Probably a bug?
 
IF ( [Your package].[Your Query Subject].[FUND_CODE]='AA') THEN
([Your package].[Your Query Subject].DUMMY_COUNT)
ELSE (0)

Quote from: asmfloyd on 09 Oct 2025 10:01:08 PMHello,

  I have a list report with a few dimension columns (Year/IndexCode/IndexName) and a measure column. The measure I am calculating inside a variable as below:

  IF ( FUND_CODE='AA') THEN (1) ELSE (0) where I am keeping my measure's Detail Aggregation Property as "Total"
My goal is to count the number of fund_codes of value 'AA'

When I check the generated sql, it creates an additional column "FUND_CODE_u" (as below- due to which only one row will have value but others will be null ) and hence the total is not working.
Any inputs why this is occurring and how to fix?


Generated SQL:
"FUND_CODE",
        CASE
            WHEN
                ROW_NUMBER()
                    OVER(
                        PARTITION BY
                            "ACADEMIC_YEAR_DIM0"."ACADEMIC_YEAR",
                            "IDX_DIM"."IndexCode",
                            "IDX_DIM"."IndexName",
                            "FDX_DIM"."FUND_CODE"
                        ORDER BY
                            "ACADEMIC_YEAR_DIM0"."ACADEMIC_YEAR" ASC,
                            "IDX_DIM"."IndexCode" ASC,
                             "IDX_DIM"."IndexName" ASC,
                            "FDX_DIM"."FUND_CODE" ASC
                    ) = 1
                THEN
                    "FDX_DIM"."FUND_CODE"
            ELSE NULL
        END AS "FUND_CODE_u"

Thanks,

Hi,

When you create a calculation, the timing is controlled based on whether you use item names from the existing query or item names from the source pane in your expression. If you use item names from the query, the calculation happens after the default aggregation has been done (aggregate then calculate), whereas using item names from the source pane makes the calculation happen before the default aggregation (calculate then aggregate). I'm assuming you need the latter?

If so, change the expression of your calculation so that [FUND_CODE] (from the query) is replaced by [Your package].[Your Query Subject].[FUND_CODE] (from the source pane). You can just drag it in to get the fully qualified name.

Cheers!

MF.

Hello,

  I have a list report with a few dimension columns (Year/IndexCode/IndexName) and a measure column. The measure I am calculating inside a variable as below:

  IF ( FUND_CODE='AA') THEN (1) ELSE (0) where I am keeping my measure's Detail Aggregation Property as "Total"
My goal is to count the number of fund_codes of value 'AA'

When I check the generated sql, it creates an additional column "FUND_CODE_u" (as below- due to which only one row will have value but others will be null ) and hence the total is not working.
Any inputs why this is occurring and how to fix?


Generated SQL:
"FUND_CODE",
        CASE
            WHEN
                ROW_NUMBER()
                    OVER(
                        PARTITION BY
                            "ACADEMIC_YEAR_DIM0"."ACADEMIC_YEAR",
                            "IDX_DIM"."IndexCode",
                            "IDX_DIM"."IndexName",
                            "FDX_DIM"."FUND_CODE"
                        ORDER BY
                            "ACADEMIC_YEAR_DIM0"."ACADEMIC_YEAR" ASC,
                            "IDX_DIM"."IndexCode" ASC,
                             "IDX_DIM"."IndexName" ASC,
                            "FDX_DIM"."FUND_CODE" ASC
                    ) = 1
                THEN
                    "FDX_DIM"."FUND_CODE"
            ELSE NULL
        END AS "FUND_CODE_u"

Thanks,

Mark this Resolved! 

Thanks dougp, I had trouble finding that Property as I was looking for it relevant to either the Query or the Crosstab container when it is instead a Property of the Report page.

Adjust the "Group repeating cells - export to Excel" property of the Report object.

I'm using v11.2.3.

My Report Crosstab contain has nested date-parts as row headings - like Year, Month Name, and Day.

By default, the multiple occurrences of the Year and the Month Name are being "grouped" which looks fab in HTML. 

But my audience needs to be able to easily export to MS Excel for further manipulations.  The grouped row heading make it difficult on them to use the rows within Excel.

I've Googled for ideas but seems like all hints I've come across seem to want to help prevent auto aggregation of the values in the body of the Crosstab.  None of those hints influenced the formatting of the row headings.


Any other ideas anyone might be able to share???

   

Yes, Cognos is running on a windows server. We have two dispatcher servers, one content manager server, one gateway and one application server.

I found in the IBM Cognos Analytics forum other users with the same issue, and that looks particular on the scheduled reports. The rest is not a problem, is the scheduler that gets affected and you need to renew the credentials, which is kind of what I did the following day when I notice the issue.

I will revie the different suggestions on the other forum and will write here what was applied to have a generic scheduler user.

I may be wrong, but...

I'm pretty sure we've had report/schedule owners leave the organization, their Active Directory accounts destroyed, and their report schedules continue to work.

Are you running Cognos on a Windows Server?  How is the IBM Cognos service configured?  On the Log On tab in the service properties, is your account running Cognos?