If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Workspace Cache

Started by andy_mason_84, 24 Aug 2015 04:38:56 AM

Previous topic - Next topic

andy_mason_84

Hi All,

So I have created a set of 'widgets' and created a dashboard with several tabs.  The dashboard runs fine so all is well until we recently pointed Cognos to another Database.  This database has different data in.

The dashboard widgets in Workspace now render as 'No Data Available'.  Now this isn't the case as if you run the widget in Report Studio it has data.

Clearing the cache in my browser (IE 8 and 9) doesn't make a difference.  The filters in Workspace update to have the new data in and all options are selected so this cannot be the problem.

If i drag the same widget on again then it renders with data but obviously every time we point Cognos to a new DB we cannot recreate the dashboards from scratch.

Anyone else experienced his kind of behaviour and have any advice/fixes/fudges to make it work?

Using 10.2.1 FP8 w/SQL Server

Cheers,

AM

bdbits

Cognos is very aggressive with caching these days, sometimes annoyingly so.

Did you use the refresh icon on the toolbar? It is almost in the middle of the toolbar, the ying-yang-with-arrowheads symbol, tooltip "Refresh Workspace". Also available on the first pull-down menu.

I am kind of curious, if you don't mind - why the on-going need to switch source databases?

andy_mason_84

It is a development environment so we are always loading datasets into different databases and switching it, obviously in the "real world" this may not be an issue.

The Refresh button didn't work, the widgets still came back as No Data Available.

We found out by deselecting all and reselecting all in the filters and applying the changes this actually did kick them back into life.  Sometimes our datasets are completely unrelated so what is in the Product Group Filter in one dataset isn't what is in another, so it seems that workspace selects all the new items in the filters but doesn't actually apply them or something to that nature.

So we have a fudge for now, just seems odd behaviour even if we are switching DB's.