Access Tables in 8.4

[Milt]

Hi,

First time post !

We recently upgraded from 8.1 to 8.4 (fix pack 1) and all went well, apart from an issue we discovered in the way access tables are handled in 8.4

So, we have a cube which has a dlist used as a context - the access table has NODATA entries agains the dlist.

However, when the cube is opened in the rich client you can see all entries in the dlist ! This is a bit of a disaster as some of the information is confidential !

The only solution to the problem was to set the access to HIDDEN.

I assume though that this means the cube isn't cut down when GTP'd which means the whole data model is loaded into the web client ?

Anybody else come accross this issue?

Cheers, Milt

[JaromirSeps]

Hello,

yep, we came across this issue as well.

We got it logged on IBM support (no. 00430 SGC 668 ). The final response was, that if it is business critical, they will include it in some future fix pack.

Please log it to support as well, so they will finally understand this is important.

Jaromir

[rbuhrt]

Hi,

First time post !

We recently upgraded from 8.1 to 8.4 (fix pack 1) and all went well, apart from an issue we discovered in the way access tables are handled in 8.4

So, we have a cube which has a dlist used as a context - the access table has NODATA entries agains the dlist.

However, when the cube is opened in the rich client you can see all entries in the dlist ! This is a bit of a disaster as some of the information is confidential !

The only solution to the problem was to set the access to HIDDEN.

I assume though that this means the cube isn't cut down when GTP'd which means the whole data model is loaded into the web client ?

Anybody else come accross this issue?

Cheers, Milt

Yes, this is an open issue in the Rich Client software, it is actually only a visual defect with the No Data option showing the dlist item(s) visible in the dropdown. If you open the application in the classic client, you will not see the same effect. The model will be infact cutdown correctly by using this type of access table, however your users will see the items visible but would be unable to see any data for the item.

[Milt]

Thx for your replies.

The issue only seems to arise if the dlist is targeted by more than 1 cube. So, the solution is to create a copy of the dlist for each cube (then you can use the NODATA option)

I assume Cognos will fix this issue in the future.

>Milt

[RickC]

Does it work if you make it both "No Data" and "Hidden"?  That is, would that solve the issue of the GTP taking longer?

[Milt]

I think this is fixed in FP2 although I've not tested it yet.

[lav4you]

IBM has released service Cognos Planning 8.2 fix pack 2 which has addressed this problem..
download and release notes are available here
http://www-01.ibm.com/support/docview.wss?rs=3449&uid=swg24024831

[B. Connell]

In addition to the NO DATA concer, for cells which I have marked HIDDEN, I am getting zeroes instead.
I don't see this fix on the FP2 listing - have other people encountered this as well?

Thanks,
Briana