Accepted Solutions
You'll have to apply the custom property to a machine object, then reference that in the binding using the name of that machine, not the _resource identifier.
So in this example, I have a blueprint that nests another blueprint called "CentOS7". I attach the vRA.Deployment.Tags property to the machine element in that blueprint and I can bind to it here.
You'll have to apply the custom property to a machine object, then reference that in the binding using the name of that machine, not the _resource identifier.
So in this example, I have a blueprint that nests another blueprint called "CentOS7". I attach the vRA.Deployment.Tags property to the machine element in that blueprint and I can bind to it here.
Yes this is easy to do within the blueprint for VM custom properties and software properties. I do this alot.
My scenario: Provide a catalog request for users to build a SharePoint instance, CRM instance, Web farm, etc using a simplifed form. I have already done all the scripting and all the testing. Its using all software components with Powershell with some NSX load balancer (soon). All requests work, but the forms are hideous. The user has to drill into each VM and fill in the fields, where I want it all on the main form (like the scren shot above). The other problem is all the software components have same properties to access a software share to download locally before install. I also need to import these blueprints across multiple disconnect domains (vra single tenants), but if I do, I have to go into each and every blueprint and software component to change the credentials used to access their appropiate software share (username, password, IP, share, etc) for each domain (same credentials in NOT an option). Its a pain. What I wanted was to build a "global" property group that consists of those properties definitions, and then when I export/import i do't have to change anything because each disconnect networks vRA instance will already have the configured property groups with all vm templates named the same as well so all should just work.
BUT how can I bind Property Groups? I have a property group that consists of 5 property definitions. I want to specify the property group in the vm level and bind it to the software component. I REALLY want it to load at the Blueprint level (so the catalog request form field on on the blueprint top level not in the sub sections)
Here is what I want it to look like:
I have tried many different configs. Blue print level propery definitions are not passed inside to the VM's or at least not by vRA that i can tell. So I moved the property groups and definitiosn to the VM level which makes the form options go under the main page...sucks.
But even now I can't bind property groups. I tried it like this thinking propery groups is an array or variables:
But it does not like this.
If I remove the [#] from the binding i get
Its almost seems Property groups are not supposed to be bound but only used for vRO workflows: https://theithollow.com/2017/05/22/vra-placement-decisions-dynamic-form/
Ideas?