Hello,

I have a home-brew component that has the requirement that at least one of two parameters must be populated before the component will be validated (turn from red to blue).

I have it set that both parameters are mandatory and I use an Enable script in each parameter that checks for the absence of content in the other parameter and if that criterion is satisfied then the parameter is Enabled.

'Enable script for Parameter 1
parameter('parameter 2') eq ''

Thus, the component starts with both parameters flagged as required, and then providing a value to either parameter disables the other and the component is validated. It should be the case that, with normal usage, the component can only ever have a maximum of one of those parameters populated at any one time.

This all works perfectly ... until I have one of the parameters initialized using a global property. It appears that in such a case the basic Enable script will not recognize the globally initialized parameter as having content and therefore the component will not validate.

Is there a more sophisticated way to construct the Enable script such that it can recognize the instance that a parameter has been set to be initialized with a global property.

Note: The same behavior is seen if the parameter is initialized by the following methods:

• Global Property
• Data Property
• Parent Parameter

Thanks in advance - Tris

​​​​​​​