I have some resource actions defined that interact with vRO/External REST APIs. It seems after upgrading to 7.3 I'm not able to select the VM object as a 'Defined Field Value' to the external call? The object shows and states 'No Sub fields'. Pre-existing Resource Actions work just fine, but if I go to edit them I see the same behaviour.
Can anyone shed light on this? Image attached.
Oddly I still see this issue after patching/ensuring the system is good after upgrade. This wasn't the case prior to upgrade 😕
This is my input on the Action -
Add the action, go to select field data -
And no vm object?
As mentioned, the pre-existing resource actions are running ok, but display the same if I try to reassign the values. If I hack the yaml and import the resource action, it runs ok, but does the same if I try to edit the values. When using the vRA interface to create a new workflow, it's not possible.
This issue has been fixed in 7.4, but for 7.3 the only workaround is to modify the action in the vRO. Here are the steps how to do this:
Login to vRO client and make a copy of the “Test passing of VC:VirtualMachine” – workflow.
Go to Actions tab and create a new action, where:
Log in to vRA and select Design -> Resource Actions -> create a new action you want to use. Expand the workflows and select the copy if the initial workflow (the one you’ve created in the previous step).
In the Form tab drag and drop a text field. Select the field and on the right hand side panel select the Constraints tab.
From the Value drop down menu select External -> Edit External value and then select the newly created action:
Select Value for the generated property of type Field.
Select Define Filed Values and expand objVCVirtualMachine , then select id. Click Apply
I hope this helps!