<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Generateseries: unexpected behaviour in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1196034#M19027</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="178805" data-lia-user-login="ivostammis" class="lia-mention lia-mention-user"&gt;ivostammis&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I tried different variations of your table, and I experience the same issue as you. And I can't get it to work properly. Funny thing is that when I create new calculated column like this:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;Date time column = DATEVALUE([Value])+TIMEVALUE([Value])&lt;/LI-CODE&gt;
&lt;P&gt;it returns the correct values. So that is one possible workaround. Another workaround would be to create the datetime-list with Power Query. Using Power Query is usually beneficial for how Power BI treats your table. Here is a recipe for how to create the table in power query:&lt;BR /&gt;&lt;A href="http://datacornering.com/how-to-generate-date-and-time-interval-list-using-power-query/" target="_blank"&gt;http://datacornering.com/how-to-generate-date-and-time-interval-list-using-power-query/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Sturla&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2020 20:39:13 GMT</pubDate>
    <dc:creator>sturlaws</dc:creator>
    <dc:date>2020-07-01T20:39:13Z</dc:date>
    <item>
      <title>Generateseries: unexpected behaviour</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1195448#M19001</link>
      <description>&lt;P&gt;I am building a maintable containing a long series of points in time. This maintable looks up / checks values from other tables which are not continuous (so containing gaps in time). To populate this table I use this query:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Maintable = GENERATE(SELECTCOLUMNS(Tagnames, "Colonne", Tagnames[Colonne], "Machine", Tagnames[Machine]), &lt;EM&gt;GENERATESERIES(DATEVALUE("15-06-2020 06:00:00"),DATEVALUE("22-06-2020 06:00:00"),TIME(0,0,10))&lt;/EM&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now the &lt;STRONG&gt;GENERATESERIES&lt;/STRONG&gt; is throwing a weird result: I add 10 seconds to the next step by TIME(0,0,10) (so expect to see only times ending on :00, :10, :20 etc). However after a while the time ends on :09, :19 et! This makes my whole model not working anymore, as I also have data in the other tables on the every-10 seconds schedule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After 9420 rows this event occurs for one machine, for the other machine after 5418 rows&amp;nbsp; (see the picture below).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone an idea why this happens? At first I had &lt;SPAN&gt;1/24/360&lt;/SPAN&gt; as timestep in GENERATESERIES , so I thought it had to do with floating point values, but now I am using TIME(0,0,10) and the issue is still here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;&lt;img /&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 01 Jul 2020 15:08:45 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1195448#M19001</guid>
      <dc:creator>ivostammis</dc:creator>
      <dc:date>2020-07-01T15:08:45Z</dc:date>
    </item>
    <item>
      <title>Re: Generateseries: unexpected behaviour</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1195996#M19026</link>
      <description>&lt;P&gt;i think your floating point hunch is still correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of cumulatively adding ten seconds, I would use a fixed datetime starting point and calculate the offsets from there. That way you can avoid the drift.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 20:13:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1195996#M19026</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2020-07-01T20:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Generateseries: unexpected behaviour</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1196034#M19027</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="178805" data-lia-user-login="ivostammis" class="lia-mention lia-mention-user"&gt;ivostammis&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I tried different variations of your table, and I experience the same issue as you. And I can't get it to work properly. Funny thing is that when I create new calculated column like this:&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;Date time column = DATEVALUE([Value])+TIMEVALUE([Value])&lt;/LI-CODE&gt;
&lt;P&gt;it returns the correct values. So that is one possible workaround. Another workaround would be to create the datetime-list with Power Query. Using Power Query is usually beneficial for how Power BI treats your table. Here is a recipe for how to create the table in power query:&lt;BR /&gt;&lt;A href="http://datacornering.com/how-to-generate-date-and-time-interval-list-using-power-query/" target="_blank"&gt;http://datacornering.com/how-to-generate-date-and-time-interval-list-using-power-query/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Sturla&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 20:39:13 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1196034#M19027</guid>
      <dc:creator>sturlaws</dc:creator>
      <dc:date>2020-07-01T20:39:13Z</dc:date>
    </item>
    <item>
      <title>Re: Generateseries: unexpected behaviour</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1198101#M19077</link>
      <description>&lt;P&gt;Thanks! I ended up generating the table in powerquery, as DAX was already slowing my model down a lot I hope this also contributes to refresh speed &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2020 13:36:12 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Generateseries-unexpected-behaviour/m-p/1198101#M19077</guid>
      <dc:creator>ivostammis</dc:creator>
      <dc:date>2020-07-02T13:36:12Z</dc:date>
    </item>
  </channel>
</rss>

