nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Customize parameter behaviour in Modelbuilder?

EvelynHsu

Are there ways to customize parameter behaviours in a model in ArcMap 10.8.1?

Specifically, I'd like to enable one model parameter only when another parameter (boolean type) is True.

In a script tool, I can achieve this by editing ToolValidator class. Can something similar be done with a model?

Encontre mais publicações marcadas com

Desktop

Accepted answers

DanPatterson

I don't see how that can be accomplished in modelbuilder, you may have to examine what is available via python's validation and switch from a model to a python tool, probably in Pro and not arcmap

All comments

DanPatterson

preconditions perhaps, for example

If Value Is (ModelBuilder)—ArcGIS Pro | Documentation

EvelynHsu

Thanks Dan. Perhaps I should add that I'm using ArcMap 10.8.1. Not the most ideal option...gotta make do with what is available 😕

DanPatterson

meaning you are left with

A quick tour of using preconditions—ArcMap | Documentation (arcgis.com)

Using If-Then-Else logic for branching—ArcMap | Documentation (arcgis.com)

EvelynHsu

Unfortunately preconditions and if-else logic don't quite give the same behaviour with model parameters.

Preconditions and if-else logic can be used to control whether a step (say, Step A) should be executed. But, if parameters of Step A have been marked as model parameters, then regardless of whether Step A is executed, its parameters are always marked as mandatory parameters of the model and input values are expected.

What we wanted is the ability to conditionally enable model parameters in modelbuilder: if Step A does not meet the precondition, then its parameters should also be optional.

DanPatterson

I don't see how that can be accomplished in modelbuilder, you may have to examine what is available via python's validation and switch from a model to a python tool, probably in Pro and not arcmap

EvelynHsu

Marking this as the solution as I couldn't find any other way to achieve it either. In the end we decided to switch to a python tool.

DanelleMalget1

I've been looking to do the same thing, but i need to keep the bulk of the analysis in modelbuilder. I've setup my parameter processing in a python tool/box and then added that tool to my model - but the pyt validation doesn't get exposed when i make that tools parameters as model parameters.

I'm about to try to make a regular toolbox (.atbx in Pro 3.5) and add the same tool validation at the TOOL Level, instead of where it is at the 'toolbox level' (it would seem) for a pyt.🤞

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.