<?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: FeatureDataForm, Commit button disabled in ArcGIS API for Silverlight Questions</title>
    <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266833#M6956</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Looks like a bug.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We'll try to fix it in a future version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for reporting that.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Sep 2011 14:22:11 GMT</pubDate>
    <dc:creator>DominiqueBroux</dc:creator>
    <dc:date>2011-09-20T14:22:11Z</dc:date>
    <item>
      <title>FeatureDataForm, Commit button disabled</title>
      <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266832#M6955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am using feature templates for using the creation of features. The form is prefilled with the values from the template after the feature creation. However when you do not change the contents of a field, the commit button remains disabled. Can you make the button always enabled and let the application validate if the input was correct?. It is strange that the form decide what correct is or not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Johnny&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2011 05:04:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266832#M6955</guid>
      <dc:creator>JohnnyPenet</dc:creator>
      <dc:date>2011-09-20T05:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: FeatureDataForm, Commit button disabled</title>
      <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266833#M6956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Looks like a bug.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;We'll try to fix it in a future version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for reporting that.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2011 14:22:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266833#M6956</guid>
      <dc:creator>DominiqueBroux</dc:creator>
      <dc:date>2011-09-20T14:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: FeatureDataForm, Commit button disabled</title>
      <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266834#M6957</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Dominique,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you for your quick response. I will try a work around for now. I am doing a lot of low ESRI API in Silverlight,by using PRISM/MEF and MVVM. I am currently looking at your MapPrinting, great stuff !!!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Johnny&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Looks like a bug.&lt;BR /&gt; &lt;BR /&gt;We'll try to fix it in a future version.&lt;BR /&gt; &lt;BR /&gt;Thanks for reporting that.&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2011 17:27:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266834#M6957</guid>
      <dc:creator>JohnnyPenet</dc:creator>
      <dc:date>2011-09-20T17:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: FeatureDataForm, Commit button disabled</title>
      <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266835#M6958</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Johnny,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for your nice comment about the mapprinting sample:)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After more thoughts concerning the featuredataform, I am no more sure it's a bug.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The feature is created with its default attributes as soon as you click on the map.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Then, the feature dataform is only useful if you want to modify some attributes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you don't modify any values, you can kill the dataform and the feature is created with its default values.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Perhaps confusing?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Sep 2011 12:09:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featuredataform-commit-button-disabled/m-p/266835#M6958</guid>
      <dc:creator>DominiqueBroux</dc:creator>
      <dc:date>2011-09-21T12:09:12Z</dc:date>
    </item>
  </channel>
</rss>

