"X++ debugging is not enabled for code running on Application Object Server" warning

this warning can be ignored. and continue to debugging.

query not updated.

Hi,

Have you ever work with query in the class? and after do some changes to the query in the class, when you run it, the query is not updated?

Well, its because of the sysLastValue. It keep your query saved. So whenever you change the query, it still be using the old one, unless you delete the saved query at the sysLastValue.

If you realized, after you changed the query, when you debugged it, it does not go into your initQuery() method, but once you deleted the saved query, it will go into the initQuery() again, to get the new query to run. now! you'll have your new, fresh updated query run.

To delete the sysLastValue is, go to the aot:

AOT > System Documentation > Tables > SysLastValue

right click at the SysLastValue, go to the table browser, find your element name, and delete everything that is listed there related to your element. make sure you deleted the right one.

wallah! now you good to go! :)

Enable Debug

You must enable debugging for each component as follows:

1. In the Development Workspace, on the Tools menu, click Options > Development > Debug,
and then select When Breakpoint in the Debug mode list.

2. From the AOS, open the Microsoft Dynamics AX Server Configuration Utility under Start
> Administrative Tools > Microsoft Dynamics AX 2012 Server Configuration. Create a new
configuration, if necessary, and then select the check box Enable Breakpoints to debug X++
code running on this server.


3. For Enterprise Portal code that uses the BCPROXY context to run interpreted X++ code, in the
Microsoft Dynamics AX Server Configuration Utility, create a new configuration, if necessary, and select the check box Enable Global Breakpoints.