<?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: Append: Unexpected behavior scheduling tasks while preserving globalids in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/append-unexpected-behavior-scheduling-tasks-while/m-p/496186#M21808</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;UPDATE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After further investigation the environment variables not carrying over under scheduled tasking is indeed a bug.&amp;nbsp; I have been notified a patch has been made and this functionality will be availible in ArcGIS Pro 2.6.2.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Sep 2020 18:39:10 GMT</pubDate>
    <dc:creator>BrentDavis</dc:creator>
    <dc:date>2020-09-24T18:39:10Z</dc:date>
    <item>
      <title>Append: Unexpected behavior scheduling tasks while preserving globalids</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/append-unexpected-behavior-scheduling-tasks-while/m-p/496185#M21807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am trying to schedule the append geoprocessing tool with the 'Preserve Global IDs' environment variable set.&amp;nbsp; When the tool is scheduled the global IDs are not preserved.&amp;nbsp; If you look at the scheduled task calendar you can check that the 'Preserve Global ID' environment was not passed to the tool when scheduled to run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried a few things in order to get something to work.&amp;nbsp; The first thing was to uncheck and recheck the box next to Preserve Global IDs.&amp;nbsp; When I schedule the tool, the details of the tool history did show that 'Preserve Global IDs' environment was used, but it was still not preserving global IDs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, I set up the append tool as a model in ModelBuilder. I had a feeling there was a bug in the environment hierarchy with regard to how environment variables are passed to scheduled tools. I unchecked and rechecked the box next to 'Preserve Global IDs' for the append tool within a model I had built and it did preserve the Global IDs once the model was scheduled to run.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems what is happening is that the defaults are overriding was is set in the environment panes unless they are refreshed by unchecking and rechecking the global ID box.&amp;nbsp; Once the program detects a change in the environment pane it will pass them to the scheduled tool.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Sep 2020 23:14:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/append-unexpected-behavior-scheduling-tasks-while/m-p/496185#M21807</guid>
      <dc:creator>BrentDavis</dc:creator>
      <dc:date>2020-09-09T23:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Append: Unexpected behavior scheduling tasks while preserving globalids</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/append-unexpected-behavior-scheduling-tasks-while/m-p/496186#M21808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;UPDATE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After further investigation the environment variables not carrying over under scheduled tasking is indeed a bug.&amp;nbsp; I have been notified a patch has been made and this functionality will be availible in ArcGIS Pro 2.6.2.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Sep 2020 18:39:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/append-unexpected-behavior-scheduling-tasks-while/m-p/496186#M21808</guid>
      <dc:creator>BrentDavis</dc:creator>
      <dc:date>2020-09-24T18:39:10Z</dc:date>
    </item>
  </channel>
</rss>

