<?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 prevent layer renumbering when republishing services in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160550#M6313</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have several services that are being used by other entities and they have scripted some things that query by the layer number.&amp;nbsp; I needed to add a new data layer to one of those services and when I republished it renumbered all of the data layers (which obviously broke their query).&amp;nbsp; Is there any way to lock the layer numbering that's done when you publish a service?&amp;nbsp; I know I could just publish a separate service for any new&amp;nbsp; data layers I needed to add but I would prefer not to if I don't have to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Jan 2016 12:44:00 GMT</pubDate>
    <dc:creator>LarisaKruger</dc:creator>
    <dc:date>2016-01-28T12:44:00Z</dc:date>
    <item>
      <title>prevent layer renumbering when republishing services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160550#M6313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have several services that are being used by other entities and they have scripted some things that query by the layer number.&amp;nbsp; I needed to add a new data layer to one of those services and when I republished it renumbered all of the data layers (which obviously broke their query).&amp;nbsp; Is there any way to lock the layer numbering that's done when you publish a service?&amp;nbsp; I know I could just publish a separate service for any new&amp;nbsp; data layers I needed to add but I would prefer not to if I don't have to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 12:44:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160550#M6313</guid>
      <dc:creator>LarisaKruger</dc:creator>
      <dc:date>2016-01-28T12:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: prevent layer renumbering when republishing services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160551#M6314</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Larisa,&lt;/P&gt;&lt;P&gt;If you are working on ArcGIS 10.3 and later, you could set up the map document to preserve layer and table IDs.&lt;/P&gt;&lt;P&gt;&lt;A href="http://server.arcgis.com/en/server/latest/publish-services/windows/map-authoring-considerations.htm#ESRI_SECTION1_4C54586DEB0445B4B97AF15856E546AB" title="http://server.arcgis.com/en/server/latest/publish-services/windows/map-authoring-considerations.htm#ESRI_SECTION1_4C54586DEB0445B4B97AF15856E546AB"&gt;Map authoring considerations—Documentation (10.3 and 10.3.1) | ArcGIS for Server&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 13:00:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160551#M6314</guid>
      <dc:creator>JayantaPoddar</dc:creator>
      <dc:date>2016-01-28T13:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: prevent layer renumbering when republishing services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160552#M6315</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Awesome! We are in the process of migrating to 10.3.1 right now. Just one more reason to do so. Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 13:06:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160552#M6315</guid>
      <dc:creator>LarisaKruger</dc:creator>
      <dc:date>2016-01-28T13:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: prevent layer renumbering when republishing services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160553#M6316</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Larisa:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully you do not use annotation in your mapservice as there is a bug with annotation in v10.3.1 that has supposedly been fixed in v10.4.&amp;nbsp; Just an FYI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 15:01:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160553#M6316</guid>
      <dc:creator>MichaelVolz</dc:creator>
      <dc:date>2016-01-28T15:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: prevent layer renumbering when republishing services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160554#M6317</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thankfully, no, just labeling.&amp;nbsp; But thanks for the heads up.&amp;nbsp; That is good to know and I will keep it in mind.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jan 2016 15:04:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/prevent-layer-renumbering-when-republishing/m-p/160554#M6317</guid>
      <dc:creator>LarisaKruger</dc:creator>
      <dc:date>2016-01-28T15:04:03Z</dc:date>
    </item>
  </channel>
</rss>

