<?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>idea Creating and updating features via a feature view in ArcGIS Enterprise should honor the view definition in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/creating-and-updating-features-via-a-feature-view/idi-p/927549</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Feature views in ArcGIS Enterprise are awesome. You can specify attribute and spatial filters as well as choose which fields are visible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When a user views/queries information from this view, only features matching those preset filters are returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if the same user either submits a new feature, or submits an edit for an existing feature, where the new feature does NOT match the filters, currently the view silently accepts the edit. This can result in a strange and un-intuitive situation where a user creates/edits a feature, only for it to immediately disappear since they no longer have the ability to view it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logically, I believe that the create and update endpoints should be amended so that they reject any attempt to submit a feature that does not match the defined filters. This then would&amp;nbsp;be a more complete implementation of the filtered view acting as a true security permission for those users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. Fred works in the North Island of New Zealand, and Sue works in the South Island. Currently, I can restrict Fred to only viewing features located in the North Island, but I also want to stop him from creating features located in the South Island.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Mar 2018 20:57:22 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2018-03-06T20:57:22Z</dc:date>
    <item>
      <title>Creating and updating features via a feature view in ArcGIS Enterprise should honor the view definition</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/creating-and-updating-features-via-a-feature-view/idi-p/927549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Feature views in ArcGIS Enterprise are awesome. You can specify attribute and spatial filters as well as choose which fields are visible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When a user views/queries information from this view, only features matching those preset filters are returned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if the same user either submits a new feature, or submits an edit for an existing feature, where the new feature does NOT match the filters, currently the view silently accepts the edit. This can result in a strange and un-intuitive situation where a user creates/edits a feature, only for it to immediately disappear since they no longer have the ability to view it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logically, I believe that the create and update endpoints should be amended so that they reject any attempt to submit a feature that does not match the defined filters. This then would&amp;nbsp;be a more complete implementation of the filtered view acting as a true security permission for those users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. Fred works in the North Island of New Zealand, and Sue works in the South Island. Currently, I can restrict Fred to only viewing features located in the North Island, but I also want to stop him from creating features located in the South Island.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2018 20:57:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/creating-and-updating-features-via-a-feature-view/idi-p/927549</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2018-03-06T20:57:22Z</dc:date>
    </item>
  </channel>
</rss>

