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.
Recently we found that a shared path:
"\\server\share\contentfolder\myDB.sde\myFeatureLayer"
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.
The above folder was being turned into:
"%scratchworkspace%\\server\share\contentfolder\myDB.sde\myFeatureLayer"
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.
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.
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.
