<?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: PRO 2.3.1 Annotation Upgrade Dataset &amp; Python in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337903#M14818</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That #1 item is really difficult to overcome.&amp;nbsp; It would be great if ESRI could at least make the annotation viewable in ArcMap if you upgrade the annotation to be editable in Pro.&amp;nbsp; This would make the transition to Pro so much easier and less risky as this is a big sticking point.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Jun 2019 18:26:00 GMT</pubDate>
    <dc:creator>MichaelVolz</dc:creator>
    <dc:date>2019-06-25T18:26:00Z</dc:date>
    <item>
      <title>PRO 2.3.1 Annotation Upgrade Dataset &amp; Python</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337899#M14814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am going to start to upgrade the annotations in our databases and have some troubles, questions and concerns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; I read this in the documentation. "&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;Feature classes in the same feature dataset as the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN class="" style="color: #4c4c4c; background-color: #ffffff;"&gt;ArcGIS Pro&lt;/SPAN&gt;&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;annotation are also read-only in ArcMap."&amp;nbsp; So if I upgrade the annotation in our parcel fabric dataset, all points, lines, and polygons feature classes within that dataset will be uneditable in ArcMap?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;2.&amp;nbsp; Currently in Pro we cannot Publish Services to ArcGIS Server.&amp;nbsp; So if we upgrade our Annotation, this annotation cannot be published?&amp;nbsp; Can this be done in Python instead then?&amp;nbsp; Did I read correctly that Publishing Services to Server in Pro will be possible in 2.4 as long as we are on Server 10.6.1?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;3.&amp;nbsp; Once upgrade is there anyway to export or make a copy of the annotation to be viewed in ArcMap?&amp;nbsp; Just in case we edited a bunch of the upgraded annotation and later find that Pro is not going to work for us yet.&amp;nbsp; If not is this something in the works for later releases?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;4.&amp;nbsp; I tried running this script in both the Old Catalog and within Pro and got these errors.&amp;nbsp; I was testing it on a File Geodatabase before I use it on the sde database.&amp;nbsp; None of my feature classes are empty.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #4c4c4c; background-color: #ffffff;"&gt;Script:&lt;/SPAN&gt;&lt;/P&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;&lt;CODE&gt;&lt;SPAN class="keyword token"&gt;import&lt;/SPAN&gt; arcpy


arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;env&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;workspace &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; &lt;SPAN class="string token"&gt;"C:/temp/JFKSCopy/JFKS_Copy.gdb"&lt;/SPAN&gt;

arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;env&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;overwriteOutput &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; &lt;SPAN class="token boolean"&gt;True&lt;/SPAN&gt;


featClass &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;ListFeatureClasses&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;""&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;"Annotation"&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;


&lt;SPAN class="keyword token"&gt;for&lt;/SPAN&gt; row &lt;SPAN class="keyword token"&gt;in&lt;/SPAN&gt; featClass&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt;
    output &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; row &lt;SPAN class="operator token"&gt;+&lt;/SPAN&gt; &lt;SPAN class="string token"&gt;"_Pro"&lt;/SPAN&gt;
    copy &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;CopyFeatures_management&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;row&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; output&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
    &lt;SPAN class="keyword token"&gt;for&lt;/SPAN&gt; rows &lt;SPAN class="keyword token"&gt;in&lt;/SPAN&gt; copy&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt;
        arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;UpgradeDataset_management&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;rows&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Catalog error:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;Runtime error&amp;nbsp; Traceback (most recent call last):&amp;nbsp; &amp;nbsp;File "&amp;lt;string&amp;gt;", line 5, in &amp;lt;module&amp;gt;&amp;nbsp; &amp;nbsp;File "c:\program files (x86)\arcgis\desktop10.5\arcpy\arcpy\management.py", line 5645, in UpgradeDataset&amp;nbsp; &amp;nbsp; &amp;nbsp;raise e ExecuteError: ERROR 001267: Dataset type does not support upgrade.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pro error:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;Traceback (most recent call last):&lt;BR /&gt; File "&amp;lt;string&amp;gt;", line 5, in &amp;lt;module&amp;gt;&lt;BR /&gt; File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 6117, in UpgradeDataset&lt;BR /&gt; raise e&lt;BR /&gt; File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\management.py", line 6114, in UpgradeDataset&lt;BR /&gt; retval = convertArcObjectToPythonObject(gp.UpgradeDataset_management(*gp_fixargs((in_dataset,), True)))&lt;BR /&gt; File "c:\program files\arcgis\pro\Resources\arcpy\arcpy\geoprocessing\_base.py", line 498, in &amp;lt;lambda&amp;gt;&lt;BR /&gt; return lambda *args: val(*gp_fixargs(args, True))&lt;BR /&gt;arcgisscripting.ExecuteError: ERROR 002577: Upgrading annotation requires at least one annotation class and symbol.&lt;BR /&gt;Failed to execute (UpgradeDataset).&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Dec 2021 15:59:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337899#M14814</guid>
      <dc:creator>MatthewDriscoll</dc:creator>
      <dc:date>2021-12-11T15:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: PRO 2.3.1 Annotation Upgrade Dataset &amp; Python</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337900#M14815</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can comment on a few of the items above based on my research and experience:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Correct, if the annotation is in the feature dataset and it is upgraded you will NOT be able to view/edit/etc the feature contained within within ArcMap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. You can publish services to a stand-alone (unfederated) ArcGIS Server site via ArcGIS Pro, as of 2.3, with Python. Starting at ArcGIS Pro 2.4 there will be more user friendly UI component.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Publishing:&amp;nbsp;&lt;A href="https://enterprise.arcgis.com/en/server/latest/get-started/windows/what-s-new-in-arcgis-for-server.htm#ESRI_SECTION1_485BF14C8FBA41F5AB2D516290A0849C"&gt;https://enterprise.arcgis.com/en/server/latest/get-started/windows/what-s-new-in-arcgis-for-server.htm#ESRI_SECTION1_485BF14C8FBA41F5AB2D516290A0849C&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;arcpy.sharing:&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/arcpy/sharing/introduction-to-arcpy-sharing.htm"&gt;https://pro.arcgis.com/en/pro-app/arcpy/sharing/introduction-to-arcpy-sharing.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not tested publishing updated annotation to a stand-alone ArcGIS Server site. I can tell you that publishing from ArcGIS Pro to ArcGIS Enterprise works as expected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Once the annotation is upgraded with the ArcGIS Pro client, it will not be visible within ArcMap. This includes copying out annotation. If you wanted to have a "backup" before moving to ArcGIS Pro, I would recommend taking a verified backup of your Enterprise Geodatabase or make a copy to a file geodatabase. Remember that if the annotation is in a feature dataset, you would also have to replace the feature classes with the "backup" copy. This might cause you to lose edits made since the backup/upgrade. I have not tested this workflow out at this time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not know if this is something in the works for a future release. I would venture towards the no portion since the structure is different for annotation between ArcMap and ArcGIS Pro, hence the need to upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. I am not a Python expert. I would recommend reaching out to Esri technical support for help with this portion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2019 17:58:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337900#M14815</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2019-06-25T17:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: PRO 2.3.1 Annotation Upgrade Dataset &amp; Python</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337901#M14816</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you.&amp;nbsp; I will make sure to back everything up.&amp;nbsp; The Annotation Upgrade nuking any ability to fall back to ArcMap, and possibly publishing, is my biggest hurdle for moving the organization to Pro.&amp;nbsp; &amp;nbsp;We really will have to go all in or not at all.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2019 18:12:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337901#M14816</guid>
      <dc:creator>MatthewDriscoll</dc:creator>
      <dc:date>2019-06-25T18:12:23Z</dc:date>
    </item>
    <item>
      <title>Re: PRO 2.3.1 Annotation Upgrade Dataset &amp; Python</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337902#M14817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To some extent that may be true but there are other ways to get around that issue. With the upcoming ArcGIS Pro 2.4 release I understand that they will release the new parcel fabric.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could also upgrade your annotation, have the users that need to edit use ArcGIS Pro client and the other "non-editors" use web maps that you create within ArcGIS Enterprise for them to use.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2019 18:14:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337902#M14817</guid>
      <dc:creator>George_Thompson</dc:creator>
      <dc:date>2019-06-25T18:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: PRO 2.3.1 Annotation Upgrade Dataset &amp; Python</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337903#M14818</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That #1 item is really difficult to overcome.&amp;nbsp; It would be great if ESRI could at least make the annotation viewable in ArcMap if you upgrade the annotation to be editable in Pro.&amp;nbsp; This would make the transition to Pro so much easier and less risky as this is a big sticking point.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2019 18:26:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/pro-2-3-1-annotation-upgrade-dataset-python/m-p/337903#M14818</guid>
      <dc:creator>MichaelVolz</dc:creator>
      <dc:date>2019-06-25T18:26:00Z</dc:date>
    </item>
  </channel>
</rss>

