ArcGIS Pro 3.4.2: The “mask” in the “environments” appears not to have a dropdown menu,

[JamalNUMAN]

ArcGIS Pro 3.4.2: The “mask” in the “environments” appears not to have a dropdown menu,

I observed that the “mask” in the “environments” appears not to have a dropdown menu, despite the fact that there are already some layers added to the content.

What could be the issue here?

Is this a bug?

[DanPatterson]

It is the use of shortcuts I suspect.

when validating the inputs to the tool, select the environments tab there and not after the fact.

A drop down will appear since the tool validation is aware of the possible inputs as it is being used.

When things are done after the fact, via a shortcut, you can still set the environment, but you have to select it after from the file on disk.

making shortcuts behave as the expected process adds a whole extra layer of unnecessary checking.

To access the drop down within environments simply keep within the modelbuilder tool settings and not those of the shortcuts.

[JamalNUMAN]

Here I’m referring to the “environments” of the entire model but not that belong to a particular tool

[DanPatterson]

That is what I am referring to as well. It is best to set it up on a per-tool basis within the tool itself since globally, there is no reference, hence no option to select a layer etc.  Within the tool's environments, Pro has more "information" about the environment settings that can apply to the selected tool within modelbuilder.

It is a workflow.  If you want to select layers etc, then set your environments from within the tool.  If you want to set them globally, then navigate to a featureclass or raster on disk.  Also, the tool environments offers the ability to select things from disk as well as the layer, another advantage of focusing on the tool's environments rather than global shortcuts.

[JamalNUMAN]

Two things:

• This feature used to be available in previous versions of Pro. A screenshot is provided for Pro 3.1.5, where the dropdown menu selection is available. This is most likely a bug in Pro 3.4.2
• Setting the “environment” at the model level is much more efficient than setting it for each individual tool.