I have a tool that I created from a Python script which I update from time to time. Usually I will right-click the tool and choose Import Script, but lately this has been unavailable, as shown below:
enter image description here
This has been happening to almost all the tools I create, usually after a few imports. The problem is that if the script is cached the only workaround is to create a whole new interface, which can be pretty time-consuming.
Does anyone know why this happens?
I found this post on the Esri forums describing the same problem: http://forums.arcgis.com/threads/70829-Python-Import-Script-grayed-out
-
4Do you have a strong need to import the script into the tools cache? Why not just allow the ArcGIS script tool to point to the script (on disk) itself. Unless it is for portability or to "hide" the script from a user, there is no need to "Import Script"...RyanKDalton– RyanKDalton2012年12月03日 21:16:24 +00:00Commented Dec 3, 2012 at 21:16
-
I don't theoretically need to import the script, but sometimes it will become cached anyway (that is, making changes to the .py file doesn't affect the behavior of the script) and my way of "resetting" it is to use the Import Script function.bertday– bertday2012年12月03日 21:47:56 +00:00Commented Dec 3, 2012 at 21:47
-
2I've never seen Python scripts get cached using the method @RyanDalton suggests so would recommend using that rather than Import Script which seems to be for Embedding scripts and password protecting toolsPolyGeo– PolyGeo ♦2012年12月04日 03:11:00 +00:00Commented Dec 4, 2012 at 3:11
-
1I rebuilt the tool without importing and it seems to be working better, so maybe that is the way to go. Thanks guys. I still don't understand though what would make the Import Script option disappear like that (suppose I did need to embed the script, for example). Anyone from Esri listening? :)bertday– bertday2012年12月04日 19:06:56 +00:00Commented Dec 4, 2012 at 19:06
2 Answers 2
The question has been answered in Geonet:
you need to export script and then you gonna be able to add a new script... Don't overwrite the script you want to import.
-
Could you link to the source?nmpeterson– nmpeterson2014年10月27日 18:28:55 +00:00Commented Oct 27, 2014 at 18:28
-
1geonet.esri.com/message/414853#414853offermann– offermann2014年10月29日 07:40:27 +00:00Commented Oct 29, 2014 at 7:40
In your Comment you ask if anyone from Esri is listening.
Although a number of Esri staff are regular users of this site, I suspect each will be focussed on their own area(s) of expertise.
Consequently, if this issue is still of concern to you then I think that you should submit this to your local Esri Support . However, before doing that I recommend that you try to have it in a reproducible form.