I cannot modify Dimensions properly. Why?

I cannot modify Dimensions properly. Why?

This problem can occur if 'Orderbydes' column and 'Level' column are defined in different DB columns. For any Dimension defined in the data model, both the 'Orderbydes' column and the 'Level' Column should be defined with the same DB column. We cannot provide a different column name in 'Orderbydes' because it will not support multi parse queries and expression measures (if any). This is an advanced configuration, please consult Support team before making changes.

    • Related Articles

    • Manage module doesnot work properly

      If there is no KPI in the newly created module, the module doesn't reflect in the Analyst. Therefore, add at least one KPI (assigned to a KPI Group) for the module to appear in Analyst.

    • Why is the newly added Module not working properly?

      If there is no KPI in the newly created module, the module does not reflect in the Analyst.

    • Why can't I rename Dimensions and Hierarchies?

      You cannot rename Dimensions and Hierarchies, as they will be used in more than one KPIs. Renaming may disturb the functioning of some of the KPIs. But you can try the following instead: 1. Create a new dimension and hierarchy. 2. Link all the KPIs ...

    • Drilled down data sorting does not work properly. Why?

      Try the following steps: 1) For child level drill down, remove the 'Order by condition for the measure 2) To get the first column sorted in ascending order, Set the 'order by condition' as 'ascending' for department_code level in the datamodel.

    • Why is Weekday analysis by branch KPI not working properly?

      For the Measure C170 the DB_COLUMN_NAME (date_key) was mentioned in lower case. whereas in DB the column name (DATE_KEY) is upper case. Change the Measure "C170" DB_COLUMN_NAME to upper case, the KPI should work fine.