This problem can occur if the new module created does not contain any KPIs. Please create at least one KPI for the newly created module. Additionally, there is no need to assign this to Super users. By default, security does not apply to Super users. ...
This issue generally happens when we have the WH DB related jars file incompatible. To resolve this we need to have correct db version specific jar say in specific case of SQLSERVER2008N as WH DB. sqljdbc.jar and sqljdbc4.jar need to update to tomcat ...
Data security can be assigned at the Role level as well as the User level. Privileges can be set for individual Roles/Users. If there are any discrepancies with the security, re-assign the privileges for the problematic users.
When checked in the oracle_dbmodel.xml for the Department hierarchy the foreign key Department_Code has to be equivalent (match) with one of the level column name . Ensure that the foreign key of the problematic hierarchy in the 'dbmodel.xml file' ...