<?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 Dates Formatted Differently through Salesforce API after Upgrading Connector in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Dates-Formatted-Differently-through-Salesforce-API-after/m-p/1447209#M1230471</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, everyone.&amp;nbsp; Our IT team has recently upgraded our server with new .NET framework and new connector (14.1) to comply with the forced TLS 1.2 requirement from Salesforce.&amp;nbsp; I am not an IT guy, so I'm out of my element here, but I have discovered that our dates are coming back formatted for SOQL (YYYY-MM-DD) when we use the new connector (.exe/14), but they come back formatted M/D/YYYY using our old connector (.dll/11).&amp;nbsp; This has caused many of our set analysis expressions referencing dates to evaluate to errors, no records, etc. and as a result, we have problems after refreshing.&amp;nbsp; If we refresh locally using our old .dll connector to Salesforce, no issue and all is well.&amp;nbsp; If we kick off on the server via task manager using the new .exe connector, we experience the issue.&amp;nbsp; Can anyone help?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 21:26:37 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2026-01-26T21:26:37Z</dc:date>
    <item>
      <title>Dates Formatted Differently through Salesforce API after Upgrading Connector</title>
      <link>https://community.qlik.com/t5/QlikView/Dates-Formatted-Differently-through-Salesforce-API-after/m-p/1447209#M1230471</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, everyone.&amp;nbsp; Our IT team has recently upgraded our server with new .NET framework and new connector (14.1) to comply with the forced TLS 1.2 requirement from Salesforce.&amp;nbsp; I am not an IT guy, so I'm out of my element here, but I have discovered that our dates are coming back formatted for SOQL (YYYY-MM-DD) when we use the new connector (.exe/14), but they come back formatted M/D/YYYY using our old connector (.dll/11).&amp;nbsp; This has caused many of our set analysis expressions referencing dates to evaluate to errors, no records, etc. and as a result, we have problems after refreshing.&amp;nbsp; If we refresh locally using our old .dll connector to Salesforce, no issue and all is well.&amp;nbsp; If we kick off on the server via task manager using the new .exe connector, we experience the issue.&amp;nbsp; Can anyone help?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 21:26:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dates-Formatted-Differently-through-Salesforce-API-after/m-p/1447209#M1230471</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2026-01-26T21:26:37Z</dc:date>
    </item>
  </channel>
</rss>

