Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

Historic Data by Week Number, Creating a Current Week X-Axis

I'm struggling to get data to show correctly in any chart visual yet the data shows fine in a table format. Most likely because they are 2 seperate tables. Below is the chart as it previously existed in Excel (This was done using static calculations in another Excel sheet and take time every week) Hence moving over to Power BI which would do it automatically. 

 

Incident Chart in Excel

Note the black circled x-axis is the week number of the year (of 2018). Now below is the data now in Power BI into a Table Visual. See that the Count figures (taking Week 24 as a example) is the same as the Excel chart, showing to me at least that the data can be matched and verified between Power BI and the Excel Chart (Week 24 for Example show 662 Resolved and 684 Arrived).

 

Incident data in Table Visual

Brilliant, but unfortunately when trying to stick this into a Chart Visual, the numbers dont match all because i can only use the Arrival Week Number OR Closed Week Number in the X-Axis thus only one set of values is correct. In the below case it will be the bar in Red (Arrivals) because the X-Axis is Arrival Week Number. 

 

Incident Chart in Power BI 

So how do i get Current Week into the X-Axis ???

  • Hi Anonymous,

     

    Yes, I can.

    Usually, only one date table is needed. Please refer to the snapshot below. There are two relationships while one is inactive.

    // We don't need to use userealtionship() for the active relationship.
    
    _Incidents_Resolved = COUNTROWS(Incidents)
    _Incident_Arrivals =
    CALCULATE (
        COUNTROWS ( Incidents ),
        USERELATIONSHIP ( Added_Date[DATEKEY], Incidents[Added_Date_Key] )
    )
    

    Historic-Data-by-Week-Number-Creating-a-Current-Week-X-Axis

     

     

    Best Regards,

8 Replies

  • v-jiascu-msft's avatar
    v-jiascu-msft
    Microsoft Employee

    Hi Anonymous,

     

    You need a date table in your scenario. And then create two relationships but only one is active. Finally you can calculate one value using a measure with userelationship-function-dax. It could be like below.

     

    Measure =
    CALCULATE (
        COUNTROWS ( 'table' ),
        USERELATIONSHIP ( 'calendar'[date], 'table'[Closed Week Number] )
    )
    

     

     

    Best Regards,

    • Anonymous's avatar
      Anonymous
      Not applicable

      v-jiascu-msft Many Thanks for this. So here is my DAX

       

      _Incident_Arrivals = CALCULATE(COUNTROWS(Incidents),USERELATIONSHIP(Added_Date[DATEKEY],Incidents[Added_Date_Key]))
       
      and the same again for Incidents Resolved
       
      _Incident_Resolved = CALCULATE(COUNTROWS(Incidents),USERELATIONSHIP(Closed_DateDATEKEY],Incidents[Closed_Date_Key]))
       
      Sticking that in the Values and the WeekNum from my Calendar into the Axis gets me the chart below. Somthings not right as you can tell. Both Values are the same
       
      Chart after UseRelationship DAX
      • v-jiascu-msft's avatar
        v-jiascu-msft
        Microsoft Employee

        Hi Anonymous,

         

        Can you share your file? Please mask the sensitive parts first.

        Why are there so many date tables like Added_Date, Colsed_Date? Only one date table is needed.

         

         

        Best Regards,