TM1 Web-Hide selected Cubes or Automatically publish reports

[Daniela]

Dear TM1 Community,

the navigation pane of our TM1 Web application looks like this:
--> Applications
App1
App2
App3

--> Views
ReportingCube1
TechnicalCube1
ReportingCube2
TechnicalCube2

The users have access to the applications and can edit and save the reports under applications with a new name.
The saved new report is then located in the navigations pane under views. Therefore the users have to switch to views to see their new applied report.
The users can now see under views the technical and reporting cubes of our application, but this is unwanted. The user is only allowed to see the reporting cubes.

There are two possible solutions for this issue. But I couldn't figure out how to implement this solutions. Maybe some of you could help!

1.) Is it possible to hide some selected cubes in the views? (hide the technical cubes)
There is already one topic concerning this, but the use of security is not the appropriate approach.
http://www.tm1forum.com/viewtopic.php?f=3&t=4654

2.) Is it possible to automatically publish reports from views to applications?
If the reports are automatically published from views to application, we could hide the hole view node.

I hope I have explained our problem in an understandable way

Thank you very much for your help!

Kind regars,

Daniela

[tomok]

The users have access to the applications and can edit and save the reports under applications with a new name.
The saved new report is then located in the navigations pane under views. Therefore the users have to switch to views to see their new applied report.

Why do you think users have to switch to the Views folder to see an application they just published? The whole purpose of the Applications folder is to give you a spot to store web sheets, views and TI processes all in one spot to make it easier for users. Why would you publish a new view in the Applications folder and then go somewhere else to view it?????

Is it possible to hide some selected cubes in the views? (hide the technical cubes) There is already one topic concerning this, but the use of security is not the appropriate approach.

Why is security not the appropriate approach? It is, in fact, the only way you can selectively hide views from inside the Views folder.

[Daniela]

Why do you think users have to switch to the Views folder to see an application they just published? The whole purpose of the Applications folder is to give you a spot to store web sheets, views and TI processes all in one spot to make it easier for users. Why would you publish a new view in the Applications folder and then go somewhere else to view it?????

I know what's the purpose of an application is, but if a user opens a report stored under applications, edit and saves this report, the new report now appears under views folder. Now someone has to publish this report. This was exacly my question: It is possible to automate the publish process.


We have now a completly different solution. For everyone who has the same problem: we decided to create a new instance of our data model.
The required cubes are replicated in this instance and by a chore the cubes were synchronized automatically.
The user sees only the reporting cubes. That's it

[tomok]

I know what's the purpose of an application is, but if a user opens a report stored under applications, edit and saves this report, the new report now appears under views folder. Now someone has to publish this report. This was exacly my question: It is possible to automate the publish process.

First of all, the users are not actually editing and saving a report, they are actually editing and saving a cube view, which is why it is showing up in the Views folder. If you are giving them the security to do this why not just allow them to publish the view to the Applications folder as well? It should be possible to write a TI process that would publish all views as an Applications but you would need to have complete knowledge of the structure of the Applications object in TM1 and would not be something I would recommend for the inexperienced developer. I have never seen an example of such on this site but it might be here. You can do a search for it to see if there are any examples.

We have now a completly different solution. For everyone who has the same problem: we decided to create a new instance of our data model.
The required cubes are replicated in this instance and by a chore the cubes were synchronized automatically.
The user sees only the reporting cubes. That's it

This will certainly work but I don't know why you would go to this kind of trouble when applying security to accomplish the goal would be much simpler and not be a waste of TM1 resources.