Hi Jerome
It "should" all be documented.... for reports, dashboards and exploration... so interested in hearing your comments on the documentation, whether we can improve it in any way.
The overall guidance to which visualization to use is here:
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ug_ca_dshb.doc/wa_an_hlp_viz_change.htmland if you then pick one, like the Marimekko,
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ug_ca_dshb.doc/ca_visualization_marimekko_dash.html , it will explain what it's used for, how, steps including a small video and a link to sample data.
Mandatory data slots are marked with a red star in Cognos and the icons are telling you whether it's a dimension or measure.
For R7 of the dashboards, we are also improving the visualization even further by letting you drag&drop into data slots on the visualization to make it clear where each item belongs:
Let me know your feedback on this
Thanks
Torben
------------------------------
Torben Noer
Offering Manager, Cognos Analytics and Planning Analytics
IBM
------------------------------
Original Message:
Sent: Thu July 02, 2020 03:18 PM
From: jerome roberts
Subject: data needed to make visualizations work
Thanks for your reply and information. It looks like visualizations are made easy for Dashboards when correct fields and field types are provided. I guess one can look at the details after the visualization is created in the Dashboard, then see where the fields mapped to or maybe create in Dashboard then cut and paste to report. Why they made visualizations in report so different from creation in Dashboard is mystery to me. And why there are no obvious tutorials on creating the various types of visualizations is a mystery too. Thanks again for your link.
Jerome P Roberts
IT Specialist
Philips Oral Healthcare - Los Angeles
jerome.roberts@philips.com
image002.jpg@01CF4423.BA6A3360">
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
Original Message:
Sent: 7/2/2020 8:26:00 AM
From: Dave Chirayath
Subject: RE: data needed to make visualizations work
Hi Jerome,
I have also looked for a more clear and concise list of what data to use and how for various visualizations and not found anything outside of this tutorial from IBM: https://www.ibm.com/cloud/garage/dte/tutorial/ibm-cognos-analytics-1114-getting-started-dashboards.
I took that tutorial and then started digging into the visualizations and experimenting to find out what to use and where.
Thanks,
Dave
------------------------------
Dave Chirayath
Original Message:
Sent: Mon June 29, 2020 05:43 PM
From: jerome roberts
Subject: data needed to make visualizations work
Cognos provides a lot of visualizations to use. But I find very little information on how to use them (what data to map to the various attributes fields or suggested file/query layouts to create to use them). There are some articles, but usually for the simple visualizations. I jotted down a few of the various attributes needed to make some of the visualizations work. Some have common names some don't. Are there any guidelines on how or what to use when mapping fields from a query to the various visualization attributes like the ones below? Each pair of {} are for attributes needed for a particular type of visualization.
1 - {bars, length, color}
2 - {bubble, size, color, extra data}
3 - {rows, columns, points, heat, size, extra data}
4 - {x-axis, color, y-axis, extra data}
5 - {bars, length, width, color, extra data}
I'm looking for something that would say something like, 'usually color takes a type xxxx field and represents yyyyyy.' Usually extra data takes type xxxx field and represents yyyyyy. xxxx meaning type (numeric, alpha, unique or non-unique and yyyyy for whatever it represents).
------------------------------
jerome roberts
------------------------------