AX7 how to catch XPP exception object (Microsoft.Dynamics.Ax.Xpp.ErrorException)

(1) Share

Report

Posted on by Community Member

Hello community,

I am looking to catch the X++ exception object similar to C# "Catch (System.Exception _e)".

When debugging the catch block I can see a new object has been added to the Locals pane.

Name: $exception

toString:{"<Error text goes here>"}

Type: Microsoft.Dynamics.Ax.Xpp.ErrorException

Is this an object that I can access with X++ in the catch block?

I am very interested in retrieving the stack trace that lead to the exception being thrown.

Best Regards,

Cody P

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Mea_ 60,286 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi Cody,

You can try next code:

try { throw Exception::Error; } catch { info(con2Str(xSession::xppCallStack())); }

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

xppCallStack() does not solve the problem.

A typical use case would be to call more complex logic inside the try block (e.g SalesFormLetter.update()).

xppCallStack will show me that SalesFormLetter.update() was the last line called in the try block before the exception, but does not know about the calls inside SalesFormLetter.update().

$exception has call that threw the exception, I just need to know if/how to access it.

Best Regards,

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Cody,

We have the exact same problem at an integration project. Did you find any answer on this?

Regards,

Yakup

Was this reply helpful? Yes No
Verified answer

Martin Dráb 239,938 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!

X++ doesn't use objects for exceptions, so it obviously can't have any syntax for working with them. If you throw an error, the only data you can provide is the value of the Exception enum, i.e. a number. Throw error("Error message") is the same as calling throw Exception::Error and putting "Error message" to infolog.

What you see it the consequence of the fact that CIL has a completely different approach to exceptions than X++ - it uses objects, not the Exception enum, therefore it must create an exception object under the hood.

Therefore you can't get it from X++; you would have to find some hack how to extract the information from CLR.

Was this reply helpful? Yes No