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

How do I refresh visualisations in Reporting?

Started by Blue, 01 Nov 2016 05:07:54 PM

Previous topic - Next topic

Blue

G'day guys

I have several visualisations in a complex dashboard built with the Reporting tool.
The visualisations are being tweaked based on user feedback.  But once I reimport the changes visualisation in to CA11.0.4 I don't see the new version.
How, other than deleting and re-adding the viz to the report, do I refresh the viz so I can see the changes?

Cheers,

Blue
Robert Edis
Principal
Robert Edis Consulting
Rotorua, New Zealand

MFGF

Quote from: Blue on 01 Nov 2016 05:07:54 PM
G'day guys

I have several visualisations in a complex dashboard built with the Reporting tool.
The visualisations are being tweaked based on user feedback.  But once I reimport the changes visualisation in to CA11.0.4 I don't see the new version.
How, other than deleting and re-adding the viz to the report, do I refresh the viz so I can see the changes?

Cheers,

Blue

Hi Blue,

Select the visualization on your page. From the interactive toolbar, click on the ellipsis (three dots) and use the "Convert Visualization" option.

Cheers!

MF.
Meep!

Blue

Thanks for the reply.

Didn't work.  Only renamed the Data Container but the viz stays the same.  :(
Funny thing is that other vizes did update without me having to do anything at all.
I'll try re-imported the new viz individually with overwrite set to see if that does the trick.
Robert Edis
Principal
Robert Edis Consulting
Rotorua, New Zealand

Blue

OK, I'm a dufus.

I had four visualisations, each almost the same and based on a gauge.  The first was gaugered to be used when a value is below a certain threshold.  This was refined with the ring size, colour sequence (palette order), font, etc and saved as as gaugered.zip.  The name in the spec was gauge.red and this is documented in the code.  All good.
I then modified as appropriate and save the viz as gaugeamber, gaugegreen, and gaugegrey.  Each of these was imported into the dashboard report.  All renaming was done correctly.
I then had to make a major change so I modified the the gaugered and then saved it with JSON mods as ..amber, ..green, and ..grey.

What I forgot to do was CHANGE THE NAME in the actual code!!!  When I did the import the system simply saw four copies of gauge.red (irrespective of the zip file name) and just update that one viz.
Now I corrected the names as appropriate all works fine.  ;D

Cheers

Blue
Robert Edis
Principal
Robert Edis Consulting
Rotorua, New Zealand

MFGF

Quote from: Blue on 02 Nov 2016 04:55:43 PM
OK, I'm a dufus.

I had four visualisations, each almost the same and based on a gauge.  The first was gaugered to be used when a value is below a certain threshold.  This was refined with the ring size, colour sequence (palette order), font, etc and saved as as gaugered.zip.  The name in the spec was gauge.red and this is documented in the code.  All good.
I then modified as appropriate and save the viz as gaugeamber, gaugegreen, and gaugegrey.  Each of these was imported into the dashboard report.  All renaming was done correctly.
I then had to make a major change so I modified the the gaugered and then saved it with JSON mods as ..amber, ..green, and ..grey.

What I forgot to do was CHANGE THE NAME in the actual code!!!  When I did the import the system simply saw four copies of gauge.red (irrespective of the zip file name) and just update that one viz.
Now I corrected the names as appropriate all works fine.  ;D

Cheers

Blue

That's the sort of thing I'm prone to do! Thanks for the update Bob! :)

Cheers!

MF.
Meep!