7
Currently, when we use the out of box azure service bus integration, the message properties include:
Organization URI
Calling user ID
Initiating user ID
Entity logical name
Request name
It would be extremely helpful to also include the entity Id in the message properties. This is extremely helpful for troubleshooting, as we won't have to look at the body of the message to determine entity id.
Also, if the sessionid had the entityid set (maybe this is a configuration checkbox in endpoint setup) it would allow us to use sessions if we wanted to.
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/write-listener-application-azure-solution#filter-messages
Organization URI
Calling user ID
Initiating user ID
Entity logical name
Request name
It would be extremely helpful to also include the entity Id in the message properties. This is extremely helpful for troubleshooting, as we won't have to look at the body of the message to determine entity id.
Also, if the sessionid had the entityid set (maybe this is a configuration checkbox in endpoint setup) it would allow us to use sessions if we wanted to.
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/write-listener-application-azure-solution#filter-messages
STATUS DETAILS
Needs Votes