Select to view content in your preferred language

ArcGIS Pro Model Builder Parameter Dependency Not Functional

788
5
07-11-2024 04:59 AM
KristieReece
Occasional Contributor

I am attempting to create a simple model in ArcGIS Pro. The model has two variable parameters - one of which should dependent on the other. However, when editing the model properties the Dependency field is greyed out, so I cannot set the dependency for this variable. 

The first variable is an input feature layer and the second is a list of fields from that feature layer. Documentation (https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/modelbuilder/model-parameters.h...) states this functionality exists; however, I cannot seem to achieve this on a model.  It works fine with a script though.

 

While researching this issue I came across a previous post on this topic, but it there was no resolution on the post. https://community.esri.com/t5/arcgis-pro-questions/parameter-dependency-non-functional-in-arcpro/td-...

Any assistance with this would be appreciated!

5 Replies
DanPatterson
MVP Esteemed Contributor

The list of fields from the feature layer would be a "derived" parameter

Model parameters—ArcGIS Pro | Documentation


... sort of retired...
0 Kudos
KristieReece
Occasional Contributor

The documentation states that derived parameters by default become an output. The parameter I am trying to set needs to be an input. Once the user selects the desired feature layer they need to specify the field within the layer to be used on when the tool runs.

DanPatterson
MVP Esteemed Contributor

that leaves "Dependency" in the link


... sort of retired...
0 Kudos
DRynne
by
Emerging Contributor

I am finding this issue as well, did you ever figure it out?

0 Kudos
KristieReece
Occasional Contributor

I'm not entirely sure what model this was in reference too, so I went poking through our toolbox to see if I could figure it out. We have some models that have the functionality to display fields from the previously selected feature class; however, these are all using pre-existing geoprocessing tools with the functionality already in place. 

 

I did find a development version of a tool that tried to implement that functionality and appears to be unsuccessful, The production version of that tool has the field hard coded instead of being parameterized.

0 Kudos