<?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 How to keep date from becoming an integer in a mixed-format field in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902006#M74414</link>
    <description>&lt;P&gt;I have a load script that imports various CSVs and QVDs. One of the fields, ObservationValue, contains a mix of text, dates and numbers. Depending on the order that the files are loaded in, some of the dates get converted to integers, but I want them to stay in their original date format. I would rather not force the field to be Text. Is there any other way to guarantee that all values will appear exactly as they were in the source files?&lt;/P&gt;</description>
    <pubDate>Mon, 07 Mar 2022 20:28:59 GMT</pubDate>
    <dc:creator>Lauri</dc:creator>
    <dc:date>2022-03-07T20:28:59Z</dc:date>
    <item>
      <title>How to keep date from becoming an integer in a mixed-format field</title>
      <link>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902006#M74414</link>
      <description>&lt;P&gt;I have a load script that imports various CSVs and QVDs. One of the fields, ObservationValue, contains a mix of text, dates and numbers. Depending on the order that the files are loaded in, some of the dates get converted to integers, but I want them to stay in their original date format. I would rather not force the field to be Text. Is there any other way to guarantee that all values will appear exactly as they were in the source files?&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2022 20:28:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902006#M74414</guid>
      <dc:creator>Lauri</dc:creator>
      <dc:date>2022-03-07T20:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep date from becoming an integer in a mixed-format field</title>
      <link>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902017#M74416</link>
      <description>&lt;P&gt;If those values are loaded having a numerical value then the assigned text format will be taken from the first occurrence of each value. I think the only guaranteed way to keep the original text representation is to load as text (using the text() function).&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2022 20:48:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902017#M74416</guid>
      <dc:creator>MarcoWedel</dc:creator>
      <dc:date>2022-03-07T20:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep date from becoming an integer in a mixed-format field</title>
      <link>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902041#M74421</link>
      <description>&lt;P&gt;Thank you, Marco. The curious thing: Even within the same load, some dates appear as integers, and some don't. I can't determine why. I will use your suggestion with Text().&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2022 21:40:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/How-to-keep-date-from-becoming-an-integer-in-a-mixed-format/m-p/1902041#M74421</guid>
      <dc:creator>Lauri</dc:creator>
      <dc:date>2022-03-07T21:40:11Z</dc:date>
    </item>
  </channel>
</rss>

