<?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>idea Re: Global Transformation DateTime Offset - Replicate - Status changed to: Delivered in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Global-Transformation-DateTime-Offset-Replicate/idc-p/1769289#M4584</link>
    <description>&lt;P&gt;Thank you for the feedback.&amp;nbsp; This feature will be generally available in April 2021.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Dec 2020 15:11:07 GMT</pubDate>
    <dc:creator>Shelley_Brennan</dc:creator>
    <dc:date>2020-12-17T15:11:07Z</dc:date>
    <item>
      <title>Global Transformation DateTime Offset - Replicate</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Global-Transformation-DateTime-Offset-Replicate/idi-p/1761690</link>
      <description>&lt;P&gt;We have a use case where a downstream pipeline is dependent on &lt;EM&gt;&lt;STRONG&gt;datetime&lt;/STRONG&gt;&lt;/EM&gt; columns transformed to &lt;EM&gt;&lt;STRONG&gt;datetime offset&lt;/STRONG&gt;&lt;/EM&gt;&amp;nbsp;. &amp;nbsp;Currently the only way to do this in &lt;LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"&gt;&lt;/LI-PRODUCT&gt; is to do the transformation at the table level. &amp;nbsp;This is not scalable and is not able to easily allow schema additions or changes with &lt;EM&gt;&lt;STRONG&gt;datetime&lt;/STRONG&gt;&lt;/EM&gt; data types without precarious communication processes. &amp;nbsp;The lack of global transformation to this data type is preventing us from using&amp;nbsp;&lt;LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;as our data integration tool and we have to rely on the current AWS service we purchased&amp;nbsp;&lt;LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;to replace. &amp;nbsp;We're currently forced to go to production using the AWS services next week and have lost some credibility within our stakeholder community.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Source system - &amp;nbsp;2020-01-30 00:00:00.000&lt;BR /&gt;Preferred output -&lt;SPAN&gt;&amp;nbsp; 2020-01-30T00:00:00.000Z&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2020 20:19:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Global-Transformation-DateTime-Offset-Replicate/idi-p/1761690</guid>
      <dc:creator>ResMed_LesB</dc:creator>
      <dc:date>2020-11-13T20:19:43Z</dc:date>
    </item>
    <item>
      <title>Re: Global Transformation DateTime Offset - Replicate - Status changed to: Delivered</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Global-Transformation-DateTime-Offset-Replicate/idc-p/1769289#M4584</link>
      <description>&lt;P&gt;Thank you for the feedback.&amp;nbsp; This feature will be generally available in April 2021.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 15:11:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Global-Transformation-DateTime-Offset-Replicate/idc-p/1769289#M4584</guid>
      <dc:creator>Shelley_Brennan</dc:creator>
      <dc:date>2020-12-17T15:11:07Z</dc:date>
    </item>
  </channel>
</rss>

