<?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: intervalmatch on client works, but not as a task? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1826352#M1214011</link>
    <description>&lt;P&gt;I couldn't provide an answer only some hints. Within the help to the intervalmatch are remarks regarding the included data - of course the interval-fields must be numeric but also that there could be unexpected results if there are NULL's which should be checked/replaced in beforehand.&lt;/P&gt;&lt;P&gt;Therefore I suggest to make a quick test with a smaller subset of the data - with any where-conditions which surely excludes possible NULL's and if this worked to extend the dataset to find the causing records (maybe there is an issue with the data-quality) and/or to implement logics to replace the NULL's with real values.&lt;/P&gt;&lt;P&gt;Beside this you could consider to replace the inbuilt intervalmatch-feature with an internal while-loop like:&lt;/P&gt;&lt;P&gt;load [from]+ iterno() - 1 as Date, * from Source&lt;BR /&gt;while [from] + iterno() - 1 &amp;lt;= to;&lt;/P&gt;&lt;P&gt;which is my preferred approach for such tasks.&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
    <pubDate>Tue, 03 Aug 2021 13:17:49 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2021-08-03T13:17:49Z</dc:date>
    <item>
      <title>intervalmatch on client works, but not as a task?</title>
      <link>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1824463#M1213858</link>
      <description>&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;I have a strange problem, at least it seems strange to me.&lt;/P&gt;&lt;P&gt;However, if i run this script on my client it runs through perfect:&lt;/P&gt;&lt;P&gt;FST_DATEI_FZH_SERVICEFALL_EVENT_PROGR1:&lt;BR /&gt;load&lt;BR /&gt;Text(FGNR7) as FGNR7_FST_DATEI_PROGR,&lt;BR /&gt;Text(FGNR17) as FGNR17_FST_DATEI_PROGR,&lt;BR /&gt;timestamp(DIAG_DATETIME) as DIAG_DATETIME_FST_DATEI_PROGR,&lt;BR /&gt;time(DIAG_DATETIME - (10/86400)) as DIAG_DATETIME_FST_DATEI_PROGR_UG,&lt;BR /&gt;time(DIAG_DATETIME + (10/86400)) as DIAG_DATETIME_FST_DATEI_PROGR_OG,&lt;BR /&gt;timestamp(ERRTIME) as ERRTIME_FST_DATEI_PROGR,&lt;BR /&gt;Year(ERRTIME)&amp;amp; '-' &amp;amp;num(Month(ERRTIME),00) as ERRTIME_JAHR_MONAT_FST_DATEI_PROGR,&lt;BR /&gt;DATEINAME as DATEINAME_FST_DATEI_PROGR,&lt;BR /&gt;1 as ZAEHL_PROGR_ABG_FST_DATEI_PROGR&lt;BR /&gt;from&lt;BR /&gt;$(vPfad)FST_DATEI_PROGR.qvd (qvd)&lt;BR /&gt;where exists (FGNR17_DIM_FAHRZEUG, FGNR17)&lt;BR /&gt;;&lt;/P&gt;&lt;P&gt;FZH_SERVICEFALL_EVENT_PROGR:&lt;BR /&gt;load&lt;BR /&gt;Text(FGNR7_FZA) as FGNR7_FST_DATEI_PROGR,&lt;BR /&gt;Text(FGNR17_FZA) as &lt;FONT color="#FF0000"&gt;FGNR17_FST_DATEI_PROGR&lt;/FONT&gt;,&lt;BR /&gt;Time(Frac(timestamp(REFERENZ_DT))) as &lt;FONT color="#FF0000"&gt;REFERENZ_DT_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG&lt;/FONT&gt;,&lt;BR /&gt;num(EVENT_ID_EVENT) as EVENT_ID_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG,&lt;BR /&gt;num(EVENT_ID_PROGR) as EVENT_ID_FZH_EV_PROGRAMMIERUNG_ABG,&lt;BR /&gt;STATUS as STATUS_FZH_EV_PROGRAMMIERUNG_ABG,&lt;BR /&gt;if (isnull(EVENT_ID_EVENT),0,1) as ZAEHL_PROGR_ABG_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG_TEMP,&lt;BR /&gt;if (isnull(EVENT_ID_PROGR),0,1) as ZAEHL_PROGR_ABG_FZH_EV_PROGRAMMIERUNG_ABG_TEMP,&lt;BR /&gt;timestamp#(mid(timestamp(INSERT_DATE_FZA,'DD.MM.YYYY hh:mm:ss'),1,16),'DD.MM.YYYY hh:mm') as INSERT_DATE_FZH_EV_PROGRAMMIERUNG_ABG&lt;BR /&gt;from&lt;BR /&gt;$(vPfad)FZH_SERVICEFALL_EVENT_PROGR.qvd (qvd)&lt;BR /&gt;;&lt;/P&gt;&lt;P&gt;inner join INTERVALMATCH (&lt;FONT color="#FF0000"&gt;REFERENZ_DT_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG&lt;/FONT&gt;, &lt;FONT color="#FF0000"&gt;FGNR17_FST_DATEI_PROGR&lt;/FONT&gt;)&lt;BR /&gt;load DIAG_DATETIME_FST_DATEI_PROGR_UG, DIAG_DATETIME_FST_DATEI_PROGR_OG, FGNR7_FST_DATEI_PROGR, FGNR17_FST_DATEI_PROGR resident FST_DATEI_FZH_SERVICEFALL_EVENT_PROGR1;&lt;/P&gt;&lt;P&gt;if I create a task i get the following error:&lt;/P&gt;&lt;P&gt;inner join INTERVALMATCH (REFERENZ_DT_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG, FGNR17_FST_DATEI_PROGR)&lt;BR /&gt;&amp;nbsp;load DIAG_DATETIME_FST_DATEI_PROGR_UG, DIAG_DATETIME_FST_DATEI_PROGR_OG, FGNR7_FST_DATEI_PROGR, FGNR17_FST_DATEI_PROGR resident FST_DATEI_FZH_SERVICEFALL_EVENT_PROGR1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&amp;nbsp;4 fields found: DIAG_DATETIME_FST_DATEI_PROGR_UG, DIAG_DATETIME_FST_DATEI_PROGR_OG, FGNR7_FST_DATEI_PROGR, FGNR17_FST_DATEI_PROGR,&lt;BR /&gt;&amp;nbsp;Error: &lt;FONT size="4" color="#FF0000"&gt;Interval Fields List not matching number of fields.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="4" color="#000000"&gt;am I overseeing any obvious?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="4" color="#000000"&gt;thanks!&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jul 2021 10:43:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1824463#M1213858</guid>
      <dc:creator>sebastianfaust</dc:creator>
      <dc:date>2021-07-26T10:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: intervalmatch on client works, but not as a task?</title>
      <link>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1826257#M1214001</link>
      <description>&lt;P&gt;I don't have a reply to this, I'm just looking for a solution or explanation for this error too:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;Interval Fields List not matching number of fields.&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is that? This suddenly started appearing in a QV document I'm running every month, made no changes whatsoever. I even added floor() functions to interval and matching field dates, so that there are no format integrity issues.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 08:04:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1826257#M1214001</guid>
      <dc:creator>FakeJupiter</dc:creator>
      <dc:date>2021-08-03T08:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: intervalmatch on client works, but not as a task?</title>
      <link>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1826352#M1214011</link>
      <description>&lt;P&gt;I couldn't provide an answer only some hints. Within the help to the intervalmatch are remarks regarding the included data - of course the interval-fields must be numeric but also that there could be unexpected results if there are NULL's which should be checked/replaced in beforehand.&lt;/P&gt;&lt;P&gt;Therefore I suggest to make a quick test with a smaller subset of the data - with any where-conditions which surely excludes possible NULL's and if this worked to extend the dataset to find the causing records (maybe there is an issue with the data-quality) and/or to implement logics to replace the NULL's with real values.&lt;/P&gt;&lt;P&gt;Beside this you could consider to replace the inbuilt intervalmatch-feature with an internal while-loop like:&lt;/P&gt;&lt;P&gt;load [from]+ iterno() - 1 as Date, * from Source&lt;BR /&gt;while [from] + iterno() - 1 &amp;lt;= to;&lt;/P&gt;&lt;P&gt;which is my preferred approach for such tasks.&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 13:17:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1826352#M1214011</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2021-08-03T13:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: intervalmatch on client works, but not as a task?</title>
      <link>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1996510#M1221333</link>
      <description>&lt;P&gt;u need to put , key field in intervalmatch to the list of loaded field.&lt;/P&gt;
&lt;P&gt;and only load interval start- end&amp;nbsp;field and key field needed in load statement after intervalmatch.&lt;/P&gt;
&lt;P&gt;exam :&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;inner join INTERVALMATCH (REFERENZ_DT_FZH_SERVICEFALL_EVENT_TYP_PROGR_ABG, FGNR17_FST_DATEI_PROGR)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;load DIAG_DATETIME_FST_DATEI_PROGR_UG, &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;DIAG_DATETIME_FST_DATEI_PROGR_OG, &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;FGNR7_FST_DATEI_PROGR&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;resident FST_DATEI_FZH_SERVICEFALL_EVENT_PROGR1&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 09:32:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/intervalmatch-on-client-works-but-not-as-a-task/m-p/1996510#M1221333</guid>
      <dc:creator>andykrst</dc:creator>
      <dc:date>2022-10-25T09:32:08Z</dc:date>
    </item>
  </channel>
</rss>

