I'm a newbie to Cognos (though well versed in compute generally) but I'm stumped by what I think should be a simple task ... the renaming of a View within the GL Cube in our Cognos Express 10.1 instance sitting on a Win2008 domain sever.
Our user wants to update a particular item within one of their GL Cube views but keep a copy of the original view as a rename (for rollback and reference).
Is there no simple way top rename a View ? ... or am I missing something glaringly obvious?
I've Googled and read and searched forums (like this one) and even tried renaming the .vue files (via the filesystem) in the user's private GL}vues directory but that doesn't seem to pull through to the "Server Explorer: IBM Cognos Express Architect" UI nor the "Xcelerator Client" UI (Spreadsheet browser version).
We tried Opening the original Public view and doing SaveAs to the "Private" view but then it will not let you have two views of the same name (one private one public) so the only way I can see to do this is ...
Open the Public view and SaveAs by a slightly different name
Delete the original public view
Open the renamed version, make the required updates and SaveAs back by the original name.
It's just 'messy' and feels risky making a renamed copy then deleting the original ....
Worse too is that for some reason the user cannot directly SaveAs a public view (even without the "Private" tick-box checked). They have to SaveAs "Private" then right-click and "Publish" the view .... I don't yet understand why as there are no error messages and they appear to have the same rights (within Cognos admin) as myself, yet I CAN SaveAs directly to a public view.
Any guidance or suggestions appreciated.
Renaming a View
-
- Posts: 5
- Joined: Tue Feb 04, 2014 2:55 am
- OLAP Product: Cognos Express
- Version: 10.1
- Excel Version: 2010
Re: Renaming a View
If the original cube view name was 'view1' > open 'view1' and save as 'copy of view1' > re-open 'view1' and make the changes, then save to overwrite.
I'm pretty sure only admin group has public view write access. Remaining groups have access to create and modify private views only.
I'm pretty sure only admin group has public view write access. Remaining groups have access to create and modify private views only.
Yeon
-
- MVP
- Posts: 3706
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Renaming a View
As in hit the F2 key and type something? Nope, that would be too easy. Just open the view ans Save As, followed by delete the original view if you need to. Not that hard a work-around.Is there no simple way to rename a View?
Wrong on this one. Unless you did something wrong (as in renamed the wrong file) it does indeed pull through and change the client settings. What is required that you might have missed though is a log out (if the user is currently logged in) and login. Remember TM1 is an in memory database and file system objects are only read initially and not continuously, for private objects these are read and registered when the user logs in.I've even tried renaming the .vue files (via the filesystem) in the user's private GL}vues directory but that doesn't seem to pull through to Server Explorer.
Are you positively 100% sure? Because what you state is incorrect. Private objects (views and subsets) can exist with the same name as public objects. But this comes at a price which is that the private objects will be used in preference to the public ones and which can result in 2 users seeing something different (for reasons other than security) when they *think* they are looking at the same object.We tried Opening the original Public view and doing SaveAs to the "Private" view but then it will not let you have two views of the same name (one private one public) ...
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Posts: 5
- Joined: Tue Feb 04, 2014 2:55 am
- OLAP Product: Cognos Express
- Version: 10.1
- Excel Version: 2010
Re: Renaming a View
Thanks to both contributors esp. to lotsaRAM - thanks for very helpful individual responses ... food for thought!
The saving-back issue has me puzzled because apart from me being a Local Admin at the system level at the Cognos server, our internal client and my own account appear to have identical rights looking at the Cognos security settings where we are both "Admin" for all the same objects ... I CAN save back to the Public view when I un-tick the "Private" box whereas the system seems to LET her do the save but then upon reload of the supposedly updated view, ... it has not retained what she added
The client and I both have has these security objects selected:
Administrative Group assignments:
Admin selected ... DataAdmin and SecurityAdmin NOT selected
User Group Assignment:
Cognos\Express Administrators, Cognos\Express Users and Cognos\All divisions selected ... all other User groups NOT selected
On renaming the view at the file-structure level, I had actually had both the user and I exit our clients and re-load/re-connect our sessions following the rename, yet the view name showing in the UI stubbornly remained unchanged upon re-connect. We even tried doing "refreshes" but again - no change. My experience suggested it should have changed but didn't and because I'm no COGNOS specialist, I decided to change it back and leave it alone in case I was inadvertently messing with some internal tables or indexes or something nasty.
As far as saving to the Private view with the same View name as in Public, all I know is that we loaded the Public view went to SaveAs with the Private box ticked and it wiped the name out of the SaveAs name field and sat challenging for a name so we re-selected the (public view) name and re-tried SaveAs (private) and the name vanished again!!! We Reselected the name a third time, added the user's initials and it saved as a private view for her, sweet-as.
I didn't test any further then, but in light of your comments I shall now re-visit that also.
Hmmm ... nice warning about the Private over-ruling the Public view of the same name! All the more reason to rename the original one and leave it in the Public space for everyone to access when(if) required.
If I discover something new, I'll post back
Thanks again for the quick responses folk.
Regards Col.Sanders
The saving-back issue has me puzzled because apart from me being a Local Admin at the system level at the Cognos server, our internal client and my own account appear to have identical rights looking at the Cognos security settings where we are both "Admin" for all the same objects ... I CAN save back to the Public view when I un-tick the "Private" box whereas the system seems to LET her do the save but then upon reload of the supposedly updated view, ... it has not retained what she added


The client and I both have has these security objects selected:
Administrative Group assignments:
Admin selected ... DataAdmin and SecurityAdmin NOT selected
User Group Assignment:
Cognos\Express Administrators, Cognos\Express Users and Cognos\All divisions selected ... all other User groups NOT selected
On renaming the view at the file-structure level, I had actually had both the user and I exit our clients and re-load/re-connect our sessions following the rename, yet the view name showing in the UI stubbornly remained unchanged upon re-connect. We even tried doing "refreshes" but again - no change. My experience suggested it should have changed but didn't and because I'm no COGNOS specialist, I decided to change it back and leave it alone in case I was inadvertently messing with some internal tables or indexes or something nasty.
As far as saving to the Private view with the same View name as in Public, all I know is that we loaded the Public view went to SaveAs with the Private box ticked and it wiped the name out of the SaveAs name field and sat challenging for a name so we re-selected the (public view) name and re-tried SaveAs (private) and the name vanished again!!! We Reselected the name a third time, added the user's initials and it saved as a private view for her, sweet-as.
I didn't test any further then, but in light of your comments I shall now re-visit that also.
Hmmm ... nice warning about the Private over-ruling the Public view of the same name! All the more reason to rename the original one and leave it in the Public space for everyone to access when(if) required.
If I discover something new, I'll post back
Thanks again for the quick responses folk.
Regards Col.Sanders