Override Property Dictionary - Required "yes" in specific Catalog Item

[vMarkusK1985]

Hi,

Per default we have created a custom Network List as Dropdown List and set the first Network as required. -> Set in Infrastructure > Blueprints > Property Dictionary

Now we need a Catalog Item (vSphere VM) with a fixed Network. I already created a Build Profile for this Item the property’s “VirtualMachine.Network0.Name” and “VirtualMachine.Network0.ProfileName”.

But the first network is still “Required” an all the Dropdown List for the Network Adapters are in the Request visible.

vCAC Version: 6.0.1

Any Idea how to do this?

[stvkpln]

If you don't want to use that custom property, don't have it be part of the blueprint (or the build profiles associated with that blueprint)... Creating a custom property in the property dictionary doesn't associate it with every blueprint.

[vMarkusK1985]

The custom property is part of the Business Group...

[stvkpln]

Ok, so in that case.. you have two options... You can either remove the property from the business group and apply it somewhere else (like in a build profile or a blueprint) so that it's something associated with the blueprint rather than the business group... or you can set a value on the property in the business group so it doesn't start as empty when the catalog item is selected.

[vMarkusK1985]

OK,

To set a predefined Value is a good Idea. Can I set this in the Build Profile to?

I tried it, but it doesn’t work...

[stvkpln]

Since you're setting the property at the business group, I'd fill in the value field for the custom property on the business group with whatever you want the default to be.. When you set a value on a custom property that has a drop-down control type, all that does is set a default value for the form.. It doesn't necessarily lock it in. If you want to lock the value in, then that property shouldn't be user prompted.... Some flexibility is implicitly lost when setting values at the business group because they follow that business group, not a particular blueprint / build profile. To this point, I've avoided (and in one instance, resisted) the urge to set values on the business groups for that very reason.