question

ZachF-5565 avatar image
0 Votes"
ZachF-5565 asked SatishBoddu-MSFT commented

Command Response, no "View Payload" button

I am using the code from the async-hub-scenarios, particularly the "receive_direct_method" file.

It states to do the following:

74981-image.png

This is what happens in the "response"

74982-image.png

If I serialize the payload, the response now shows - however - there is no "view payload" button and the response is overwritten in the command history when I send another command.

Here is code:

74983-image.png

Here is response with no "view payload" button.

74991-image.png

Why is the response originally nothing, then theres no view payload button - but the entire time, every response overwrites the previous response in the command history section. Thank you.

azure-iot-hubazure-iot-central
image.png (51.2 KiB)
image.png (77.7 KiB)
image.png (54.9 KiB)
image.png (79.0 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@ZachF-5565 Welcome to Microsoft Q&A Platform and thanks for your query.

Could you please post the Document link or the tutorial link to which you have referred to?

0 Votes 0 ·

1 Answer

rkiss avatar image
1 Vote"
rkiss answered SatishBoddu-MSFT commented

@ZachF-5565 Try to use the object schema for the command response.

75014-iotc2.png


For the second question about the missing responses in the Command history, yes, it looks like this is a bug.

btw. this is a duplicate question to SO.

Thanks
Roman



iotc2.png (193.3 KiB)
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks @rkiss & @ZachF-5565 I have reported this internally, will be updating you soon.

1 Vote 1 ·

Hi Satish! Let us know if there is an update on the bug report

0 Votes 0 ·

Hello all,

We are investigating this issue with our Engineering team, via offline email conversation. Please comment in the below section if you have the same issue and need help in this regard!

Workarounds & Suggestions are Welcome!

0 Votes 0 ·