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

 

Click on a package folder to open the default analysis in AS - Possible?

Started by JGirl, 17 Mar 2011 10:54:07 PM

Previous topic - Next topic

JGirl

Is it possible?

Our business users are sure that they used to be able to click the package and the default analysis opened in Analysis Studio.

I think they are confusing it with PowerPlay cubes.

Ideas anyone?

PRIT AMRIT

QuoteOur business users are sure that they used to be able to click the package and the default analysis opened in Analysis Studio.

There is no such functionality I believe. As you said they are confusing with PowerPlay Cube files saved inside the package.

MFGF

You can define a default analysis for a package, which will open up when a user launches Analysis Studio against the package. Is this what you mean?

MF.


Snet form my fumblefingers
iPhon 5 usig Tapatalk
Meep!

AussiePete2011

Hi there

Is this what you are referring to
Steps from IBM Cognos Connection

    In IBM Cognos Connection, click the More option for a PowerPlay report.

    Choose the target studio to use for the migration:

        To migrate the report to Analysis Studio, click Open with Analysis Studio.

        To migrate the report to Report Studio, click Open with Report Studio.

    A dialog box appears warning you that there might be differences between the source report and the migrated report.

    If you want to see a list of what will be different in the migrated report, click Details.

    Tip: If you clear the Show this dialog in the future check box and later on you want to see this dialog again, you must delete your browser cookies.

    Click OK to continue with the migration process.

The bit that is important is the Tip

Cheers
Peter B

JGirl

Quote from: MFGF on 20 Mar 2011 02:11:57 PM
You can define a default analysis for a package.....Is this what you mean?

Nope, not what I mean.  I've already a default analysis attached to each package, but our users are adamant that they used to be able to click once on the blue package folder in Cognos Connection and the cube would magically open in Analysis Studio. 

I was 99% sure this functionality didnt exist, and that they were confusing it with a PowerPlay cube but just thought I'd post it here in case it is something that has changed in more recent versions of Cognos.

Thanks all for your feedback.
J

AussiePete2011


twlarsen

How about hiding the package folder so they can't see it?  Then only allow them to view and use cube views that you've created.  Do they need to see the actual package for a particular reason?

MFGF

Quote from: JGirl on 20 Mar 2011 06:29:51 PM
Nope, not what I mean.  I've already a default analysis attached to each package, but our users are adamant that they used to be able to click once on the blue package folder in Cognos Connection and the cube would magically open in Analysis Studio. 

I was 99% sure this functionality didnt exist, and that they were confusing it with a PowerPlay cube but just thought I'd post it here in case it is something that has changed in more recent versions of Cognos.

Thanks all for your feedback.
J

I'd tend to agree with your thoughts about then getting confused with PowerPlay -- clicking on the cube link would open the cube in PP, and I'd be willing to bet this is what they are thinking of.

Regards,

MF.
Meep!

cognostechie

This is the same scenario that one of my clients had. Specially, because the Cube Package and Framework Package both look blue.

What I did was to hide all the packages from the users so they don't see it. Create appropriate folder structures and create a default analysis from the cube package. Save it so it gets saved as a cube report but the icon looks like a Cube. Copt that to the folders accessible by the users. When they click on it, it opens up as was saved (with default analysis).

Actually, it doesn't make sense to show packages to the users.

JGirl

Quote from: cognostechie on 24 Mar 2011 12:22:40 AM
...create a default analysis from the cube package....Actually, it doesn't make sense to show packages to the users.

This is how I was planning to get around it.  Thanks again to everyone for the input.