<?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 Field validation with updateFeatures in ArcGIS REST APIs and Services Questions</title>
    <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/field-validation-with-updatefeatures/m-p/131833#M606</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a process that uses updateFeatures to update features with values from another application which has no awareness of the feature layer's schema.&amp;nbsp; The process works&amp;nbsp;as expected when all of the attributes for the supplied features are valid for the layer's schema, but if any of the attributes are not valid (ex, a single string value is one character longer then the field accepts), the entire updateFeatures call fails with "ArcGISRequestError: 500: Unable to complete operation".&amp;nbsp; The details are "Unable to perform updateFeatures operation."&amp;nbsp; I see similar behavior when submitting the same update through the html form accessed in the REST Services Directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to validate the feature data for the request and/or configure the feature service so that it's not an all-or-nothing operation, or do we need to implement all field-level validation processing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Aug 2020 21:17:18 GMT</pubDate>
    <dc:creator>SparkyT19</dc:creator>
    <dc:date>2020-08-26T21:17:18Z</dc:date>
    <item>
      <title>Field validation with updateFeatures</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/field-validation-with-updatefeatures/m-p/131833#M606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a process that uses updateFeatures to update features with values from another application which has no awareness of the feature layer's schema.&amp;nbsp; The process works&amp;nbsp;as expected when all of the attributes for the supplied features are valid for the layer's schema, but if any of the attributes are not valid (ex, a single string value is one character longer then the field accepts), the entire updateFeatures call fails with "ArcGISRequestError: 500: Unable to complete operation".&amp;nbsp; The details are "Unable to perform updateFeatures operation."&amp;nbsp; I see similar behavior when submitting the same update through the html form accessed in the REST Services Directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to validate the feature data for the request and/or configure the feature service so that it's not an all-or-nothing operation, or do we need to implement all field-level validation processing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Aug 2020 21:17:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/field-validation-with-updatefeatures/m-p/131833#M606</guid>
      <dc:creator>SparkyT19</dc:creator>
      <dc:date>2020-08-26T21:17:18Z</dc:date>
    </item>
  </channel>
</rss>

