Merging Dimensions in Web Intelligence
Submitted by Ian Pendlebury on Wed, 2008-02-27 13:18.
I have created two queries in Web Intelligence and run them both simultaneously to create one report as demonstated in Kevin O'Shea's webinar. I now want to merge dimensions but unlike in the webinar the relevent button is greyed out. Do you know why this is? Thanks.
Synching queries
There is an article on the TDN about synching queries. It has been updated for the new functionality in Web Intelligence
Synchronising Queries in Talis Decisions
The icon may be greyed out if there is only one query (which isn't the situation here) but access can be prevented within the rights setup in the CMC.
Under Home > BusinessObjects Enterprise Applications > Web Intelligence it is possible to set the Merge dimensions for synchronization right for groups and users.
I would suggest checking if the user has this right granted either specifically or via inheritance. This is usually allowed to the administrator user by default but it may have been changed since installation or if a different user the migration or creation process might mean this right hasn't been granted.
In terms of rights you always have to check because users may pick up rights from different groups and if a right is not clearly granted the system will default to denying the right. remember you may have to logout and back into InfoView/Web Intelligence to pick up changes.
If the rights are OK then more information about the objects used in the queries will be required.
Thanks
Brian Crampton
Developer, Talis
Merging Dimensions
You're right Brian, I don't have the neccessary rights but I can't work out how to change that.
changing rights
I can only give a general pointer as I don't know exactly what groups and users you have setup. You may want to raise a call with Support to go through the details.
If you go through the links in the CMC to the Web Intelligence area Home > BusinessObjects Enterprise Applications > Web Intelligence as the administrator user you will be in the rights area for the application.
What you will see is a list which will include the Administrators and Everyone groups. You may also have other groups and users that have been created or migrated.
For each row in the list there is a link called Advanced.
For the Administrators group click on this link and set the Merge dimensions for synchronization to Explicitly Granted and click OK. (you may want to do the same for all the rights in the list)
For the Everyone group click on the link but this time set the right to Not specified and click OK. You may have to uncheck the option to inherit at the top of the page and click apply first to do this. (again it is worth doing this for all the rights for the everyone group).
Every user is automatically in the everyone group and can't be removed. What I usually advise is to set all rights for the everyone group to not specified so they don't conflict with rights inherited from other groups e.g. if you explicitly deny a right for the everyone group then a user will not be able to do something even if the right is explicitly granted elsewhere.
At this point it gets more complicated since I don't know exactly what groups and users may also be displayed and what level of control you require. As a general rule I would remove any individual users from the list and then change the rights for the other groups listed to the same values as was done with the administrator group.
If the user is in a group not in the list then add the group to the list and set the rights. Please ensure that the user is in a group other than everyone.
The Add/Remove button allows you to modify the list.
As I said this is a general approach which may not suit you specifically and you may need to speak to Support.
The configuration of rights is covered in the System admin training course. Details can be seen in the Talis Education section of the web site.
Thanks
Brian Crampton
Developer, Talis
Merging Dimensions
Thanks Brian, I'd finally managed to work it out. My colleague Chris Hill was saying to me earlier on that on editing a query and then running it, the resulting report did not reflect the changes. I suspect this may have something to do with user rights as well.