Share
Report
574Hi,
We have an integration calling a D365 Finance & Operations OData action, for example:
Entity1/Microsoft.Dynamics.DataEntities.Action1
[SysODataActionAttribute('Action1', false)]
public static str Action1(
str _id1,
DataAreaId _dataAreaId)
We noticed that when D365 returns a response, the response contains the "ms-dyn-aid" header. We can use this value to find the corresponding Activity ID in LCS Environment Monitoring and trace the request on the D365 side.
However, our integration has a client-side timeout. If the client stops waiting before D365 finishes processing the request, it does not receive the response and therefore does not receive the "ms-dyn-aid", even though the request may still be processing in D365.
In this scenario, we would like to generate our own unique ID for each request/attempt and send it with the OData request. Is there a supported way to have this ID captured in D365 telemetry so that we can search for it in LCS Environment Monitoring and identify the corresponding D365 Activity ID?
I previously tested sending a custom request identifier with the request, but I was unable to find it in LCS Environment Monitoring.
Additionally, in LCS Environment Monitoring, the RequestUrl shows Entity1 and Action1, but it does not show the method parameter values/request body, so we cannot identify which specific entity record the request relates to. Is there a supported way in LCS Environment Monitoring to identify the parameter values or specific entity record associated with an OData action request?
All responses (
Answers (
