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

Changing package in Report Studio

Started by kgcognos, 24 Sep 2015 12:57:52 PM

Previous topic - Next topic

kgcognos

We have existing standard reports that uses a Sales cube but we want other users to use a different cube. All definitions are the same except the name of the cube. We tried to change the Package from the properties.
But we get an error
QE-DEF-0030 Expression parsing error.
QE-DEF-0359 The query contains a reference to at least one object '[Sales Cube].[Time].[Time].[Month]' that does not exist.
The Sales cube is the name of the original cube.
I thought we can link a different package to a report as long as the fields are the same.
Is there a setup that we need to follow when creating reports or packages in order to allow us to easily change a package?


Thanks in advance.

cognostechie

Cognos works with MUN (Member Unique Names) which is the full qualifier to identify an item in the package. In order to change a package and still have the report work, the MUNs have to be the same.

kgcognos

The MUNs are different. It contains the name of the package.
Is it possible to make it the same?

bdbits

Nothing simple, due to MUNs. The easiest thing would probably be to export the report spec, do a search/replace, and import it back into Report Studio.

If the reports and packages are the same, why are you going through this? I suspect there is a deeper problem you are trying to solve with a jackhammer. Maybe you just need a screwdriver.

kgcognos

Yes, we are currently having performance issue using 1 cube containing all companies. We may need to split the cubes. But we have standard reports that we don't want to duplicate to point to the child cube.
Thanks for the reply.

bdbits

Here is what I would do, assuming your cube is based on a package and company is a dimension.

Create a new company dimension query subject(s) in the package that has a filter for company, taking care to keep all the same columns as the unfiltered query subject.
Publish the package.
Copy the cube model to a new file. You can do this within Transformer if you like with a File > Save As.
Open the copied cube model in transformer.
Modify the columns on the package query subject, remapping the columns to the new query that has the company filter.
Build and publish/deploy the new cube.
Open/copy one of the existing reports and change it to the new cube, see if it runs.

I believe if you use these steps you will preserve the MUNs and so it will work.