<?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>I am experiencing a curious issue with a date field in the cloud (didn&amp;#39;t hav</title><link>https://community.appian.com/discussions/f/user-interface/126/i-am-experiencing-a-curious-issue-with-a-date-field-in-the-cloud-didn-t-hav</link><description>I am experiencing a curious issue with a date field in the cloud (didn&amp;#39;t have this issue before migrating to the cloud). When a user physically enters a date that is &amp;quot;incorrect&amp;quot; (i.e 2/31/2012 or 2/3/960) it is automatically converted to a &amp;quot;valid date</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: I am experiencing a curious issue with a date field in the cloud (didn't hav</title><link>https://community.appian.com/thread/293?ContentTypeID=1</link><pubDate>Sat, 12 May 2012 00:07:21 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:e420e56c-44b9-4635-a196-d59f9c87297b</guid><dc:creator>Sunny</dc:creator><description>This is the expected behavior with date fields. &lt;br /&gt;Please check the following thread for using JS validation on date fields:&lt;br /&gt;&lt;a href="https://forum.appian.com/suite/apps/resources/discussions/thread/4148"&gt;forum.appian.com/.../4148&lt;/a&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>