No read access to element, cannot view

[miker100]

Hi All,

A bit of a newbie to TM1 and having played around with a dimension I get the above error message. Any clues?

Thanks

Mike

[ajain86]

Mike,

Can you please explain what you are trying to do and when exactly you see an error?

thanks,

Ankur

[Alan Kirk]

A bit of a newbie to TM1 and having played around with a dimension I get the above error message. Any clues?

Take a look at the TM1 Developer's Guide .pdf document for version 9.1, specifically chapter 6, "Controlling Access to TM1 Objects".

In short:
- You've applied element level security to the dimension. Most likely at some point you were using an Admin login, right clicked on the dimension, selected "Security" -> "Elements Security Assignments...", made some changes and exited the dialog, thus imposing element security on the dimension;
- You're attempting to open the dimension or a cube using the dimension using a non-Admin login; a login which has not been put into a security group which has at least read access to the dimension elements.

[miker100]

Hi,

Thanks for the response. I am an admin user and all group have at least write permission in the dimension. What I did to cause this was write a process to load an alternative consolidation on this dimension. When I ran the process it deleted the existing consolidation level and added the new one. This was strange in itself. Since then despite recreating the original consolidation I get that error message. Most strange

Thanks

Mike

[Steve Rowe]

Hi,
It's most likely a problem with the view you are trying to open. When the view was saved, it was referencing a particular set of elements.
On one of the dimensions you deleted all the elements and added some new ones.
You tired to open the view and in one dimension all the elements that were in the view definition had been deleted. This was reported to you as a security issue.
Once the view was broken, reinstating the elements won't help, broke is broke.

Solution : Delete the (probably default) view of the cube concerned.
HTH
Steve

[miker100]

Hi Steve,

Yep broke is broke. I deleted the view as you suggested and hey presto its back in business.

Thanks a lot.

Mike

[paulsimon]

Mike

This only happens when the missing element is in the Title area of the view. It is not a problem if it is in the row or column area. The view will still open but you won't see data.

If your View uses an unnamed subset in the title area, then as per the previous post there is nothing that you can do but delete the View and re-create it.

However, if the View used a named subset on the dimension that has the problem, then just by re-creating the element and putting it in to that subset, you can then use the View again.

Regards


Paul Simon

[rkaif]

I got the same error once and I deleted the following to get it working:

CubeName.Default.blb
CubeName}vues (folder)

then I restarted the TM1 Server/Windows Service

[lotsaram]

I got the same error once and I deleted the following to get it working:

CubeName.Default.blb
CubeName}vues (folder)

That sounds a bit drastic as deleting the }Vues folder for the cube will blow away all views for the cube!

As per Paul's post this error message only apples when a title dimension (context filter for our newer Cognos colleagues) has no element assigned. You only need to delete the view if the title dimension causing the error uses an unregistered subset. A good reason IMO to ensure that all public views must use public subsets for all dimensions. Don't forget that title elements are assigned by index and not by name. The cause of this error could be an empty subset assigned to a title dimension but could just as well be due to a dimension having a title index of 10 assigned and then the subset is edited to have only 9 elements. Resave the subset in question with sufficient elements and the view will be fixed.

[asutcliffe]

.... Don't forget that title elements are assigned by index and not by name. The cause of this error could be an empty subset assigned to a title dimension but could just as well be due to a dimension having a title index of 10 assigned and then the subset is edited to have only 9 elements. Resave the subset in question with sufficient elements and the view will be fixed.

I've got the same problem. I what's happened is the element has been deleted and then an element with the same name added again. It now has an index of 3 when previously I presume it had an index of 1. I have a number of views that I'd rather not re-create from scratch. I am hoping I can simply edit the vue file directly. Has anyone tried this?

Cheers,
Alex

[lotsaram]

If you have enough views to make it worthwhile you could reassign subsets and elements via code in TI or with API code.

If you are talking about manually editing the .vue files I don't see how this is any easier than manually recreating views. If you do want to do this then yes it should be possible but I would only do this when the server is down as editing .sub and .vue files directly while the server is in session can cause issues, even server crashes in some versions.

[kpk]

As far as I remember you can change the elements in the corrupt view from the "Export as ASCII data" window if you do not want to delete and recreate it.

[lotsaram]

True.

Why did no one else think of that? Nice tip Peter

[asutcliffe]

Thanks Peter, I'd managed to work around it already but this should be easier next time.

Alex