Hi,
Just trying to set up a vRA 7 Blueprint and avoid having users duplicate "global" property values that apply to all sub-components - in this case vSphere machines (see screen shot).
For this I am setting a custom property e.g. "Company.Common.Environment" to value (e.g. "Prod-Tier2") at the top level of the request.
I've then got a second property (e.g. Reservation Policy ID) set at the next level down (vSphere machine in this case) that is linked to a vCO action that requires the value of the higher-level property as an input (bound field).
With debug code in the action, I've verified that the value of the property already set at the higher level ("Company.Common.Environment") is not being passed through to the vCO action bound to the property set at the lower level.
I've tried multiple configurations here including using nested blueprints as opposed to vSPhere machines directly in he blueprint (which is shown below), and assigning the lower level property doing the vCO lookup at the nested blueprint level. No combinations seem to work.
Can someone tell me if this is expected behavior, and advise if there are any possible workarounds?
Disappointing if this does not work because it means any vCO Action-linked property cannot make use of values from other locations in the request form.
Here is how the master and sub-components look at request time:
Here is the custom property definition. Note that this works perfectly if all the dependent property values are loted at the same level in the blueprint (e.g. all on the vSphere virtual machine, or all on a nested blueprint).
As you can see it is bound to the Company.Common.Environment property value.
Many thanks in advance for any info.
Regards,
Justin