If you have just started working with vRealize Automation, you will notice that you can apply Custom Properties to many elements. While this is great and add a lot of flexibility to the product and make it easier to customize the product to do things differently in the way you desire. It can get confusing which property will precede/over write the other one, if a duplicate property with a different value was assigned at a different element/level. In this post, I wanted to highlight the order of Precedenc for Custom Properties in vRA, so you can predict your results.

The full order of precedence for custom properties is that any property value specified in a source later in the list overrides values for the same property specified in sources earlier in the list. The order is shown in the following list:

Order of applying Custom Properties, later one over write earlier one:

1. Build Profile
2. Blueprint
3. Business Group
4. Compute resource
5. Reservation
6. Endpoint
7. Runtime

Note: Please note only Build Profile, Blueprint, and Business Group custom properties are assigned at the request time, while most other custom properties (Comput resources, reservation, & Endpoint) are assigned during provisioning, as they are not being assigned till the provisioning process has been started.… Read More