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

• Related Articles

• 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.

• 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 ...

• 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.

• How to restrict the number of weeks displayed in the Week range filter?

  You can restrict the number of weeks to be shown in the Week Range filter by modifying the 'weekRange' property in arc.properties. After modifying, please remember to re-cache changes.

• Week' on Crosstab KPI does not sort on column correctly. Why?

  Perform the following steps to resolve: 1. Add a new column week_number_this_year-year in DIM_DATE. 2. Map the new column to date_fld level s description parameter, in the mssql_dbmodel.xml file. OR Change the Set Order By column to DATE_FLD.