Dropdown options causing SNOW request to not be sent to vRA

[rstoker13]

We have added 2 additional text dropdowns to our vRA blueprint. These dropdowns work perfectly when the catalog item is requested through vRA. SNOW will sync the dropdowns and allow selection, but submitting the request never makes it to vRA. I have tried each of the new dropdowns independently without success. If they are both removed, the request works correctly. If one or both are added back, it doesn't make it through again. I have attempted to review the SNOW logs, but unfortunately I do not have a great deal of familiarity with that product. I have included a few screencaps below. Please let me know if you need additional information.

Dialog from SNOW:

Dialog from vRA:

[kbhushan05]

Can you please share some log by using following steps.

1. Type 'integration' in filter navigation then select 'log' sub category.

2. Filter out logs by using 'Level' attribute for Error.

Please share vRA version as well.

[rstoker13]

It appears to be complaining about a "Bad Request". Please see the errors below:

Created	Level	Message	Source
2017-05-08 05:14:55	Error	Exception caught inside  VRASNRequestUtil.getRequestStatus: TypeError: Cannot read property "completionDetails" from null	vRealize-Automation
2017-05-08 04:34:54	Error	Exception caught inside  VRASNRequestUtil.getRequestStatus: TypeError: Cannot read property "completionDetails" from null	vRealize-Automation
2017-05-08 04:31:57	Error	REST call error found inside VRASNRequestUtil.requestVRACatalog: Method failed: (/catalog-service/api/consumer/entitledCatalogItems/3c2dfc12-cb6d-4e27-b9f4-9ac81bbce2fd/requests) with code: 400	vRealize-Automation
2017-05-08 04:30:27	Error	REST call error found inside VRASNImportCatalog.processVRACatalogGetCategory: Method failed: (/catalog-service/api/consumer/entitledCatalogItems/dbd91ace-99f6-43ad-bbe5-d19541711c2c) with code: 403 - Forbidden username/password combo	vRealize-Automation
2017-05-08 04:30:26	Error	REST call error found inside VRASNImportCatalog.processVRACatalogGetCategory: Method failed: (/catalog-service/api/consumer/entitledCatalogItems/169f22aa-79e4-46ca-afda-69633f521cc2) with code: 403 - Forbidden username/password combo	vRealize-Automation

Also, I have included screenshots of the new Property Definitions for reference:

[rstoker13]

Any ideas? I can submit an export of the properties using CloudClient if this would be beneficial.

[kbhushan05]

I can see Error message for property 'CompletionDetails' but this property is not visible on user interface. Can you please verify about property 'CompletionDetails' and share its details.

[rstoker13]

Thank you for your response. I have included a screenshot of our properties sorted alphabetically. We do not have a custom property named 'CompletionDetails'. Is this a native/hidden property?

[kbhushan05]

What is type of Blueprint? does your blueprint contains mix of static(like Agency application environment) and dynamic custom properties (call to vRO actions).

[rstoker13]

This is a standard composite blueprint with only a single machine component. All properties added to this blueprint are static. We have found that vRO backed properties do not display in the SNOW plugin, therefore we are not using them. If they did work, we would love to use them.

Below is a capture of the property group applied to the blueprint:

The merged properties:

[kbhushan05]

Thanks for all the logs and images.

We will reproduce this issue at our end and update your further.

[rstoker13]

Thank you for your assistance. Let me know if you want exports of these items via cloudclient.

[kbhushan05]

We tried same scenario at our end, It works for us. I need to discuss with team here, how can we help you in this scenario by some screen sharing or data exchange.

Please share your vRA version.

[rstoker13]

Sorry for the delayed response. It magically started working. No changes were made so I am uncertain what resolved the issue. We are using a developer instance for this testing. I guess it is possible that the hibernation of the instance caused something to be reset. Either way, it does not appear to be an issue anymore. We will soon be moving to a full instance and I hope to not see this issue then.