I am a bit confused how to run the job queue. In the past with the schedular, you simply set up the information, when it was to be run and off it went. A session had to be lefy open...but a small price to pay!
There are a couple of specific issues that I have......
1. I write a record with status of ready to the job queue Entries table.
2. On the IT Administration jobs set up menu I make sure the job queue
active is set to yes.
3. Nothing happens at this stage....so I go to the job queue processes and
find the relevent session...there is only one....and i take functions
activate job queue session....still nothing happens....
4. I go to the object designer and run codeunit 448 Job queue dispatcher.
This runs the job, but I get an error message about there being no
parameters. Which I don't want to pass to the job anyway.
5. Now i can't get the jobq to stop! If I run the debugger CU448 is looping
round. If I try and de-activate the job from the job queue processes >
functions > Deativate... nothing happens. I have to close down the session
and restart Nav.
I know that I am missing something here....but can't work it out.
Your help is appreciated.
Tim
0
Comments
Can someone shed more light on how to properly setup the Job Queue in 5.0?
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
All Codeunits needs to have job queue entry on onrun as parameter. Even if you don't use it.
You can run a report which doesn't require a parameter.
You can add a new field to Job Queue called require parameter, and then modify the following CU "Job Queue Start Codeunit"
//old code
// "Object Type to Run"::Codeunit:
// CODEUNIT.RUN("Object ID to Run",Rec);
"Object Type to Run"::Codeunit:
if Rec."Require parameter" then
CODEUNIT.RUN("Object ID to Run",Rec)
else
CODEUNIT.RUN("Object ID to Run");
If you want to run the job scheduler from Nav client. You need to run CU
Job Queue Dispacher.
This will star the timer, and there is no way to stop it except exiting out of the company.
Also The job will only run once a day unless you add a value in
"No. of Minutes between Runs". If the mentioned field is zero it will run once and only one time for that day.
Also make sure "Earliest Start Date/Time" is before the currentdatetime.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n