Share
Report
5Hello,
I’m currently working with Dynamics 365 webhooks and Azure Functions. I’ve set up a webhook in Dynamics 365 that triggers an Azure Function via an HTTP trigger. The webhook sends a JSON representation of the RemoteExecutionContext object in the request body to the Azure Function.
According to every answer I found, the JSON structure of the request body object should directly map to the RemoteExecutionContext class in .NET. However, I’m noticing some discrepancies in the JSON structure I’m receiving in the Azure Function.
For example, the InputParameters property is coming in the format {/key/:/Target/,/value/:/Entity/EntityReference/}, whereas I was expecting it to be {/Target/: /Entity/EntityReference/}.
I’ve managed to work around this issue by creating a custom class that matches the incoming JSON structure and deserializing the JSON into this custom class. However, I’m curious as to why there’s a discrepancy between the JSON structure and the RemoteExecutionContext class in the first place.
Has anyone else encountered this issue? Any insights into why this might be happening would be greatly appreciated.
Thank you!
P.S. The error I was receiving when trying to parse or deserialize the body to the RemoteExecutionContext class was related to /OwningExtension.keyattributes/ key in the object which I assume means it successfully passed the lines before it which include the key/value part I mentioned above
All responses (
Answers (
