<?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>How to detect invalid input in a!dateField to disable a save button?</title><link>https://community.appian.com/discussions/f/user-interface/40359/how-to-detect-invalid-input-in-a-datefield-to-disable-a-save-button</link><description>Hi Appian community, 
 I&amp;#39;ve been dealing with a tricky validation problem with a!dateField and I wanted to share it here in case anyone has found a workaround. 
 I have a form with several date fields that toggle between a!dateField (edit mode) and a</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: How to detect invalid input in a!dateField to disable a save button?</title><link>https://community.appian.com/thread/154384?ContentTypeID=1</link><pubDate>Thu, 23 Apr 2026 15:28:26 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:19d28a84-536f-46aa-a376-45cf64e19078</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;a!dateField does not let you reliably detect invalid typed text, because Appian stores invalid input as null. If null is also valid, you must either rely on the field&amp;rsquo;s native validation or switch to a text field with custom parsing if you need the raw input.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>