New Cube Different Internal IDs?

[Francis aka khayman]

We currently have a Cube (lets call it CubeA) and reports using this cube in production. I made minor and temporary changes to CubeA, build the cube, created another package in our Production environment, say Cube B (i know, i know, not the best of practices). 

I tried to point the existing reports to Cube B. I got errors. It seems like the existing members in the are not found in Cube B. Most probably the internal ID or MUN changed.

Is this an accurate assesment?

[Francis aka khayman]

I am relatively new to cubes. So I am approaching this like what I would do using FM packages. If I want to test some changes I made to my FM and make sure that the reports in production would work with the new FM as well as the changes works properly, I would publish my changes in another package, create another copy of a production report and point it to the new package and check.

Sometimes this kind of dev work needs to be done in Production because our Development database is not synched to production (DBAs tsk tsk tsk)

[bdbits]

Yes, probably different MUNs. You can verify this by getting properties on the members in the package tree within Report Studio. You are probably getting different ids at the lowest level of the MUN (the part at the end).

[MFGF]

I strongly suspect the package name forms the first part of each MUN, so having a package with a different name will mean every single MUN is different.

As Bob says, expand your package tree within each package in Report Studio and right-click on a member and choose Properties - this will give you the MUN of the member. You can compare both and see what the differences are...

MF.

[Francis aka khayman]

Just tested... you are right... but... Cognos gets weird again.

Package name is part of MUN, true, but it is not derived from package name but from datasource.

Using the same datasource, you can create different package names and report from one package will work with the other package -- as long as the packages came from the same datasource.

If you have different datasources, no matter how the same the contents are (dimensions and measures) and no matter if they come from the same cube, and it will not matter if you create the same package names, report will not work on another package with the same name if the datasource is different.

[Francis aka khayman]

Or the first part of MUN is Datasource name? Its just we usually use package name = datasource name so we think its package name.