<?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: What is the best strategy for refreshing data sources for ArcGIS Server? in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/what-is-the-best-strategy-for-refreshing-data/m-p/74669#M2874</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, updating the shapefile, as long as the folder is a registered data store directory with ArcGIS Server, would flow through.&amp;nbsp; Update the shapefile, the Web App would show the changes on the next REST call. (e.g. Pan/zoom the map)&lt;/P&gt;&lt;P&gt;Schemalock should be set to FALSE in the service editor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Filegeodatabases is a better alternative than having shapefiles laying around. &lt;/P&gt;&lt;P&gt;Enterprise SDE and FME or some custom .net ETL process would be even better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I guess it depends on what you plan on doing. Or how much scalability you want to put into this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jul 2016 22:05:37 GMT</pubDate>
    <dc:creator>MichaelRobb</dc:creator>
    <dc:date>2016-07-27T22:05:37Z</dc:date>
    <item>
      <title>What is the best strategy for refreshing data sources for ArcGIS Server?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/what-is-the-best-strategy-for-refreshing-data/m-p/74668#M2873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have published a map document as a Map Service from ArcGIS Server that is consumed by ArcGIS Portal to display maps in a web app. The actual data source for the map document comes from a shape file. This shape file gets updated on nightly basis and I want the portal to reflect the updates to the map accordingly. &lt;/P&gt;&lt;P&gt;The question that I have is: would updating the shape file automatically update the map that is hosted on the Portal? If not, what steps should I follow to make it happen? I am new to this technologies so I will appreciate any help. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jul 2016 21:53:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/what-is-the-best-strategy-for-refreshing-data/m-p/74668#M2873</guid>
      <dc:creator>GagagDa_Morvi</dc:creator>
      <dc:date>2016-07-27T21:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best strategy for refreshing data sources for ArcGIS Server?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/what-is-the-best-strategy-for-refreshing-data/m-p/74669#M2874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, updating the shapefile, as long as the folder is a registered data store directory with ArcGIS Server, would flow through.&amp;nbsp; Update the shapefile, the Web App would show the changes on the next REST call. (e.g. Pan/zoom the map)&lt;/P&gt;&lt;P&gt;Schemalock should be set to FALSE in the service editor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Filegeodatabases is a better alternative than having shapefiles laying around. &lt;/P&gt;&lt;P&gt;Enterprise SDE and FME or some custom .net ETL process would be even better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But I guess it depends on what you plan on doing. Or how much scalability you want to put into this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jul 2016 22:05:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/what-is-the-best-strategy-for-refreshing-data/m-p/74669#M2874</guid>
      <dc:creator>MichaelRobb</dc:creator>
      <dc:date>2016-07-27T22:05:37Z</dc:date>
    </item>
  </channel>
</rss>

