<?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: May 2025 qlik sense update broke part of window function in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/May-2025-qlik-sense-update-broke-part-of-window-function/m-p/2541143#M109301</link>
    <description>&lt;P&gt;You are right, this behavior changed with the Qlik Sense May 2025 release and it looks like a regression in the Window() function when Distinct is applied to numeric/dual fields.&lt;/P&gt;&lt;P&gt;Qlik's own notes for May2025 also confirm that Window() underwent engine changes and fixes in that release, which likely introduced the side-effect you're hitting.&lt;BR /&gt;&lt;BR /&gt;I was reading somewhere that the same pattern over a text field still work.&lt;BR /&gt;&lt;BR /&gt;So for now you can&amp;nbsp; do a quick fix by converting the date/numeric field to text inside Distinct.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;!-- ScriptorStartFragment --&gt;&lt;STRONG&gt;Window(Count(DISTINCT Text(Floor(friday_date)))) as num_weeks&lt;/STRONG&gt;&lt;!-- ScriptorEndFragment --&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;This may avoid the broken numeric path.&lt;BR /&gt;&lt;BR /&gt;Also you can update to the latest May-2025 patch, since Qlik is actively fixing Window() issues in this release.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jan 2026 05:52:50 GMT</pubDate>
    <dc:creator>Sayed_Mannan</dc:creator>
    <dc:date>2026-01-20T05:52:50Z</dc:date>
    <item>
      <title>May 2025 qlik sense update broke part of window function</title>
      <link>https://community.qlik.com/t5/App-Development/May-2025-qlik-sense-update-broke-part-of-window-function/m-p/2539338#M109056</link>
      <description>&lt;P&gt;plan_query:&lt;BR /&gt;LOAD&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;friday_date,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;project,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;funding_type,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;start_dt,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;planned_mandays,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;window(count(DISTINCT friday_date)) as num_weeks,&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;window(count(DISTINCT project)) as num_projects&lt;BR /&gt;FROM [lib://AttachedFiles/Over Time Upload FY26.xlsx]&lt;BR /&gt;(ooxml, embedded labels, table is [Unpivoted Execution Plan]);&lt;BR /&gt;&lt;BR /&gt;Before the May 2025 qlik sense update this query worked as expected in the data load editor.&amp;nbsp; But now num_weeks returns 0 for every row.&amp;nbsp; This seems to be the case if I do something similar with any numeric field. friday_date is a date/numeric field.&amp;nbsp; However num_projects works just as expected and that seems to be because project is a string field, not numeric.&amp;nbsp; It correctly returns 29 for every row in this case.&amp;nbsp; I know there's workarounds to this specific case.&amp;nbsp; But in more complicated cases, the work arounds become messier.&amp;nbsp; So I'm wondering why this issue was introduced and whether there's a plan for it to be fixed.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 15:59:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/May-2025-qlik-sense-update-broke-part-of-window-function/m-p/2539338#M109056</guid>
      <dc:creator>JakeSchmitz</dc:creator>
      <dc:date>2025-12-16T15:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: May 2025 qlik sense update broke part of window function</title>
      <link>https://community.qlik.com/t5/App-Development/May-2025-qlik-sense-update-broke-part-of-window-function/m-p/2541143#M109301</link>
      <description>&lt;P&gt;You are right, this behavior changed with the Qlik Sense May 2025 release and it looks like a regression in the Window() function when Distinct is applied to numeric/dual fields.&lt;/P&gt;&lt;P&gt;Qlik's own notes for May2025 also confirm that Window() underwent engine changes and fixes in that release, which likely introduced the side-effect you're hitting.&lt;BR /&gt;&lt;BR /&gt;I was reading somewhere that the same pattern over a text field still work.&lt;BR /&gt;&lt;BR /&gt;So for now you can&amp;nbsp; do a quick fix by converting the date/numeric field to text inside Distinct.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;!-- ScriptorStartFragment --&gt;&lt;STRONG&gt;Window(Count(DISTINCT Text(Floor(friday_date)))) as num_weeks&lt;/STRONG&gt;&lt;!-- ScriptorEndFragment --&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;This may avoid the broken numeric path.&lt;BR /&gt;&lt;BR /&gt;Also you can update to the latest May-2025 patch, since Qlik is actively fixing Window() issues in this release.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 05:52:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/May-2025-qlik-sense-update-broke-part-of-window-function/m-p/2541143#M109301</guid>
      <dc:creator>Sayed_Mannan</dc:creator>
      <dc:date>2026-01-20T05:52:50Z</dc:date>
    </item>
  </channel>
</rss>

