https://community.esri.com/t5/arcgis-pro-questions/alter-field-data-management-doesn-t-work-with-quot/m-p/1380261#M78529 <P><SPAN>In the <A href="https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/the-in-memory-workspace.htm" target="_self">documentation provided by Esri</A>, it's mentioned that to write to the memory workspace, one should specify an output dataset path beginning with 'memory'. However, it's observed that the Alter Field tool only operates with 'in_memory', which is the legacy memory-based workspace designed for ArcMap. This discrepancy raises the question: was the Alter Field tool overlooked during the transition from 'in_memory' to 'memory' workspaces? Any insights into this matter would be greatly appreciated.</SPAN></P><P>&nbsp;</P><P>&nbsp;</P> Fri, 09 Feb 2024 13:19:33 GMT EloyGonzalez 2024-02-09T13:19:33Z https://community.esri.com/t5/arcgis-pro-questions/alter-field-data-management-doesn-t-work-with-quot/m-p/1380261#M78529 <P><SPAN>In the <A href="https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/the-in-memory-workspace.htm" target="_self">documentation provided by Esri</A>, it's mentioned that to write to the memory workspace, one should specify an output dataset path beginning with 'memory'. However, it's observed that the Alter Field tool only operates with 'in_memory', which is the legacy memory-based workspace designed for ArcMap. This discrepancy raises the question: was the Alter Field tool overlooked during the transition from 'in_memory' to 'memory' workspaces? Any insights into this matter would be greatly appreciated.</SPAN></P><P>&nbsp;</P><P>&nbsp;</P> Fri, 09 Feb 2024 13:19:33 GMT https://community.esri.com/t5/arcgis-pro-questions/alter-field-data-management-doesn-t-work-with-quot/m-p/1380261#M78529 EloyGonzalez 2024-02-09T13:19:33Z