Toolbox Compatibility ArcGIS Pro

[StevenGraf1]

Is there a document somewhere that describes ArcGIS Pro version compatibility for toolboxes.

I created a toolbox in Pro 2.1.2 and I can't use it in previous versions of Pro.  I have also created a toolbox in an earlier release of Pro and could not use it in a later release.  These are all python scripts imported into a toolbox.

[DanPatterson_Retired]

I have had no problems with scripts in a custom toolbox http://pro.arcgis.com/en/pro-app/arcpy/geoprocessing_and_python/a-quick-tour-of-creating-script-tool...

You can compare the differences between python and custom toolboxes here

http://pro.arcgis.com/en/pro-app/arcpy/geoprocessing_and_python/comparing-custom-and-python-toolboxe...

http://pro.arcgis.com/en/pro-app/arcpy/geoprocessing_and_python/adding-a-script-tool.htm

Unless you need some of the capabilities of a pure python toolbox, I have always found that I like to let Arc*  do the heavy lifting and simply define the parameters to use for the tool and attach the script using either sys.argv or arcpy.getparameterastext to associate the tool's parameters with parameters in the script.

Any of the things I have written have worked in all versions of PRO so far

[StevenGraf1]

My basic workflow is Create a toolbox in pro.  Create a new script tool in the toolbox.  Import my script in.  Set the parameters since I am using the GetParametersAsText variables in my script.

It seems random.  Some tools work.  Some just simply won't open in a newer or older versions of Pro.

I will continue to investigate.  It's possible I am using some desktop arcpy instead of going to the Pro arcpy help.

[DanPatterson_Retired]

For sure... if you don't have the python in the anaconda path 

C:\...your_install_folder...\bin\Python\envs\arcgispro-py3

all bets are off.  If you have ArcMap installed, it has its own python, but if you have other pythons, get rid of them and use a separate Anaconda distribution to keep all you environments clean and manageable.

[Robert_LeClair]

Also you may want to run the Analyze Tools for Pro geoprocessing tool that's in ArcMap and ArcGIS Pro.  The output is a text file that will tell you if the tool/script will run with no issues or error codes of what will not work with a hyperlink for resolution of the error.

[StevenGraf1]

Thanks!  I didn't know such a tool existed.

[DanPatterson_Retired]

Unless there is something undocumented... http://pro.arcgis.com/en/pro-app/tool-reference/data-management/analyzetoolsforpro.htm

works from going from 10.x to PRO.

There is no mention of going back and forth with Pro versions which seems to be your case

[Robert_LeClair]

That's true.  From what I know, 2.x functionality is not backwards compatible to 1.x functionality in ArcGIS Pro.  What version are you trying to go back to?

[StevenGraf1]

2.0.X to 2.1.X

[DanPatterson_Retired]

maybe a screengrab of your tool parameters and what your script does... maybe it is one of the input types being used to the tool that is the issue.  

I can confirm that featureclasses and rasters as inputs and outputs cause no problems with anything I produce.  I haven't been accessing geodatabases or any of that sde stuff.  Worth a shot comparing the differences between the no-problem vs the-problem tool parameters