If the month range selected is in between Nov 2010 to Jan 2011 then Week1 that belongs to Jan 2011 appears first in the KPI. The order is improper. How can I correct the order?

• Related Articles

• If the month range selected is between Nov 2010 to Jan 2011 then Week1 that belongs to Jan 2011 appears first in the KPI. The order is improper

  Set the 'OrderBy' column in the cross-tab area of the KPI to 'DATE_KEY - Ascending' such that the Week1 that belongs to Jan 2011 appears at the end which is the correct way of looking at the data if the month range selected is between Nov 2010 to Jan ...

• Why is the order improper, while using the Month Range option? For example, I selected Nov 2010-Jan 2011. Week 1 of Jan 2011 got displayed first.

  Modify the 'OrderBy' column in the crosstab area of the KPI as 'DATE_KEY - Ascending' to get the month range in the ascending format. After doing the changes, if you select Nov 2010-Jan 2011, then the Week1 of Jan 2011 appears at the end.

• Crosstab is not sorting properly when week range is selected across multiple years. Why?

  This issue can occur if the column name for the week in 'TIME' dimension is mapped to 'WEEK_NUMBER_THIS_YEAR'. To solve the issue, change the column name of the week in 'TIME' dimension in the dbmodel to 'WEEK_NAME_THIS_YEAR'.

• Why is week range starting from week 35?

  This issue can occur if there is a problem in queries of admin_mssql_warehouse.xml. Check and modify the following queries in admin_mssql_warehouse.xml. Query ID's: 1. WEEKMINRANGE 2. FILTERDAO1 3. FILTERDAO7 Please note that only administrators can ...

• Week filters show 1 week ahead. How can I correct this?

  Refer and update 'MAINMENU4' and 'WWCAL16' queries in warehouse. xml file.