Finance | Project Operations, Human Resources, ...

xSession::xppCallStack() is not containing the root object details from where the error is triggered

(0) Share

Report

Posted on by Community Member

In our system we have customized a framework which captures the errors and warnings infolog details of the current user session into a log.

This framework workds fine for other cases, but in the above case there isn't any information about from which form this error is getting triggered and it is not recorded in the callstack too.

Here is how we are capturong the callstack into the table field.

xxxGlobalInfologsErrors.ObjectType = con2Str(xSession::xppCallStack());

Do you guys have any idea to capture the root object details from where the error is getting triggered.

I have the same question (0)

All responses (9)

Answers (0)

nmaenpaa 101,162 Moderator on at

Like (0)

Report

Hi 8tejaskumar,

unfortunately your screenshot is so small that I can't see any details. So it's not clear what you mean by "the above case".

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I guess, now you will be able to see it

Was this reply helpful? Yes No
nmaenpaa 101,162 Moderator on at

Like (0)

Report

Thanks. Basically you get the "root object details" since it's a FormRun object. All forms are FormRun objects.

But you would like to somehow capture the name of the form.

Could you share more details about your code that captures these exceptions? How is it triggered?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

we have added below piece of code in info class's add method

select firstOnly sysClientSession where sysClientSession.Status == 1;

if(sysClientSession)

{

if(_exception == Exception::Error || _exception == Exception::Warning)

{

customclass::captureInfolog(_exception, _txt, _helpUrl);

}

}

in the captureinflog method we are inserting the values into the log table like below

xxxGlobalInfologsErrors.ObjectType = con2Str(xSession::xppCallStack());

Was this reply helpful? Yes No
nmaenpaa 101,162 Moderator on at

Like (0)

Report

Thanks for the details.

Could you try one thing. If you throw exception from a form via x++, do you then see the form name in the call stack?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

yes, we were able to capture the form name in call stack for other error cases...Below is one such example.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,162 Moderator on at

Like (0)

Report

Ok,

I guess that when the exception happens in the initialization of the form, then you can't get the form name via the call stack. And I'm not aware how else you could get it.

Was this reply helpful? Yes No
WillWU 22,363 on at

Like (0)

Report

Hi Tejas Kumar,

Agree with Nikolaos, you may not get the form name from the call stack.

community.dynamics.com/.../get-ms-dynamics-ax-call-stack-in-x-code

Was this reply helpful? Yes No
Martin Dráb 237,990 Most Valuable Professional on at

Like (0)

Report

Whether you see the form in the call stacks depends on whether it was the form who raised the exception.

In your second example, an exception is thrown by the form (a method overriden in the form).

In the first example, the form doesn't throw anything. The form returns control to the kernel class (SysSetupFormRun) and it's this class who throws an exception. Therefore what you see is the correct stack trace.

Was this reply helpful? Yes No