1,719
Hi guys,
I've been investigating if is it possible to access the CallContext information that you provide from external applications that call the AX services, during the service operation execution in X++. It would be usefull to catch the MessageId guid from inside X++ on each execution of the service for advanced logging and then link with this messageId to the Exceptions and History AIF standard forms.
Any help on this subject will be welcome!
Thanks!
*This post is locked for comments
you can use CallContext.MessageId
for further detail:
I know that AX logs message ID to history (System administration > Periodic > Services and Application Integration Framework > History). It seems to be handled by AifMessageManager.createInternal(). I also sometimes used messageId() in debugging.
Try to configure logging and review history. If you see message IDs there, it obviously gets into AX and you can work with it. You're probably just doing it in a wrong moment.
Thanks Martin,
I found this method on the documentation (MSDN) but I never found a way to use it from the standard code. If you call this method from the service processor classes, it always returns an empty guid (00-00-00...).
If you have any example or experience with this let me know so we can do some testing ;)
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
