<?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: Timestamp cuts of fractals after 3 digits in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1544052#M62777</link>
    <description>&lt;P&gt;any idea how to create a table with a complete day? 3 digits will be enough but I need a reference day from 00:00:00.000 to 23:59:59.999&lt;/P&gt;&lt;P&gt;Is there a possibility to create such a day?&lt;/P&gt;</description>
    <pubDate>Thu, 14 Feb 2019 06:48:50 GMT</pubDate>
    <dc:creator>krameralexander</dc:creator>
    <dc:date>2019-02-14T06:48:50Z</dc:date>
    <item>
      <title>Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543604#M62770</link>
      <description>&lt;P&gt;Hello community,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I desperatly try to create a timestamp Format with 9 fractals. I got core Data from a Database where the timestamp is very dimituive with 9 fractals after ss&lt;/P&gt;&lt;P&gt;So I changed the format to "SET TimestampFormat='hh:mm:ss.fffffffff';" and enterd also a "Timestamp(Timestamp#([Time], 'hh:mm:ss.fffffffff') ,'hh:mm:ss.fffffffff') AS [TS]" at my import script, but it always cuts of after 3 digits and enters 0 instead. Anyone who can help me? I really need to solve this (Oh ... the information of course is available within the data &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; )&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 06:36:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543604#M62770</guid>
      <dc:creator>krameralexander</dc:creator>
      <dc:date>2024-11-16T06:36:20Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543609#M62771</link>
      <description>&lt;P&gt;Sample values will be helpful to help&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 13:05:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543609#M62771</guid>
      <dc:creator>vvira1316</dc:creator>
      <dc:date>2019-02-13T13:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543614#M62772</link>
      <description>&lt;P&gt;QlikView is only able to bring upto 3 fff correctly and becomes weird when you have more than 3 fff... Just an idea: What if you convert it into number and try to bring in? It might still not be able to display correctly the f in the timestamp, but the calculation on them might work.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 13:09:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543614#M62772</guid>
      <dc:creator>sunny_talwar</dc:creator>
      <dc:date>2019-02-13T13:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543647#M62773</link>
      <description>&lt;P&gt;Contract,Date,Time,Depth Level,Bid Quantity,Bid Price,Ask Price,Ask Quantity&lt;/P&gt;&lt;P&gt;ABCD Jan 2019,18.07.2018,06:00:00.193684787,0,,,,&lt;/P&gt;&lt;P&gt;ABCD Jan 2019,18.07.2018,07:55:00.125039582,0,0,43,30,43,70,0&lt;/P&gt;&lt;P&gt;ABCD Jan 2019,18.07.2018,08:00:00.146053080,0,1,43,30,43,70,2&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 13:34:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543647#M62773</guid>
      <dc:creator>krameralexander</dc:creator>
      <dc:date>2019-02-13T13:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543648#M62774</link>
      <description>&lt;P&gt;Those are exmaple Data ... as you can see, the timestamp contains 9 fractal digits ... If I convert it into timestamp format as shown above it replaces all digits after the third into zeros&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 13:35:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543648#M62774</guid>
      <dc:creator>krameralexander</dc:creator>
      <dc:date>2019-02-13T13:35:48Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543699#M62775</link>
      <description>&lt;P&gt;I'm able to see it in table&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ts.PNG" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/5869iC2AD55C00CC92E38/image-size/large?v=v2&amp;amp;px=999" role="button" title="ts.PNG" alt="ts.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Table preview image&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ts.PNG" style="width: 774px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/5870i4D59C0DFA94856CE/image-size/large?v=v2&amp;amp;px=999" role="button" title="ts.PNG" alt="ts.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SET ThousandSep=',';&lt;BR /&gt;SET DecimalSep='.';&lt;BR /&gt;SET MoneyThousandSep=',';&lt;BR /&gt;SET MoneyDecimalSep='.';&lt;BR /&gt;SET MoneyFormat='$#,##0.00;($#,##0.00)';&lt;BR /&gt;SET TimeFormat='h:mm:ss TT';&lt;BR /&gt;SET DateFormat='M/D/YYYY';&lt;BR /&gt;SET TimestampFormat='M/D/YYYY h:mm:ss[.fffffffff] TT';&lt;BR /&gt;SET FirstWeekDay=6;&lt;BR /&gt;SET BrokenWeeks=1;&lt;BR /&gt;SET ReferenceDay=0;&lt;BR /&gt;SET FirstMonthOfYear=1;&lt;BR /&gt;SET CollationLocale='en-US';&lt;BR /&gt;SET MonthNames='Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec';&lt;BR /&gt;SET LongMonthNames='January;February;March;April;May;June;July;August;September;October;November;December';&lt;BR /&gt;SET DayNames='Mon;Tue;Wed;Thu;Fri;Sat;Sun';&lt;BR /&gt;SET LongDayNames='Monday;Tuesday;Wednesday;Thursday;Friday;Saturday;Sunday';&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NoConcatenate&lt;BR /&gt;TSTmp:&lt;BR /&gt;LOAD * Inline&lt;BR /&gt;[&lt;BR /&gt;Contract,Date,Time,Depth Level,Bid Quantity,Bid Price,Ask Price,Ask Quantity&lt;BR /&gt;ABCD Jan 2019,18.07.2018,06:00:00.193684787,0,,,,&lt;BR /&gt;ABCD Jan 2019,18.07.2018,07:55:00.125039582,0,0,43,30,43,70,0&lt;BR /&gt;ABCD Jan 2019,18.07.2018,08:00:00.146053080,0,1,43,30,43,70,2&lt;BR /&gt;];&lt;/P&gt;&lt;P&gt;NoConcatenate&lt;BR /&gt;TSData:&lt;BR /&gt;LOAD&lt;BR /&gt;Contract,&lt;BR /&gt;Date,&lt;BR /&gt;Time,&lt;BR /&gt;Timestamp#(Time, 'hh:mm:ss.fffffffff') as TSString,&lt;BR /&gt;Num(Timestamp#(Time, 'hh:mm:ss.fffffffff')) as TSNum,&lt;BR /&gt;[Depth Level],&lt;BR /&gt;[Bid Quantity],&lt;BR /&gt;[Bid Price],&lt;BR /&gt;[Ask Price],&lt;BR /&gt;[Ask Quantity]&lt;BR /&gt;Resident [TSTmp];&lt;/P&gt;&lt;P&gt;drop Table [TSTmp];&lt;/P&gt;&lt;P&gt;EXIT SCRIPT;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 14:14:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543699#M62775</guid>
      <dc:creator>vvira1316</dc:creator>
      <dc:date>2019-02-13T14:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543713#M62776</link>
      <description>&lt;P&gt;I think it's caused from the used number-system of Qlik which is limited in regard to the accuracy of a calculation and also to the max. number of digits- some background to it could you find here: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Rounding-Errors/ba-p/1468808" target="_blank" rel="noopener"&gt;Rounding-Errors&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;A workaround for you might be to load this field as a string and/or to split this field into a classical time-field and a millisecond-field. By a large dataset you should really consider if you really need this granularity and if to split it - see here why: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/The-Importance-Of-Being-Distinct/ba-p/1466796" target="_blank" rel="noopener"&gt;The-Importance-Of-Being-Distinct&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 14:19:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1543713#M62776</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2019-02-13T14:19:07Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1544052#M62777</link>
      <description>&lt;P&gt;any idea how to create a table with a complete day? 3 digits will be enough but I need a reference day from 00:00:00.000 to 23:59:59.999&lt;/P&gt;&lt;P&gt;Is there a possibility to create such a day?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 06:48:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1544052#M62777</guid>
      <dc:creator>krameralexander</dc:creator>
      <dc:date>2019-02-14T06:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: Timestamp cuts of fractals after 3 digits</title>
      <link>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1544073#M62778</link>
      <description>&lt;P&gt;Take a look on daystart() and dayend() and if you want to create a master time-table look here: &lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/The-Master-Time-Table/ba-p/1469392" target="_blank" rel="noopener"&gt;The-Master-Time-Table&lt;/A&gt;. The logic could be extended to milliseconds too, but you would create a dimension table with 86 M records and therefore it might be more appropriate to leave the millisecond-part or split it into a further field and dimension-table.&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 07:30:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Timestamp-cuts-of-fractals-after-3-digits/m-p/1544073#M62778</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2019-02-14T07:30:26Z</dc:date>
    </item>
  </channel>
</rss>

