<?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 Editing in a Server Object Extension in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/editing-in-a-server-object-extension/m-p/736325#M27965</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I know that the standard mechanism for web editing is to set up a feature service, however the issue that I have with that is that it is associated with a single transactional version (typically SDE.DEFAULT, but it can point at another version).&amp;nbsp; I have a situation where I may have many dozens of transactional versions representing multiple potential designs, and as such hitting a single version through a feature service doesn't seem to be quite the right fit. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have an idea for creating a Server Object Extension (SOE) which would expose what is essentially a REST endpoint for purposes of editing on a version of the users choosing.&amp;nbsp; The exposed SOE method might take the name of the version to apply the edit to, a feature identifier (probably a feature class name and and ObjectID), and an array of name/value pairs of how that feature should be updated.&amp;nbsp; Similar methods might work for object creation and deletion as well. I'm wondering if anyone has tried to do something like this before or might comment as to its wisdom?&amp;nbsp; It seems theoretically possible, but perhaps changing from one version to another in an SOE is just a really bad idea for some reason that I'm not currently aware of.&amp;nbsp; It seems a little hacky to me.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Dec 2013 14:08:06 GMT</pubDate>
    <dc:creator>RiverTaig1</dc:creator>
    <dc:date>2013-12-17T14:08:06Z</dc:date>
    <item>
      <title>Editing in a Server Object Extension</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/editing-in-a-server-object-extension/m-p/736325#M27965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I know that the standard mechanism for web editing is to set up a feature service, however the issue that I have with that is that it is associated with a single transactional version (typically SDE.DEFAULT, but it can point at another version).&amp;nbsp; I have a situation where I may have many dozens of transactional versions representing multiple potential designs, and as such hitting a single version through a feature service doesn't seem to be quite the right fit. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have an idea for creating a Server Object Extension (SOE) which would expose what is essentially a REST endpoint for purposes of editing on a version of the users choosing.&amp;nbsp; The exposed SOE method might take the name of the version to apply the edit to, a feature identifier (probably a feature class name and and ObjectID), and an array of name/value pairs of how that feature should be updated.&amp;nbsp; Similar methods might work for object creation and deletion as well. I'm wondering if anyone has tried to do something like this before or might comment as to its wisdom?&amp;nbsp; It seems theoretically possible, but perhaps changing from one version to another in an SOE is just a really bad idea for some reason that I'm not currently aware of.&amp;nbsp; It seems a little hacky to me.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 14:08:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/editing-in-a-server-object-extension/m-p/736325#M27965</guid>
      <dc:creator>RiverTaig1</dc:creator>
      <dc:date>2013-12-17T14:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Editing in a Server Object Extension</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/editing-in-a-server-object-extension/m-p/736326#M27966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It appears that at version 10.1 you can change a version on a FeatureLayer.&amp;nbsp; The documentation is here: &lt;/SPAN&gt;&lt;A href="https://developers.arcgis.com/en/javascript/jsapi/featurelayer-amd.html#setgdbversion"&gt;https://developers.arcgis.com/en/javascript/jsapi/featurelayer-amd.html#setgdbversion&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also, I found a 75 minute movie detailing editing from the ESRI Developer Conference at &lt;/SPAN&gt;&lt;A href="http://video.arcgis.com/watch/1175/building-web-editing-applications-with-arcgis-101-for-server"&gt;http://video.arcgis.com/watch/1175/building-web-editing-applications-with-arcgis-101-for-server&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; .&amp;nbsp; The most relevant parts related to versioning is aproximately 60 minutes into the presentation (but it's all good info)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Great documentation esri!!&amp;nbsp; You guys rock.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2013 16:08:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/editing-in-a-server-object-extension/m-p/736326#M27966</guid>
      <dc:creator>RiverTaig1</dc:creator>
      <dc:date>2013-12-17T16:08:16Z</dc:date>
    </item>
  </channel>
</rss>

