Update the export ribbon configuration file so other ArcGIS Pro users can access custom script tools
Our organization has a number of custom python tools that we use on a daily basis, so we’ve added them to a few custom ribbons. We have one person in our organization who makes changes to our ArcGIS Pro project and then that person will export their ribbon configuration and share it along with the ArcGIS Pro template (which includes all the custom script tools) for her colleagues to use so that everyone has the same editing environment. Since we are still in the process of refining our ArcGIS Pro environment to make it as optimal as possible, there are new versions quite frequently. What we’ve noticed is that in the .proExportedUI file, for the custom script tools, the file path is hardcoded into the configuration file so when another user imports it into ArcGIS Pro on their machine, the custom tools break (since it can’t access the location).
It’s quite tedious to re-set all the custom python tools in the custom ribbons each time there’s an update. Also, if any new folks join our team, they will also need to re-set the custom ribbons for every custom tool before they can start working and using the script tools in ArcGIS Pro. We have explored the option of putting the tools on a shared drive that everyone has access to, but we are worried about potential performance issues, and there is an increased risk of someone accidentally deleting the python tool which would delete it for everyone.
The functionality we are hoping to see is a way to change the hardcoded file path from the .proExportedUI for custom python tools so that when other users import the ribbon configurations, the custom script tools will not break.