Recent Posts

Pages: [1] 2 3 ... 10
1
Reporting / Re: Pivot a List to a Crosstab
« Last post by Cognos_Jan2017 on Today at 02:04:54 pm »
tjohnson3050 ...

Quote
One thing that may be throwing you, if you don't have the aggregate property set correctly on the data item, it will look like the data item is displayed twice.  This is to let you know it will create a separate item for each value in the data, instead of aggregating that item to the appropriate level based on the other items on the cross tab edges.

This is fairly long, but we stumbled onto a solution.  With your experience, we welcome your thoughts on this.

First ...
Our First (Top) Crosstab … these columns are all Correct …
Hours    = a measure
Restricted Days    = a measure
DAW Cases    = a measure
DAW Incident Rate    = a calculated Data Item
DAW    = a measure
... the last Column of “DAW Severity Rate” (a calculated Data Item)
displays data for 'DAW Incident Rate'.  We are unable to separate that
from a "conjoined" 'DAW Incident Rate'.  Changing one changes the other.

Of the 6 Column Headers, checking the “Query Expression” ALL display
([IIMS - Business Layer].[Inj/Ill No. Of Lost Time Cases]
*200000)/[IIMS - Business Layer].[Employee and Supervised Contractor Hours]
As “DAW Incident Rate” ALTHOUGH
Hours
Restricted Days
DAW Cases
DAW Incident Rate
DAW ….. ALL display the correct data.

Second ...
We added a second (bottom) the first one,
and used the same Query.  In that Crosstab, we
added the Business Group as a Row, and dragged
'DAW Severity Rate' into the Crosstab.  We set
"Calculated" as Detail Aggregation, and "Default"
as Summary Aggregation.

After doing that, the second Crosstab displayed the
Correct 'DAW Severity Rate' AND ALSO changed the
incorrect value in the first (top) Crosstab replacing them
with the Correct values.

We will learn the new Analytics Dashboard, upload an Excel
file and drag in only the first (top) Crosstab.

IF we keep the Report in the old Cognos 10.2.2 Workspace
format, we will see if the second Crosstab (while still there)
can be hidden.

tjohnson3050 ... at your convenience, those this all make sense?

TIA, Bob
2
Report Studio / Re: Repeater Table
« Last post by sjdig on Today at 11:17:02 am »
Thank you for the feedback. I'll give it a try. I was hoping to have it set as an automatic process daily that the other system will pick up without manual intervention.

I've been testing using count and rank and using those to create filters instead and do a union at the end to get the data needed so that the CSV can be scheduled and require no intervention.

Example:

Data item to count # of secondary accounts for primary accounts:
Code: [Select]
count ([Secondary #] for [Primary #])
Data item to rank secondary accounts for primary accounts:
Code: [Select]
rank([Secondary #] for [Primary #])
I had to create three placeholder data items in each query for potential null instances at the end when I created a Union.

Then, four queries with the following filters.

Query One:

Code: [Select]
count ([Secondary #] for [Primary #]) = 4 and rank([Secondary #] for [Primary #]) = 1
count ([Secondary #] for [Primary #]) = 3 and rank([Secondary #] for [Primary #]) = 1
count ([Secondary #] for [Primary #]) = 2 and rank([Secondary #] for [Primary #]) = 1
count ([Secondary #] for [Primary #]) = 1 and rank([Secondary #] for [Primary #]) = 1
All will always have at least one.

Query Two:

Code: [Select]
count ([Secondary #] for [Primary #]) = 4 and rank([Secondary #] for [Primary #]) = 2
count ([Secondary #] for [Primary #]) = 3 and rank([Secondary #] for [Primary #]) = 2
count ([Secondary #] for [Primary #]) = 2 and rank([Secondary #] for [Primary #]) = 2

Only first three instances will have a value in the second place.

Query Three:

Code: [Select]
count ([Secondary #] for [Primary #]) = 4 and rank([Secondary #] for [Primary #]) = 3
count ([Secondary #] for [Primary #]) = 3 and rank([Secondary #] for [Primary #]) = 3

Only last two instances will have a value in the third place.

Query Four:

Code: [Select]
count ([Secondary #] for [Primary #]) = 4 and rank([Secondary #] for [Primary #]) = 4
Only final scenario will have a value in the fourth place.

Then at the end in my union.

Code: [Select]
maximum([Union].[Secondary #])
maximum([Union].[Secondary #1])
maximum([Union].[Secondary #2])
maximum([Union].[Secondary #3])
Using the maximum made the data fill with a number if it existed, otherwise the maximum was a null anyway. This prevented the need for the repeater table at the page level at the end.

I know it's a bit of a workaround and I'm not quite at the point where I have everything I need, but I wanted to share another potential way of solving my problem should it arise again for someone else.

sjdig
3
Reporting / Outer Join Error
« Last post by Cognos_Jan2017 on Today at 11:06:23 am »
We have made a Table/ Query, for an Outer Join, to ensure all Conditions
and all Groups are displayed even where there would be no data for a
particular Condition / Group combination.  The Table/ Query is ...

Condition    Group
Severe         AAA
Severe         BBB
Severe         CCC
Moderate      AAA
Moderate      BBB
Moderate      CCC
Minor           AAA
Minor           BBB
Minor           CCC
Minimal        AAA
Minimal        BBB
Minimal        CCC

I am a Cognos novice.

I set New Links for both joining Condition and Group.

I tried these cardinality options ...
For left outer join (A-B)1:1-0:n A left outer join on B

For right Outer (A-B) 0:n-1:1 A right outer join on B

For full outer Join 0:n-0:n

All attempts error as ...
GEN-ERR-0016

The 'ces_currentmeasure' function is not supported in the context in which it is used.

What am I doing wrong?

TIA, Bob
4
Report Studio / Re: Repeater Table
« Last post by New_Guy on Today at 10:54:07 am »
Hi,
You can try placing a repeater table as a second column after the primary and set it up as 4 across and 1 down. How big is this report as this type of reports can create performance issues? you can use cross tab as a list column and place the attachment as cross tab column.Run the report in excel and then you have to save it in CSV format. Like Lynn said running directly in CSV will not show the attachment if it is in a repeater or a cross tab.
Good luck
New guy
5
Report Studio / Re: Repeater Table
« Last post by sjdig on Today at 09:50:19 am »
Sorry if I was unclear.

Basically, I would need the CSV to do the following.

Primary # | Attached # | Attached # | Attached # | Attached # |
12345      | 456789      | 987654      |  345678     |  876543 |
45678      | 159951      | 357753      |  852258     |   null      |
90123      | 147741      | 741147      |  null           |   null      |
10123      | 868686      | null            |  null           |   null      |

In the scenarios above, the first is driving by the primary # of 12345, which then has four secondary numbers attached. Second has driving # of 456789, when only has three secondary numbers attached, and so forth.

Attached # is one data item in the query itself, but can repeat up to a maximum of those four times.

I would need the output to produce empty rows on scenarios two through four as the system I'll be using the CSV in must account for max possible numbers of secondary numbers.

So, I would need null values to be stored as empty spaces in the CSV with a separator.

I'm just unsure as to how to accomplish this using a repeater table or if it's even possible. I have it working okay when it produces as an HTML report, but attempting to use it in any other format, it's been dropping the repeater table entirely and just giving back the driving primary number.

sjdig
6
Reporting / Re: Print button in cognos version 11 report page
« Last post by sukanya on Today at 09:46:48 am »
Thank You. I have used the same code in html item. Since, print only prints first page i have instead used drill through to the same report with run option as pdf format. User can now print in pdf.
7
Report Studio / Re: Repeater Table
« Last post by Lynn on Today at 09:24:13 am »
I'm going to piggyback on this topic as I have a related question regarding repeaters or repeater tables.

Is it possible to have an item be the driving piece of a list where the sub-item repeats horizontally across rows.

For some exposition, I'm working on a report that I need to be driven by an item that can have up to four additional items attached. However, I need to also account for null values in the instance of there being less than four items.

Primary # | Attached # | Attached # | Attached # | Attached # |
12345      | 456789      | 987654      |  345678     |  876543 |
45678      | 159951      | 357753      |  852258     |              |
90123      | 147741      | 741147      |                  |              |
10123      | 868686      |                  |                  |              |

Is this possible to do using a repeater table in some manner? I need the output to go to a CSV for use in another system. So, it does have to be in this type of formatting with a driving value and repeating any possible attached values but still accounting for nulls with empty fields.

Thanks in advance for any advice or guidance you can give,
sjdig

Not sure about all of what you are describing, but CSV output is only going to give you raw unformatted data from the query.
8
Report Studio / Re: Repeater Table
« Last post by sjdig on Today at 08:59:03 am »
I'm going to piggyback on this topic as I have a related question regarding repeaters or repeater tables.

Is it possible to have an item be the driving piece of a list where the sub-item repeats horizontally across rows.

For some exposition, I'm working on a report that I need to be driven by an item that can have up to four additional items attached. However, I need to also account for null values in the instance of there being less than four items.

Primary # | Attached # | Attached # | Attached # | Attached # |
12345      | 456789      | 987654      |  345678     |  876543 |
45678      | 159951      | 357753      |  852258     |              |
90123      | 147741      | 741147      |                  |              |
10123      | 868686      |                  |                  |              |

Is this possible to do using a repeater table in some manner? I need the output to go to a CSV for use in another system. So, it does have to be in this type of formatting with a driving value and repeating any possible attached values but still accounting for nulls with empty fields.

Thanks in advance for any advice or guidance you can give,
sjdig
9
Hi,

Just wanted to ask is this feesable, are we able to have Cognos Analytics on our dev enviroment to develop on (mostly simple report studio reports) and release to the live enviroment which is still on Cognos 10.2.2.
 
We're not allowed to have Analytics on the live enviroment just yet because of well....politics  :o

Cheers

Ryan

Hi,

No, that's not going to work. You can't deploy from a later to an earlier release. It would work the other way around (10.2.2 Dev and 11 Live). You're going to need to keep your Dev environment on 10.2.2 for now, until you can upgrade your live environment to 11.

Cheers!

MF.
10
Hi,

Just wanted to ask is this feesable, are we able to have Cognos Analytics on our dev enviroment to develop on (mostly simple report studio reports) and release to the live enviroment which is still on Cognos 10.2.2.
 
We're not allowed to have Analytics on the live enviroment just yet because of well....politics  :o

Cheers

Ryan
Pages: [1] 2 3 ... 10


           
Twittear