Opening up AX Code from Infolog Warning / Error (AX 2012 R3)

(0) Share

Report

Posted on by Community Member

I am trying to review an error in AX 2012 R3. In older version I could double click the error and it would open the code behind the error as long as I had the permission to do that.

Is that functionality available in 2012 R3? I have already created a configuration that has breakpoints capability enabled on it using the server config utility and made it active in the AOS server where I am debugging.

I looked at Label Editor but its not very helpful, since the error is a very common error message used by several classes.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

André Arnaud de Cal... 301,030 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

The feature is still available. If the error is coming from AX logic you can select the error info line itself. Then a button becomes active if you have system administrator role. This will not work for kernel code and places where a menu item is linked for an infolog message to support e.g. opening the parameters form.

This is not related to the debugger or the label editor itself.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Andre' , I fixed the error so I am not getting it now but will look out for the next time.

Is there a way I can do a code Trace while I am going through a process to capture all that objects involved in that process example classes, forms, tables, etc.

What is the best way to do that?

Was this reply helpful? Yes No
Suggested answer

Jonathan Halland 11,310 on at

Like (1)

Report

Hi

An additional note. If the code, for some reason is operating in CIL you will also not be able to drillthrough to your code. So for debugging purposes you can disable the "Run business logic in CIL' option to find where its breaking out.

www.exploreax.com/.../4-drill-through-to-code-from-info-log

Was this reply helpful? Yes No
André Arnaud de Cal... 301,030 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

You can use the code tracer to capture the coding used and also see which SQL statements are used. It is in fact a performance tool but you cann also use it for this purpose. Note that it will provide possibly a bit too much information. You have to learn working with this tool. Next page is a nice introduction: blogs.msdn.com/.../walk-through-major-features-of-microsoft-dynamics-ax-2012.aspx

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

You could temporarily put a breakpoint at the beginning of the method Classes\Info\add. When you reproduce the error, AX will begin to add a message to the infoLog and the breakpoint will be hit. You could then look at the stack trace to see where the method and line that trigger the error (or at least find where to put a breakpoint so that you can step through code that executes just before the error occurs).

Was this reply helpful? Yes No