Why is week range starting from week 35?

• Related Articles

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

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

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

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

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

• Why is the application not working when we create the aggregate table starting with VW?

  This problem can occur if you have not selected 'Re-cache changes' after doing modifications in warehouse, admin databases and datamodel. So select ' Apply/ Re-cache changes' to solve the issue.