Sorry guys, I'm a little late to the party but for anyone that stumbles across this question at a later date, I've found the easiest way to do this in a stored procedure is to:. Create a new query with any procedure parameters declared and initialised at the top. Paste in the body of your procedure.
Nov 24, 2016 Debugging in AX 7 using VS2015 (When symbols are not loaded). Here is the tip/ resolution for debugging in VS 2015 when you faced issue with symbols are not loaded. Done Axapta Reports in Ax 3.0, Ax 2009 & SSRS reports in Ax 2012. Customizations on D365 Operations (AX7). Experience on Integration, code deployment.
Add a good old fashioned select query immediately after your table variable is initialised with data. If 3. Is not the last statement in the procedure, set a breakpoint on the same line, start debugging and continue straight to your breakpoint. Profit!!messi19's answer should be the accepted one IMHO, since it is simpler than mine and does the job most of the time, but if you're like me and have a table variable inside a loop that you want to inspect, this does the job nicely without too much effort or external SSMS plugins.
My apologies for the late response.Lobbi says: 'As i understand this regarding step B.2, only one user can debug?' For clarity, I would like to note that any number of users can debug their X code outside of batch jobs.
It is also possible to modify code that typically runs in batch mode and instead call it directly from a job although state could be different when code is executing on the client. In some rare cases, debugging a batch job on the server is the only way to reproduce errors with the proper state (application data, configuration settings, etc) and in those rare situations, then only one account can be used to debug the batch code running on the server. Hi,I was in assumption that we can't debug the code running under batch process. As per my experience, i worked on so many batch job related tasks, and i solved the issues by trail and error.Anyways, after going through the above explanation, I came to conclusion that we can debug the batch job as well provided the AOS account logon credentials to be given as the one who is logging into the AX.I tried the above scenario in my local machine. But in the production environment, if two or more developers are working to solve the batch job issues, is it possible for them to debug the batch jobs?Right now in my machine, i am the only person who logs into the AX and i can play changing the AOS account to my credentials. Do we need to change each and every time as per the user who is going to debug the batch job?.
I am trying to run an import job in the background. When I run the job, there is a 'Batch processing' checkbox. If enable this option and accept the job, it is added to the user batch list with a status of 'Waiting', but is never processed.The following is from the documentation: 'First of all, a job can not start before an Axapta is started as a batch executer (processing).' What does this mean? Does the AOS have to be started with certain settings, or does a client have to be started with some or other settings? Can more than one job be run at once (rather than waiting for each job to finish)?Thanks. Rama,Yes, you will need to change credentials each time or use a specific account for running the AOS under and share the credentials accordingly.Praveen,Batches are only executed every minute (by default) so you may need to simply refresh the form after 5 minutes and then you will get a new status.
If not, then there might be a batch setting that is incorrect but we would need more details With Dynamics AX 2009 and Dynamics AX 2012, you simply need to start up the AOS in order for batch processing to be run in the background.