Pergunta Time Intelligence filter returns wrong week number!?

  • segunda-feira, 6 de agosto de 2012 13:53
     
     

    The Time Intelligence filter I created returns the wrong week number. The data source is SSAS cube with date dimension hierarchy of Year -> Week -> Date.

    In analysis service cube browser as well as with MDX queries the week number lines up with the years correctly. However the time intelligence filter returns week number 18 for Monday July 30, 2012?!

    The reference member is set to 1/1/1997 the first date in the dimension and the hierarchy level is set to day. Time Member Association is set to Year, Week and Day in the time tab in the data connection.

    The preview button under the time formula shows the correct year and day however the week is incorrect.

    If I set the reference member to 1/1/2012 the I get the correct week number for 2012 but it messes prior years’ week numbers?

    Any Idea?!?!

Todas as Respostas

  • segunda-feira, 6 de agosto de 2012 14:57
     
     

    Your week count is starting from 1st April?

    Sounds like something is setting the week count type to taxYear?

  • terça-feira, 7 de agosto de 2012 15:32
     
     

    I do not think that it is the case becuase if I set the member reference to 1/1/2012 I get the correct week number for todays' date. When I set it to 1/1/1997 I get month 1 and week 2 of 2010 which not even close to 2012.

    As of today here is what the Time Intelligence Filter Preview is returning

      Year [Report Dates].[Report Dates].[Report Year].&[2012]
      Month [Report Dates].[Report Dates].[Report Month].&[2012]&[8]
      Week [Report Dates].[Report Dates].[Report Month].&[2010]&[1].&[2010]&[2]
      Day [Report Dates].[Report Dates].[Report Month].&[2012]&[8].&[2012]&[32].&[20120807]

    you can see that it is getting the correct Year, Month, and Day. The day formula even point to the right Month -> Week -> Day. Which is week 32 for Augut 7, 2012. However the the week formula is way off target!

  • terça-feira, 19 de fevereiro de 2013 07:39
     
     

    I'm experiencing the exact same thing. Did you find any solution?

    Update:

    You could use [Week.Day.Parent] instead of just [Week].

    Worked for me :-)