<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>The CDT mapping suddently can not pass verfication, can someone help me?</title><link>https://community.appian.com/discussions/f/general/18602/the-cdt-mapping-suddently-can-not-pass-verfication-can-someone-help-me</link><description>oneday, we accentely delete all CDTs in our project, so we decide recrate CDT from Oracle DB view. 
 Then we receive the errors: 
 The data source schema does not match the type mappings: Wrong column type in APPIAN.IC_V_EXPIRYDATEBLANK for column MSTID</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: The CDT mapping suddently can not pass verfication, can someone help me?</title><link>https://community.appian.com/thread/73226?ContentTypeID=1</link><pubDate>Fri, 10 Apr 2020 16:01:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:f9dc858d-2cdd-47d4-af17-8790b8a89e03</guid><dc:creator>davel001150</dc:creator><description>&lt;p&gt;I think you will have to touch the XSD files and update them yourself.&amp;nbsp; Expiry date, for instance, according to your schema is looking for a TIMESTAMP.&amp;nbsp; It looks as though Appian is trying to pass a NUMBER to it.&amp;nbsp; I think a hiccup in the XSD generation process occurred, and you&amp;#39;ll need to update XSD manually to correctly pass TIMESTAMP to that, which would map with Appian&amp;#39;s DateTime datatype.&lt;/p&gt;
&lt;p&gt;DateTimes in Appian are actually stored as miliseconds since epoch, which is standard for most operating systems.&amp;nbsp; Appian&amp;#39;s epoch is Jan 1, 2035, so it&amp;#39;s a negative integer.&amp;nbsp; It can also be represented as decimal days since epoch.&amp;nbsp; Either way, if there was a problem in the type conversion, it makes sense how it could expect NUMBER instead of TIMESTAMP.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>