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

Error in BI report sorcing from TM1 Cube, works fine in Dev enviornment

Started by cognos4321, 13 Jun 2016 04:04:23 PM

Previous topic - Next topic

cognos4321

Hi experts,

I am running a report in report studio and it works absolutely fine in Development environment and shows the following error in Production

Identifier not found '[Planning].[Account].[Account].[L4]'.

We are using cognos 10.2 and the source for all reports is TM1 cube.
I guess there is some issue with alignment of cubes in Dev and prod since the report works fine in Dev.
I checked the }HierarchyProperties Cube and was able to see all the dimensions used . I clicked Show all---> OK in both the environments in }HierarchyProperties Cube but still the error remains the same. I don't know if I am following a correct approach.

Please suggest something to troubleshoot this issue

Thanks Always.

MFGF

Quote from: cognos4321 on 13 Jun 2016 04:04:23 PM
Hi experts,

I am running a report in report studio and it works absolutely fine in Development environment and shows the following error in Production

Identifier not found '[Planning].[Account].[Account].[L4]'.

We are using cognos 10.2 and the source for all reports is TM1 cube.
I guess there is some issue with alignment of cubes in Dev and prod since the report works fine in Dev.
I checked the }HierarchyProperties Cube and was able to see all the dimensions used . I clicked Show all---> OK in both the environments in }HierarchyProperties Cube but still the error remains the same. I don't know if I am following a correct approach.

Please suggest something to troubleshoot this issue

Thanks Always.

It sounds to me like the L4 member exists in your Dev cube but not in your Prod cube? If you're referring directly to this in your report, it makes sense that it will work in Dev but not in Prod...

MF.
Meep!

cognos4321

Thanks MF for the reply.
It's fixed now . I had to update hierarchies in the Hierarchy properties cube in prod.