Forum Discussion

NickF's avatar
NickF
Frequent Visitor
10 years ago
Solved

Timeline Issue

Hey everyone,   I'm not sure if this has been discussed yet or not, but it's something I've run into over the last couple days. I'm using the Timeline slicer to view a set of data for a single mont...
Need Help
  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    10 years ago

    Hi NickF,

     

    Based on my test in Power BI Desktop version 2.37.4464.461 and TimeLine version 1.3.5, whatever the date stored in SQL Server database is datetime or date data type, when we check date range as July 1st to 31th, it will also display the data in August 1st.

     

     

     

     

    For this issue, I would suggest you send a feedback to Power BI Custom Visuals Support alias: [email protected].

     

    If you have any question, please feel free to ask.

     

    Best Regards,
    Qiuyun Yu

KGrice's avatar
KGrice
Icon for Memorable Member rankMemorable Member
10 years ago

I tried recreating the issue with no luck. Try seeing what happens if you do the same.

 

I made a table in Excel with a Date column, values from 6/30/2016 - 8/1/2016, and a Value column, with any random values you want in there. Import into Power BI and make a line chart where each date would show with its corresponding value on the chart. I downloaded the most recent version of the Timeline visual and set the Days to 7/1/2016 - 7/31/2016. The values for 6/30 and 8/1 do not show on the chart, unless I modify the selection on the timeline slicer to include them.

 

Whatever measure you're using doesn't override any of the filter context provided by the slicer, does it?

NickF's avatar
NickF
Frequent Visitor
10 years ago

I too was unable to recreate the issue using an Excel import. The problem, however, is that I use Direct Query, as this report is frequently viewed and requires fresh data (which would mean constantly updating the spreadsheet). What I've found is that Power BI appends a time to the date field when using Direct Query, and does not do so when using an Excel import.

 

Direct Query:

 

 

Excel:

 

 

Is it possible that the time is throwing off Timeline, so that it reads a date such as 8/1/2016 12:00:00 as 7/31/16 instead? The queries are identical, and so is the data they pull, so I'm not sure what else it could be. Unfortunately, since Direct Query is being used, I am also unable to use 'CAST' or 'CONVERT' to re-format the date field. Any suggestions?

  • v-qiuyu-msft's avatar
    v-qiuyu-msft
    Icon for Community Support rankCommunity Support
    10 years ago

    Hi NickF,

     

    Based on my test in Power BI Desktop version 2.37.4464.461 and TimeLine version 1.3.5, whatever the date stored in SQL Server database is datetime or date data type, when we check date range as July 1st to 31th, it will also display the data in August 1st.

     

     

     

     

    For this issue, I would suggest you send a feedback to Power BI Custom Visuals Support alias: [email protected].

     

    If you have any question, please feel free to ask.

     

    Best Regards,
    Qiuyun Yu

    • NickF's avatar
      NickF
      Frequent Visitor
      10 years ago

      Qiuyun,

       

      Thank you for the reply, I will send the Support group an email this morning. I have found that this only affects Direct Query, so as long as I use the Import option when working with SQL instead, it isn't an issue.

      • cneumann's avatar
        cneumann
        Frequent Visitor
        10 years ago

        Hi Nick,

         

        I am getting this error even when using "Import" option with SQL Server. 

         

        The behaviour I am facing is that, when I select 1 month (Jan 2016 - Jan 2016), it gives me the dates from January 2nd to Februay 1st.

         

        I am using Import option with SQL Server, PowerBI Desktop August 2016 Update, Timeline Slicer v 1.3.14.

         

        Please see the screenshot below.

         

        Thanks,

        Cristhian.