<?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: Time not matching in Data &amp; Schema Discussions</title>
    <link>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3815#M281</link>
    <description>&lt;P&gt;If this is as simple as the same row on the DB is not matching what is in Incorta you'll need to log a ticket.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the interim, try loading a singe row from the DB into a new Incorta table and see if that matches.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;It'd be helpful to see screen caps as well in order to suggest more troubleshooting options.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Feb 2023 15:32:20 GMT</pubDate>
    <dc:creator>RADSr</dc:creator>
    <dc:date>2023-02-23T15:32:20Z</dc:date>
    <item>
      <title>Time not matching</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3814#M280</link>
      <description>&lt;P&gt;I time in DB column is coming as it is in the incorta table from query level. I executed the same script in DB and Schema level and the time was matching. Once the tables are loaded in incorta I explored the schema and found out that the time in DB was no longer matching in Incorta table. I have verified there is no conversion going on at all levels, just bringing the datetime column from DB to Incorta. Please help!&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2023 10:25:42 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3814#M280</guid>
      <dc:creator>Ashutosh_Rawat</dc:creator>
      <dc:date>2023-02-23T10:25:42Z</dc:date>
    </item>
    <item>
      <title>Re: Time not matching</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3815#M281</link>
      <description>&lt;P&gt;If this is as simple as the same row on the DB is not matching what is in Incorta you'll need to log a ticket.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the interim, try loading a singe row from the DB into a new Incorta table and see if that matches.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;It'd be helpful to see screen caps as well in order to suggest more troubleshooting options.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2023 15:32:20 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3815#M281</guid>
      <dc:creator>RADSr</dc:creator>
      <dc:date>2023-02-23T15:32:20Z</dc:date>
    </item>
    <item>
      <title>Re: Time not matching</title>
      <link>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3843#M297</link>
      <description>&lt;P&gt;It was just a data agent issue. Due to that issue there was a time lag of 5 hours in all our reports. Fixed by re-deploying the data&amp;nbsp;agent.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2023 20:18:23 GMT</pubDate>
      <guid>https://community.incorta.com/t5/data-schema-discussions/time-not-matching/m-p/3843#M297</guid>
      <dc:creator>Ashutosh_Rawat</dc:creator>
      <dc:date>2023-03-01T20:18:23Z</dc:date>
    </item>
  </channel>
</rss>

