https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1044488#M60699 <P>I recently finished developing a python toolbox tool that ends up calling the arcpy.AddField_management() function about 25 times or so. I first developed it as a standalone script to get it working before I connected it up to my python toolbox. When I started testing the tool with the exact same data I found that the run time went up from ~20 seconds in standalone to ~80 seconds when run from a python toolbox inside an ArcGIS Pro map, a 4x increase. After playing around some more I found that it was definitely the AddField tool slowing it down, and then I noticed that if I close the attribute table in the Pro map the run time goes down to ~50 seconds.</P><P>So what I think is happening is that that the Pro map is busy revalidating locks and updating the GUI, etc. unnecessarily mid-script. I also notice that when the add field tools are called the "Add" and "Calculate" field buttons start alternating being grayed out, like it is cycling through locks and UI updates or something.</P><P><span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="These alternate being gray" style="width: 183px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/10280iFA52FA4D1B8B3154/image-size/large?v=v2&amp;px=999" role="button" title="Screenshot 2021-04-06 205356.jpg" alt="These alternate being gray" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">These alternate being gray</span></span></P><P>Is there any way to prevent this from happening? Can I somehow pause all that validation or whatever it is for the duration of my script? If not, is there a more efficient method to add fields? These short runtimes may not seem like a big deal but I now realize that I have many tools that have a LOT of calls to AddField and this is likely something that happens throughout my toolbox. I would like to make sure my code is as clean and efficient as practical.</P><P>All of the feature classes that have the add field function called on are in_memory layers, and are copied to new feature classes for the output layers.</P> Wed, 07 Apr 2021 01:11:05 GMT Justin_P 2021-04-07T01:11:05Z https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1044488#M60699 <P>I recently finished developing a python toolbox tool that ends up calling the arcpy.AddField_management() function about 25 times or so. I first developed it as a standalone script to get it working before I connected it up to my python toolbox. When I started testing the tool with the exact same data I found that the run time went up from ~20 seconds in standalone to ~80 seconds when run from a python toolbox inside an ArcGIS Pro map, a 4x increase. After playing around some more I found that it was definitely the AddField tool slowing it down, and then I noticed that if I close the attribute table in the Pro map the run time goes down to ~50 seconds.</P><P>So what I think is happening is that that the Pro map is busy revalidating locks and updating the GUI, etc. unnecessarily mid-script. I also notice that when the add field tools are called the "Add" and "Calculate" field buttons start alternating being grayed out, like it is cycling through locks and UI updates or something.</P><P><span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="These alternate being gray" style="width: 183px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/10280iFA52FA4D1B8B3154/image-size/large?v=v2&amp;px=999" role="button" title="Screenshot 2021-04-06 205356.jpg" alt="These alternate being gray" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">These alternate being gray</span></span></P><P>Is there any way to prevent this from happening? Can I somehow pause all that validation or whatever it is for the duration of my script? If not, is there a more efficient method to add fields? These short runtimes may not seem like a big deal but I now realize that I have many tools that have a LOT of calls to AddField and this is likely something that happens throughout my toolbox. I would like to make sure my code is as clean and efficient as practical.</P><P>All of the feature classes that have the add field function called on are in_memory layers, and are copied to new feature classes for the output layers.</P> Wed, 07 Apr 2021 01:11:05 GMT https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1044488#M60699 Justin_P 2021-04-07T01:11:05Z https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1044515#M60700 <P>use&nbsp;&nbsp;<A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-fields.htm" target="_blank">Add Fields (multiple) (Data Management)—ArcGIS Pro | Documentation</A></P><P>and keep the table closed</P> Wed, 07 Apr 2021 02:27:37 GMT https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1044515#M60700 DanPatterson 2021-04-07T02:27:37Z https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1045092#M60717 <P>Thanks, I updated my code to use Add Field<U><STRONG>s</STRONG></U> instead of Add Field in a bunch of places and it definitely sped it up quite a bit. It is still strange that having the attribute table open slows it down a noticeable amount.</P><P>As a note to others, this function is only available in ArcGIS Pro, and <STRONG>the parameter order in AddFields is actually different than the original AddField</STRONG>, which left with with a cryptic error for quite a while before I realized that.</P> Thu, 08 Apr 2021 15:46:26 GMT https://community.esri.com/t5/python-questions/python-toolbox-with-many-addfield-calls-runs/m-p/1045092#M60717 Justin_P 2021-04-08T15:46:26Z