<?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 ArcGIS REST API Add Features with Editor Tracking Disabled in ArcGIS REST APIs and Services Questions</title>
    <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494870#M2362</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Background&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a growing number of Survey 123 apps that are published to our Portal (10.3.1) with associated Hosted Feature services. As time goes on requirements for changes (new fields) to the surveys become apparent which requires creating a new instance of the survey with a new hosted feature service. What we want to be able to do is push the data from the old survey feature service to the new survey feature service including persisting the editor tracking data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Methodology&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have decided to use python and the ArcGIS Rest API with the following methodology:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use "Query" to read the features form the OLD hosted feature service&lt;/LI&gt;&lt;LI&gt;Use "AddFeatures" to write the features to the&amp;nbsp;NEW hosted feature service&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In theory the data from all matching fields will be copied over and any new fields in the new hosted feature service will not be populated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In essence the above methodology works fine. The problem however is with the Editor&amp;nbsp;Tracking fields&amp;nbsp;&lt;/P&gt;&lt;UL style="color: #000000; background-color: #ffffff; font-size: 14.4px;"&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;created_user &lt;EM&gt;( alias: created_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;created_date &lt;EM&gt;( alias: created_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;last_edited_user &lt;EM&gt;( alias: last_edited_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;last_edited_date &lt;EM&gt;( alias: last_edited_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We want the data in the editor tracking fields in the old service written to the new service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we leave editor tracking enabled and run the script to copy the data from the old service to the new service the editor fields are populated with the current user and date/time as when the script was run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we disable editor tracking the editor tracking fields are not populated at all??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can see the editor tracking fields in the json returned by the "Query" request and this is being passed to the "AddFeatures" request. The data is not populated in the new service but all other data is?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to populate editor tracking fields in a hosted feature service with data other than have them automatically populate with current user current date/time etc?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anybody has come across this issue and has a valid solution that would be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Callum&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Nov 2016 19:53:05 GMT</pubDate>
    <dc:creator>CallumSmith2</dc:creator>
    <dc:date>2016-11-02T19:53:05Z</dc:date>
    <item>
      <title>ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494870#M2362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Background&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a growing number of Survey 123 apps that are published to our Portal (10.3.1) with associated Hosted Feature services. As time goes on requirements for changes (new fields) to the surveys become apparent which requires creating a new instance of the survey with a new hosted feature service. What we want to be able to do is push the data from the old survey feature service to the new survey feature service including persisting the editor tracking data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Methodology&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have decided to use python and the ArcGIS Rest API with the following methodology:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use "Query" to read the features form the OLD hosted feature service&lt;/LI&gt;&lt;LI&gt;Use "AddFeatures" to write the features to the&amp;nbsp;NEW hosted feature service&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In theory the data from all matching fields will be copied over and any new fields in the new hosted feature service will not be populated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In essence the above methodology works fine. The problem however is with the Editor&amp;nbsp;Tracking fields&amp;nbsp;&lt;/P&gt;&lt;UL style="color: #000000; background-color: #ffffff; font-size: 14.4px;"&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;created_user &lt;EM&gt;( alias: created_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;created_date &lt;EM&gt;( alias: created_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;last_edited_user &lt;EM&gt;( alias: last_edited_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="padding: 0px 0px 3px;"&gt;last_edited_date &lt;EM&gt;( alias: last_edited_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We want the data in the editor tracking fields in the old service written to the new service&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we leave editor tracking enabled and run the script to copy the data from the old service to the new service the editor fields are populated with the current user and date/time as when the script was run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we disable editor tracking the editor tracking fields are not populated at all??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can see the editor tracking fields in the json returned by the "Query" request and this is being passed to the "AddFeatures" request. The data is not populated in the new service but all other data is?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to populate editor tracking fields in a hosted feature service with data other than have them automatically populate with current user current date/time etc?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anybody has come across this issue and has a valid solution that would be much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Callum&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Nov 2016 19:53:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494870#M2362</guid>
      <dc:creator>CallumSmith2</dc:creator>
      <dc:date>2016-11-02T19:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494871#M2363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have managed to figure out the issue. The editor tracking fields editing capability is disabled. Even when editor tracking is disabled these fields are still not editable! Dont know why I didn't notice that earlier...&lt;/P&gt;&lt;UL style="color: #000000; background-color: #ffffff; border: 0px; font-size: 14.4px; padding: 0px 0px 0px 30px;"&gt;&lt;LI style="border: 0px; font-weight: inherit; font-size: 14.4px; margin: 0.5ex 0px; padding: 0px 0px 3px;"&gt;created_user &lt;EM style="border: 0px; font-weight: inherit; font-size: 14.4px;"&gt;( alias: created_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="border: 0px; font-weight: inherit; font-size: 14.4px; margin: 0.5ex 0px; padding: 0px 0px 3px;"&gt;created_date &lt;EM style="border: 0px; font-weight: inherit; font-size: 14.4px;"&gt;( alias: created_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="border: 0px; font-weight: inherit; font-size: 14.4px; margin: 0.5ex 0px; padding: 0px 0px 3px;"&gt;last_edited_user &lt;EM style="border: 0px; font-weight: inherit; font-size: 14.4px;"&gt;( alias: last_edited_user , length: 255 , nullable: true , type: esriFieldTypeString , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;LI style="border: 0px; font-weight: inherit; font-size: 14.4px; margin: 0.5ex 0px; padding: 0px 0px 3px;"&gt;last_edited_date &lt;EM style="border: 0px; font-weight: inherit; font-size: 14.4px;"&gt;( alias: last_edited_date , length: 29 , nullable: true , type: esriFieldTypeDate , editable: false )&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I had do as part of my script is disable editor tracking and then enable editing on the fields using a UpdateDefinition Request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps someone else&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Callum&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Nov 2016 20:09:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494871#M2363</guid>
      <dc:creator>CallumSmith2</dc:creator>
      <dc:date>2016-11-03T20:09:29Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494872#M2364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you share the code please. I have the same issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Nov 2019 08:25:33 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494872#M2364</guid>
      <dc:creator>GregoryGasteratos</dc:creator>
      <dc:date>2019-11-29T08:25:33Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494873#M2365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gregory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry I missed your post. Are you still having issues? Do you still want the code?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Callum&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Dec 2019 20:15:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494873#M2365</guid>
      <dc:creator>CallumSmith2</dc:creator>
      <dc:date>2019-12-16T20:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494874#M2366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes please! The code would be very useful.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Greg.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Dec 2019 05:45:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494874#M2366</guid>
      <dc:creator>GregoryGasteratos</dc:creator>
      <dc:date>2019-12-17T05:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494875#M2367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gregory&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This may or may not help you sorry. Our scripts are split into modules for reuse so I can give you everything. Attached is the base script which should help you with the workflow we used (without too much of the detail sorry) I also wrote this a few years back so there may be netter ways of achieving this now with the ArcGIS api for python&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Callum&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Dec 2019 23:21:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494875#M2367</guid>
      <dc:creator>CallumSmith2</dc:creator>
      <dc:date>2019-12-18T23:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: ArcGIS REST API Add Features with Editor Tracking Disabled</title>
      <link>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494876#M2368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Dec 2019 05:44:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-rest-apis-and-services-questions/arcgis-rest-api-add-features-with-editor-tracking/m-p/494876#M2368</guid>
      <dc:creator>GregoryGasteratos</dc:creator>
      <dc:date>2019-12-20T05:44:49Z</dc:date>
    </item>
  </channel>
</rss>

