Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRA system context parameters starting with "__asd_" are not passed to vRO action when called in custom request form (55832)

Last Updated: 6/6/2018Categories: TroubleshootingTotal Views: 6142Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When a blueprint with custom form is requested, you see these errors:

Some data cannot be retrieved. If the problem persists, contact your system administrator.;
[1][vSphere__vCenter__Machine_1~CustomNetwork.valueList][com.vmware.vra.networks/getApplicableNetworks] Error occurred executing action. Error: [Unable to start action 'com.vmware.vra.networks/getApplicableNetworks'. Reason 'Action 'getApplicableNetworks' in module 'com.vmware.vra.networks' failed : Supplied tenant 'null' is different from the token's tenant 'qe' (unnamed script#7)'.]

[1][macOS_10.13.3~ReservationPolicyID.valueList][com.vmware.vra.reservations/getApplicableReservationPolicies] Error occurred executing action. Error: [Unable to start action 'com.vmware.vra.reservations/getApplicableReservationPolicies'. Reason 'Action 'getApplicableReservationPolicies' in module 'com.vmware.vra.reservations' failed : Supplied tenant 'null' is different from the token's tenant 'applebuild' (unnamed script#9)'.]

Cause

This issue occurs because the vRA system context parameters starting with "__asd_" are not passed to vRO action when it is called from a custom request form and null value is returned when System.getContext().getParameter("__asd_tenantRef"); function is used in vRO action scripting.

Resolution

To resolve this issue, modify the vRO action that uses system context parameters so that needed information is passed as actual action parameters instead of retrieving them from the system context. Then when choosing the action in forms designer, it is possible to bind action parameters to request info parameters.

This is step by step example for com.vmware.vra.networks/getApplicableNetworks vRO action:

Duplicate the getApplicableNetworks vRO action using vRO client.

Replace all scripting variables that are retrieved from action's system context with explicit action parameter declaration. For instance, replace the following line:

var blueprint = System.getContext().getParameter("__asd_tenantRef"); with creation of action parameter with name "tenantRef".

Navigate to the custom forms designer (Blueprints > Custom Form > Edit).

On the applicableNetworks dropdown field, select the customized action as Value Options external source. Set parameters bindings as follows:

blueprint = <enter the blueprintId as a constant>
component = <enter the component as a constant, e.g: vSphere__vCenter__Machine_1>
tenant = <bind to Tenant reference>
user= <bind to Requested For>
subtenantId = < bind to Subtenant reference>

Save the custom request form.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.4.x

Take Our Survey

Support Assistant