Should I create an active, standard, or dashboard report?

[pacificbeavs]

I need to create a dashboard-looking report, and I can't decide the best way to proceed.

Standard reports are straightforward, but lack drill-down capabilities without the proper package structure.  They also lack the interactivity.

Active reports have been my go-to for dashboard-like reports.  However, they have plenty of interactivity, but get complex to maintain and lack the newest visualizations.  Any drill-downs are artificially created.

Dashboards seem great, but they don't seem to have as much flexibility (can't modify query) unless you create a custom data module from the package.  Navigation paths are fantastic for drill downs.  The dashboards I've created thus far are incredibly slow (i.e. a couple of minutes to render a different tab of visualizations).

That said... none of these seem to be the perfect solution.  What do you recommend for a dashboard?  The intent of this dashboard is to be viewed by management (all have Cognos licenses, so running it in browser is okay).

[dougp]

That would depend on your requirements...

Building dashboards against packages (boiling the ocean) is slow.  I always use a data module or data set to feed a dashboard.  That said, I rarely use dashboards.  My users usually want something that looks like a dashboard -- to print.   :P

[pacificbeavs]

That would depend on your requirements...

Building dashboards against packages (boiling the ocean) is slow.  I always use a data module or data set to feed a dashboard.  That said, I rarely use dashboards.  My users usually want something that looks like a dashboard -- to print.   :P

Thanks, makes sense.

I would like to create a dashboard from three different packages.  Would you advise creating three separate data sets, and using those three separate data sets in my dashboard (most likely three separate tabs)?  Or would there be any reason for me to create a data module(s)?  I do not plan on joining any of that information together since it's unrelated, so presumably that would rule out the need to create a data module.

[MFGF]

Thanks, makes sense.

I would like to create a dashboard from three different packages.  Would you advise creating three separate data sets, and using those three separate data sets in my dashboard (most likely three separate tabs)?  Or would there be any reason for me to create a data module(s)?  I do not plan on joining any of that information together since it's unrelated, so presumably that would rule out the need to create a data module.

Hi,

If the data sets don't need to be joined then there's no absolute need for a data module. Other questions to consider that might impact your data module decision are:
Will the data be used in multiple dashboards?
If so, is there a requirement to add custom groups, navigation paths, calculations, filters etc?

If the answer to the above is yes, or maybe, then creating a data module would save you work in the long run. You'd be doing the work once in the data module rather than repeating it multiple times in different dashboards.

A couple of tips on using data sets too:
- If you plan to filter on an item commonly, you'll get better performance if you sort the data set on that item as you create it.
- If you are using Cognos Analytics 11.0.x, try to keep each data set to 2 million rows or fewer to get snappy performance.
- If you are using Cognos Analytics 11.1.x, try to keep each data set to 8 million rows or fewer to get snappy performance.

Cheers!

MF.

[pacificbeavs]

Thanks MF - that's very helpful!

[pacificbeavs]

Hi,

If the data sets don't need to be joined then there's no absolute need for a data module. Other questions to consider that might impact your data module decision are:
Will the data be used in multiple dashboards?
If so, is there a requirement to add custom groups, navigation paths, calculations, filters etc?

If the answer to the above is yes, or maybe, then creating a data module would save you work in the long run. You'd be doing the work once in the data module rather than repeating it multiple times in different dashboards.

A couple of tips on using data sets too:
- If you plan to filter on an item commonly, you'll get better performance if you sort the data set on that item as you create it.
- If you are using Cognos Analytics 11.0.x, try to keep each data set to 2 million rows or fewer to get snappy performance.
- If you are using Cognos Analytics 11.1.x, try to keep each data set to 8 million rows or fewer to get snappy performance.

Cheers!

MF.

I just realized I can't seem to figure out how to create a navigation path in the data module, or filter for that matter.  Attached is a screenshot of my data module, and as you'll see I can't get to the fields inside of the package to filter them or create a navigational path against them. How do you recommend I proceed?  Within the "Claims Sets" there are four different pre-filtered "sets" of data.

[MFGF]

I just realized I can't seem to figure out how to create a navigation path in the data module, or filter for that matter.  Attached is a screenshot of my data module, and as you'll see I can't get to the fields inside of the package to filter them or create a navigational path against them. How do you recommend I proceed?  Within the "Claims Sets" there are four different pre-filtered "sets" of data.

Hi,

You can't bring a package directly into a Data Module and add calculations/filters/navigation paths etc to the package. The approach is to create a data set from the package, then bring that data set into your data module. Within your data module you can then see the data items in the data set, and add whatever filters/calcs/navigation paths etc you like.

Cheers!

MF.

[pacificbeavs]

Great, thanks!

[pacificbeavs]

Hi,

You can't bring a package directly into a Data Module and add calculations/filters/navigation paths etc to the package. The approach is to create a data set from the package, then bring that data set into your data module. Within your data module you can then see the data items in the data set, and add whatever filters/calcs/navigation paths etc you like.

Cheers!

MF.

I made some progress with the data set, and then I created a data module against the data set.  I decided to add a few more fields to the data set, but it appears I can't refresh the data module.  I found an old thread that discussed a workaround, but I wanted to double check and see if there's an easier way to refresh the data module with the new data set columns.  Do you know the easiest way to do this?  I may just create a new data module... but that seems like a big to-do just to add another field.

Earlier you asked "Will the data be used in multiple dashboards?" - is there a downside to using a single data set against multiple dashboards?

If all I need is navigational paths, is there much of a difference between using a data set and then creating the navigation path in the dashboard, versus creating the navigation path in the data module and then creating a dashboard from the data module?

I really appreciate all the valuable information you're providing!

[MFGF]

I made some progress with the data set, and then I created a data module against the data set.  I decided to add a few more fields to the data set, but it appears I can't refresh the data module.  I found an old thread that discussed a workaround, but I wanted to double check and see if there's an easier way to refresh the data module with the new data set columns.  Do you know the easiest way to do this?  I may just create a new data module... but that seems like a big to-do just to add another field.

Earlier you asked "Will the data be used in multiple dashboards?" - is there a downside to using a single data set against multiple dashboards?

If all I need is navigational paths, is there much of a difference between using a data set and then creating the navigation path in the dashboard, versus creating the navigation path in the data module and then creating a dashboard from the data module?

I really appreciate all the valuable information you're providing!

Hi,

I'm using 11.1.3 and I was able to add a column to a data set, refresh the data set, then go into my data module and use the "Add more tables" option to bring the new column in.

There is no downside to using a data set in multiple dashboards I'm aware of - it's just a data source.

The benefit of defining navigation paths in a data module vs in a dashboard is really only apparent if you have multiple dashboards. You're defining things once in the data module, whereas if you have many dashboards you'll end up defining the navigation paths over and over again, which is extra work and also open to inconsistencies if you forget and define them differently in one dashboard vs another.

Cheers!

MF.

[pacificbeavs]

Hi,

I'm using 11.1.3 and I was able to add a column to a data set, refresh the data set, then go into my data module and use the "Add more tables" option to bring the new column in.

There is no downside to using a data set in multiple dashboards I'm aware of - it's just a data source.

The benefit of defining navigation paths in a data module vs in a dashboard is really only apparent if you have multiple dashboards. You're defining things once in the data module, whereas if you have many dashboards you'll end up defining the navigation paths over and over again, which is extra work and also open to inconsistencies if you forget and define them differently in one dashboard vs another.

Cheers!

MF.

I'm guessing there's an easy explanation, but I can't seem to complete the "Add more tables" solution.  Please see attached - the "Ok" button is grayed out no matter where I click/refresh.  Thanks!

[MFGF]

I'm guessing there's an easy explanation, but I can't seem to complete the "Add more tables" solution.  Please see attached - the "Ok" button is grayed out no matter where I click/refresh.  Thanks!

Hi,

Sorry - I forgot the key step - you need to remove and re-add the data set from/to the data module.

The steps I took were:
1. Edit the data set and add the new columns.
2. Save the data set.
3. Close the data set.
4. From the portal, use the ellipsis next to the data set and choose "Refresh"
5. Edit the data module.
6. Remove the data set.
7. Use the "Add more tables" option.
8. Add the data set back to the data module.

Cheers!

MF.

[pacificbeavs]

That worked - thanks!