Import/export native GP tool parameters to file

[Bud]

It would be great if we could export geoprocessing tool parameters to a file and store the file on a network drive. Then a different user could import those GP settings at a later date. Similar to field calculator scripts.

I'm aware that we can export a tool to Python code. Or make a model/toolbox. Those work as expected, but we're looking for something easier and lower risk for non-expert users. We still want our users to interact with and populate tool parameters; we just don't want them to have to manually fill in the parameters unnecessarily.

[AlfredBaldenweck]

This is definitely possible in a python toolbox https://community.esri.com/t5/python-questions/set-default-values-for-parameters-in-toolbox-for/m-p/...

[MErikReedAugusta]

I regularly call tools from the History when I'm building & testing tools, because then it auto-populates with whatever inputs were used in that particular run of the tool.

I've never thought to take that kind of approach when I'm providing the tools to my team; I usually bake the defaults into the tool.

But obviously, that only works with the tools I'm writing, and not the native ones.  I can see a few uses for this kind of functionality.

[AlfredBaldenweck]

Oh, I didn't understand what you were getting at. Yes, this would be a great option for native tools.

[Bud]

As a follow-up to @AlfredBaldenweck 's comment, I added the word "native" to the idea title to clarify.

Related: Import and export field map configuration

[Bud]

Geoprocessing: Save custom default parameters

[SSWoodward]

Thanks everyone for your comments.

Setting Custom, persistent defaults is possible in the current software with config files.   Check out this blog for more info.