If a field is read only and we omit to remove the variable in the save into fielhttps://community.appian.com/discussions/f/user-interface/186/if-a-field-is-read-only-and-we-omit-to-remove-the-variable-in-the-save-into-fielIf a field is read only and we omit to remove the variable in the save into field properties of the Node Inputs. Why would the system still capture a value and replace it when the task is submitted? We noticed that since we upgraded to 6.6 the dates ofen-USTelligent Community 12RE: If a field is read only and we omit to remove the variable in the save into fielhttps://community.appian.com/thread/432?ContentTypeID=1Mon, 25 Jun 2012 19:28:07 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:d27f22b1-152a-479d-8541-32e4abf4693fmjmalletI figured that was the fix, but wondered why it&#39;s only happening now in 6.6...<div style="clear:both;"></div>RE: If a field is read only and we omit to remove the variable in the save into fielhttps://community.appian.com/thread/431?ContentTypeID=1Mon, 25 Jun 2012 19:15:52 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b7f73667-cd28-4b17-aad6-9a78858365acMike CichyI believe date fields need to be mapped to an acp. Make sure you are not saving the acps into process variables in the data tab.<div style="clear:both;"></div>