Steps to Follow:

  1. Use your Super permission-ed Administrator account to log on to Windows and NAV. (No need to worry about NAV Development Environment or NAV Dev. Licenses)
  2. Make sure there are no enabled Job Queues running or On-hold for Report ID 795. (Go to Job Queues in NAV and open Job Queue Entries to see that)
  3. Open NAV Administration Tool.
  4. Go to Start Menu and type NAV Administration then open the program. Click on the "Console Root" on left hand pane of the opened window.
  5. Click on "Microsoft Dynamics NAV" service root under that and see from the middle pane the services you are currently using to run NAV.
  6. Make sure which Service account is accessible without any restriction to run NAV Services smoothly, in my case both the Network Service and Local Administrator account have all privileges to run NAV Services. Thus you may not face any logon failures.
  7. This is optional but recommended since we need to take care about our live NAV System's safety and reliability always. It's better to create a new NAV Service just to run all your Job Queue related activities. To do so, right click on "Microsoft Dynamics NAV" service root and click "Add Instance"
  8. In the dialog box, enter your available parameters and click OK.
  9. Click on the Left pane's tree and expand it to see your newly created service and click on it.
  10. Select Edit button on bottom of the screen and Edit the highlighted "Services Default Time Zone" to "Server Time Zone" (Default will be "UTC"). This is fixing a major glitch which you may most possible not notice in the Job Queue. If your Server's Time Zone and the UTC Zone is different there's a possibility to miss the first next recurrence of your Job to run, sadly and you will get a bad mark tomorrow morning, by hearing "Where the automation setup went you did yesterday?" with a booooo sadly.
  11. Scroll-down the page until you find a section called "NAS Services" where you can edit all the necessary NAV Application Server related details and parameters. This helps you to trigger the Job Queue without worrying much about the NAV Service by re-implementing a sub service tier under the mainly created new Service (in our case, QueueServices). Expand the section and enter details as follow. Enter Startup Argument: JOBQUEUE, Startup Codeunit: 1, Startup Method: StartNAS (For older versions from 2017, "Startup Method" should be entered as "NASHandler" instead of "StartNAS")
    Click Save finally and wait for the message saying "You need to restart the service to take effect on changes" and click OK.
  12. Then Restart the Service. Don't worry. This is not the live Service so you can freely restart without loosing any NAV related connections. (Right click on the Service and Click Restart from the middle pane) Now close the NAV Administration tool since you're done with service configuration for the Job Queue.
  13. Next is the simplest thing. Go to the NAV Roletailored Client (RTC) and find Job Queue from Administration Module.
  14. Open Job Queue Entries page.
  15. On the Job Queue Entries page you can see all your Job Queues and this is where you are going to create your Job to run Item Cost Adjustment schedule. Click New on the ribbon.
  16. On the opened page enter your Job parameters to run. Based on this, Item Cost Adjustment will run at 11:00 PM on every day without a fuss. (Please refer the original author's link at the end for better clarification with images)
  17. That's all. Now in the Job Queue Entries page you can see your newly created Job Queue. Now the final step, set the Job Status to ready and wait for next day to this magic has run.

Additionally you can see the log of ran Jobs from opening the "Log Entries" page from actions ribbon of the particular Job.

That's all. Now you can sit back and be the champ of automation with NAV Job Queues!


Read better with the original author here....