Simple python script tool work differently when published (DataLayer, Field dependency)

[MassimilianoGeppi]

Hi

Writing a simple script in ArcGIS Pro, like this

import arcpy

"""The source code of the tool."""
fc_orig = arcpy.GetParameter(0)
fc_origkey = arcpy.GetParameterAsText(1)

When i run it in ArcGIS Pro i can interact with layers in the TOC and observe the list of field in the combobox change the values as aspected

This beacuse the tool properties are set, as visible in this other picture

But when the same tool it was  published as "web tools" in the portal we have a corrisponding tool that doesn't have the same behavior.

In effect the second filed (combobox) doesn't update the values when the first combobox change layers, in the TOC as it happens in ArcGIS Pro?

Hoping i was clear i waiting for an idea.

Thank you in advance

max

[DonMorrison1]

I'm not surprised by this based on my experience with publishing Python toolboxes.  The  tool's "updateParameters" function, which provides the ability to react to parameter value changes, is never called in the published version of the tool, so the parameters are basically static, based on what the tool returns from the "getParameterInfo" function (which is called only when the tool is initialized).  I've never used dependent parameters so I'm not sure how that is affected. 

I was trying to find the ESRI help page that discusses this limitation but can't seem to find it right now. 

[MassimilianoGeppi]

Hi Don,

Thank you for your reply, yes we need an "Esri Help" or a "workaround" about this topic because we must to solve for an important customer.

How to populate dinamically a combobox of fields when i change the corresponding datalayer, selected from the TOC using a scripting tool published like a service.

m