Unable to validate custom properties when filtered on user identity in vRealize Automation
search cancel

Unable to validate custom properties when filtered on user identity in vRealize Automation


Article ID: 341074


Updated On:


VMware Aria Suite


  • You have created a custom property in vRealize Automation that uses External values.
  • The vRealize Orchestrator action is constructed to provide different results depending upon the identity of the submitting user.

    For example, the value __asd_requestedby is used to determine the results for display in a dropdown.
  • When you submit the request, you see the error:

    Note: Where corp.myproperty is the name of custom property.

    The data specified within the request is invalid. The value for the 'corp.myproperty' field should be among the permitted values.


VMware vRealize Automation 7.4.x
VMware vRealize Automation 7.1.x
VMware vRealize Automation 6.2
VMware vRealize Automation 7.0.x
VMware vRealize Automation 7.2.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation Desktop 6.2
VMware vRealize Automation Desktop 6.2.x
VMware vRealize Automation 7.3.x
VMware vRealize Automation 6.x


When validating the property, the user context will be the solution user for the vRA appliance rather than the context of the submitting user. Thus, when the customer action is considering user context, the values displayed in the request form can vary from the values returned during validation, which causes the failure.


This issue is resolved in VMware vRealize Automation 7.4, available at VMware Downloads.
To workaround this issue, if the property filtering cannot be altered, vRealize Orchestrator action should return all expected values when the solution user has encountered.

Note: The name of the solution user is unique for every installation, but will start with word cafe.

For example: cafe-nwrsei32pQ. You can confirm the name in the following file on the vRealize Automation appliance: