Impact Analysis

[dougp]

Currently using 11.2.4

I want to identify which reports could be broken by removing a column from a database.  My current effort involves a data source that is only exposed to Cognos Analytics through packages from Framework Manager models.  Is there a way to do this using the tools at hand (Cognos Administration, Framework Manager, CMTools, Audit Extension) or will I need to resort to either getting licenses for products from BSP, Motio, or similar or developing my own solution using the SDK and REST API?


I can imagine that at some point I will need to perform the same inspection involving data modules.  But that's a question for another day.  The great thing about data modules is that this is one area where the REST API is already functional.

[MFGF]

Currently using 11.2.4

I want to identify which reports could be broken by removing a column from a database.  My current effort involves a data source that is only exposed to Cognos Analytics through packages from Framework Manager models.  Is there a way to do this using the tools at hand (Cognos Administration, Framework Manager, CMTools, Audit Extension) or will I need to resort to either getting licenses for products from BSP, Motio, or similar or developing my own solution using the SDK and REST API?


I can imagine that at some point I will need to perform the same inspection involving data modules.  But that's a question for another day.  The great thing about data modules is that this is one area where the REST API is already functional.

Hi Doug,

You can do this from within Framework Manager (before publishing the changed package, obviously!) :-) Michael detailed how to do this in the post below:

https://www.cognoise.com/index.php?topic=27866.0

It's the second step of "Find report dependencies" that you need here, by the looks of things.

Cheers!

MF.

[dougp]

I knew about that (, said Doug, sheepishly) because I have used it before.

You know, at my age the hearing is the second thing to go.  I can't remember what the first thing was.

[dougp]

Selecting a query subject or query item and using Tools | Find Report Dependencies will also work.

One thing to watch out for:

Both Analyze Publish Impact... and Tools | Find Report Dependencies identify things that you would see in places like Data Items or Detail Filters.  But since the relationships between query subjects are technically not in the reports, removing something like a bridge or grouping table (used only for relationships) won't be identified as something that has an impact.  I suppose that database changes should not be harming how logical relationships work, so maybe that's OK.

For example Report X includes parts that require the SQL to look like
FROM factA INNER JOIN bridgeB INNER JOIN dimC
and I remove table bridgeB and make the relationship work directly between tables factA and dimC, there technically should not be a problem.  But what if I got it wrong?  What reports should I watch to see if I messed this up?  FM won't tell me.  I suppose that, logically, I can assume that anything using dimC must be checked.

[MFGF]

I knew about that (, said Doug, sheepishly) because I have used it before.

You know, at my age the hearing is the second thing to go.  I can't remember what the first thing was.

Welcome to my world, sir! :-D

Thanks for the further updates also - useful info!

Cheers!

MF.