https://community.esri.com/t5/arcgis-pro-ideas/improved-gp-tool-publishing-approve-changes-to/idi-p/1410497 <P>When publishing a GP tool (after a tool is run in ArcGIS Pro) to become a geoprocessing tool it is possible to see a major breaking issue.&nbsp;</P><P>Recently we found that a shared path:</P><P>"\\server\share\contentfolder\myDB.sde\myFeatureLayer"</P><P>Was being mangled in the publication/conversion process. Pro is taking in these strings\paths and inferring in them that they need to be made "Server" friendly based on assumed needs.</P><P>The above folder was being turned into:</P><P>"%scratchworkspace%\\server\share\contentfolder\myDB.sde\myFeatureLayer"</P><P>This then means that all connections/functions depending on these strings are now broken. The big issue we have is that this script/tool is now broken, and while the tool will publish the function will not work and will return a lovely 99999 error that the tool could not be executed.</P><P>What we need is a way to review/approve the changes being made to a GP tool that is being published so that Pro is not making a change that in fact is not needed to happen and breaking the script in such a way that renders it inoperative.</P><P>Troubleshooting and diagnosing this issue was complex, it required connecting to the ArcGIS-Config folder where it was published and running the script locally to the server to get to the "path not found" level issue from where the folder/string was changed.</P> Tue, 16 Apr 2024 18:16:04 GMT DEWright_CA 2024-04-16T18:16:04Z https://community.esri.com/t5/arcgis-pro-ideas/improved-gp-tool-publishing-approve-changes-to/idi-p/1410497 <P>When publishing a GP tool (after a tool is run in ArcGIS Pro) to become a geoprocessing tool it is possible to see a major breaking issue.&nbsp;</P><P>Recently we found that a shared path:</P><P>"\\server\share\contentfolder\myDB.sde\myFeatureLayer"</P><P>Was being mangled in the publication/conversion process. Pro is taking in these strings\paths and inferring in them that they need to be made "Server" friendly based on assumed needs.</P><P>The above folder was being turned into:</P><P>"%scratchworkspace%\\server\share\contentfolder\myDB.sde\myFeatureLayer"</P><P>This then means that all connections/functions depending on these strings are now broken. The big issue we have is that this script/tool is now broken, and while the tool will publish the function will not work and will return a lovely 99999 error that the tool could not be executed.</P><P>What we need is a way to review/approve the changes being made to a GP tool that is being published so that Pro is not making a change that in fact is not needed to happen and breaking the script in such a way that renders it inoperative.</P><P>Troubleshooting and diagnosing this issue was complex, it required connecting to the ArcGIS-Config folder where it was published and running the script locally to the server to get to the "path not found" level issue from where the folder/string was changed.</P> Tue, 16 Apr 2024 18:16:04 GMT https://community.esri.com/t5/arcgis-pro-ideas/improved-gp-tool-publishing-approve-changes-to/idi-p/1410497 DEWright_CA 2024-04-16T18:16:04Z