You add a custom property to retrieve network names from the vRealize Automation database when you want users to select the network in the request form. The network selector custom property uses a vRealize Orchestrator action to retrieve the values.


Plan for the following limitations when you use the network selector custom property.

  • The name of the custom property must be VirtualMachine.network0.Name. This name is required. You cannot create multiple property definitions for the network selector.

  • The action retrieves all the network names for the requesting user without validating that it applies to the target vCenter Server instance. A service catalog user might select a network that is not applicable to the selected target. If the wrong network is selected, the catalog request fails.

  • The action retrieves network names for the requesting user only. If you submit a request on behalf of other users, the networks are for you. For example, Network A and Network C are associated with Business Group 1, so the BG 1 users see only Network A and C, not B.


If you use an external vRealize Orchestrator server, verity that it is set up correctly. See Configure an External vRealize Orchestrator Server.

Custom Property Configuration Values

You use these options to create the custom property. For the general steps, see Create a vRealize Orchestrator Action Custom Property Definition.

Table 1. Network Custom Property Configuration Values




You must use VirtualMachine.network0.Name.

Data type


Display as




Action folder


Script action


This script action is an example script. You can create specific actions for your environment.

Input parameters

No required parameters.

Blueprint Configuration

Add the custom property on the blueprint Network tab. See Add a Custom Property as a Network Custom Property.