A series of user guides to Microsoft Dynamics NAV. These free resources detail specific issues and questions brought up by our clients. If you have any questions on Microsoft Dynamics NAV you’d like addressed by NAVGuides let us know at enquiries@metaphorix.co.uk

How to copy company in NAV

How to copy company in NAV

This guide will show you how to copy a company in Dynamics NAV. This is useful if you have some testing that you need to do using your current data.

Note: This function is only available in versions 2013-R2, 2015, 2016 & 2017.

1. Search for “Companies” in the search box and click on the link.

2. Select your company and then click on the “Copy” button in the ribbon.

3. Give the company a new name and then click “OK”.

4. This may take a while. Once done, your new company will appear on the page and contain the same data as the company you copied it from.

5. Once you are finished with the company and no longer need it, the company can easily be deleted. Please note that you must not be in the company you intend to delete or you will get the below message.

To delete the company, simply click on the company that you intend to delete and then click on “Delete” in the ribbon.

6. It will ask you if you are sure. Click “Yes”.

7. It will ask you a final time if you are sure. Click “Yes”.

8. This may take a while. Once completed you will see that the company has now been removed.

Configuring the Web Client for tablets (NAV 2013+)

In a NAV Know How webinar from earlier in the year, we covered configuring the Web Client for tablets in versions 2013 and above. Some of the specific areas we covered include:


1) Preview Client

2)SQL database- CRONUS-SQL

3) NAV Server – meta-dtp-11x

4) IIS (Web Server) Server – metapdtp-11x

5) Server Certificate/Self Signed Certificate

6) Internal/External

7) Web Client – Aspect Ratios – Phone.aspx/tablet.aspx

8) Android/IOD/Windows App


1) New NAV Service/connect to DB

2) New NAV web Server Instance – NAV 2015 Administration Shell (ADMIN)

3) Server- meta-dp-11x/server Instance – NAVKnowhow (NAV) Webserverinstance- NAV KNow How

4) Check IIS to see new NAV WEb Client instance

5) Make sure a certificate has been assigned to the web client

6) Change the web Config to point to the NAVknowHow Nav Service

7) Check the Web Client

8) Check the “Universal App”



Find out more

For more information on Dynamics NAV, or how Metaphorix configures the solution for specific industry requirements. Get in touch below, we’d be happy to have a chat!

Your Name (required)

Your Email (required)


7 Things to check when your Dynamics NAV service isn’t running

7 Things to check when your Dynamics NAV service isn’t running

When a solution stops working it can be frustrating. However in the case of Dynamics NAV there is often a simple solution that can be implemented. This guide will take you through seven steps to diagnose what is causing your service to stop or to not start at all.

1. Is it running on an account with enough privileges?

The default account “Network Service” usual isn’t enough when you need to run a service that has to contact multiple machines. Make sure that you have a dedicated service account running the service that has administrator privileges across all the machine that it needs to contact. Preferably a domain admin account.


2. Is the account running the service locked out?

Have a look at the active directory on your domain controller to see if this account has been locked out.


3. Has the account running the service got permissions within NAV?

For the account to run the service, it needs to have permissions within the database itself. It is generally a good idea to make the account a super user to rule out this being a limitation.

4. Is the SQL service running on your SQL server?

Dial onto your SQL server and open up services. If the SQL service is not running, then your NAV service cannot talk to the database and make a connection. Start the service if it has stopped.

5. Are your ports being taken up by another service?

Check your ports! If another service is using the same ports, then your NAV service will not start up!
On your NAV server, run command prompt as administrator and then type in the command “netstat –a”. This will list all the ports that are being used by your server. If any of these ports match ports that your service is set to use, then you need to change them.

6. Is your service set to automatic?

Open services on your NAV server and look for your NAV service. On the Startup Type column, you ideally want it set to Automatic or Automatic (Delayed Start). This will ensure that your service starts up automatically whenever your NAV server is rebooted.

7. Basic checks on the service settings.

Probably the last thing to check if everything else hasn’t got your service started back up yet. Does the database have an instance on the SQL server? Is the Database Name and Database Server Correct?

If you’d  like more information on Metaphorix’s industry specific versions of Dynamics NAV, including Construction, Manufacturing, Distribution and Service solutions get in touch!

For more great advice, hints and tips on Microsoft Dynamics NAV sign up for our newsletter below!

Your Name (required)

Your Email (required)


NAV Know How Stock Take Best Practices

NAV Know How Webinar Now available online

In this Metaphorix Dynamics NAV Guide we cover some best practices to observe when doing Stock Take within the ERP Solution. This free webinar was divided into two seperate versions of NAV, 2013 and 2016.

Some of things we cover include:

Fields to filter by
physical Inventory counting period code

The Physical Inventory Journal- Part 1
Create Journal lines- Counting period items only
Printer Report without Calculated Quantities
Update Quantities and Post Journal

The Physical Inventory Journal – part 2
Create Journal Lines- Component Items Only
Printer Report with Calculated Quantities
Update Quantities and Post Journal

NAV 2016

NAV 2013

How to change your security model in NAV

How to change your security model in NAV

Please note: Before you apply this change, make sure that all users are out of the database.

First, you must make sure that your database is set to single user mode. To set a database to single user mode, it is best to change this in SQL Server management studio.

1. Right click your database and select properties.


2. Select Options and then scroll down to the restrict access row. Change it from Multi User to Single User and then click okay.


3. Click “Yes” on this message.


4. Then open the database in the classic client and click File>>Database>>Alter.


5. Go to the Advanced tab and this will allow you to change the model to Standard. Then click OK.


Once this has been changed, you can switch the database back to Multi User mode in SQL Management studio by using steps 1 – 3 again.

How to Backup and Restore using an Azure SQL Database

How to Backup and Restore using an Azure SQL Database

This guide will show you how to take a backup from an Azure SQL database and restore it to your local SQL server.


1. First, connect to your SQL Azure database using SQL Management studio using your SQL Azure credentials.


2. Once connected, right click the desired database, then Tasks >> Export Data-tier Application…


3. This will then open an introduction page. Click “Next”.


4. Select a backup location by clicking on “Browse” and then click “Next”.


5. Here you can verify what you’ve setup and then click on “Finish”.


6. Exporting in progress. Once this is done, just click on “Close”.



7. Once this is complete, go into your local SQL service, right click Database >> Import Data-tier Application…


8. You will see another Introduction page. Click “Next”.


9. Browse for your BACPAC file that you made and then click on “Next”.


10. On this page, give your database a name and set where the data and logs files will be stored. Then click “Next”.


11. Here you can verify what you’ve setup and then click “Finish”.


12. Importing in progress. Once this is done, just click on “Close”.


Checking Setup and Troubleshooting the Job Queue

1. There are a number of things that may prevent your Job Queue from running correctly. The first thing to determine is “Has my Job Queue stopped or has the Job Queue Entry stopped?”.

A Job Queue is a tool in NAV that allows you to schedule a variety of processes and tasks to run periodically. These can included Reports and Codeunits to carry out certain functions or to provide users with data at regular intervals.

How do I check if my Job Queue is running?

Navigate to the Job Queue in NAV (Departments >> Administration >> Application Setup >> Job Queue >> Job Queues).

• Last Heartbeat: This field will show you the last time that the Job Queue ran and is updated automatically approximately every 10 seconds. Therefore, if the date and time in this field is not up-to-date you know that the issue is that the job queue isn’t running.

• Similarly, the Started tick box (next to the Last Heartbeat field) will indicate if the Job Queue has been started.

job queue 1

If you can see that either the Last Heartbeat is out of date or the Started flag is not ticked then you can start the Job Queue by selecting Start Job Queue in the Ribbon. This will tick the Started flag, populate the Last Heartbeat and also populate the User ID of the person who started the Job Queue.

job queue 2

N.B. Occasionally, selecting Start will not have an effect. This can simply mean that the system expects to your select to Stop Job Queue from the Ribbon and then select Start Job Queue.

2. If the Job Queue is running; is there a specific Error status in the Job Queue Log Entries?

In the example below I have navigated to the Job Queue Log Entries (Departments >> Administration >> Application Setup >> Job Queue >> Job Queue Log Entries). You can filter by the Status “Error” and then order the Start Date/Time to show the most recent entries to have an error. This will give you a good idea as to which process is causing an issue.

I have highlighted a line and selected Show Error Message to see the full error message for this process.

job queue 3

This is a fairly common error when trying to print a report from a Job Queue and simply, as the error suggests, the printer is not available to print to from the Service Tier. These errors can give you a good indication of what is preventing a Job Queue Entry from processing.

3. There isn’t a Job Queue Log Entry for the process.

If there is not Job Queue Log Entry for a process and the Job Queue is running then this suggests that there is an issue with the Status of the Job Queue Entry (Departments >> Administration >> Application Setup >> Job Queue >> Job Queue Entries).

job queue 3

In this example the Status is On Hold and so the Job Queue Entry won’t run. Similarly, if there has been an error in the Job Queue Log Entries (mentioned previously) that has now been resolved, the status of the entry may be Error. In both instances it is necessary to select Set Status to Ready from the Ribbon.
Dependent on the set up of the Entry, this may not cause the process to start straight away. Therefore you may not see a Job Queue Log Entry then you set the status to ready as the Entry isn’t running yet.

To gain confirmation that the process is now running you can select to Edit the Job Queue Entry and update the Earliest Start Date/Time. If you enter todays’ date and a time that is earlier than the current time, then select Set Status to Ready, the system will start running the entry immediately and you will see a Job Queue Log Entry created.

job queue 4

4. If your Job Queue is running and the Job Queue Entry is set to Status Ready with an Earliest Start Date/Time that has already passed but the Process has not run and no Job Queue Log Entry has been created then it is possible that the Job Queue Entry is not set up with a Job Queue Category Code.

Job Queue Category Codes can be used if multiple Job Queues are running. The Category Code helps to determine what the Job Queue is being used for and will filter the Job Queue Entries that the Job Queue Runs.

As such, if I select DELEGATE as the category for the Job Queue below and I would like this to run a specific Entry, I must ensure that the Entry also has this Job Queue Category set up.

job queue 5

job queue 6

5. The setup of the Job Queue may not be correct for your business needs.

If, as in the example above, the “Start Automatically From NAS” option is NOT selected in the Job Queue setup; then the reason for the Job Queue not running can often be that the Service running the NAS has been restarted (or possibly the server has been restarted) and the Job Queue is simply not setup to restart automatically.

There can be good reasons to have the Job Queue not start automatically when the NAS is restarted. For example; Flexibility. When running the Job Queue automatically, the only way to restart the job queue is by restarting the NAS (please see warning below when selecting Start from the Ribbon on the Job Queue set to run from the NAS).

job queue 7

If you are testing a Job Queue and want to be able to restart it regularly from NAV or have users in the system that are also connected to the Service that runs the NAS, then this set up option may not be appropriate.

However, if your business regularly restarts the server operating as the Service Tier for NAV or would like the act of stopping and starting the Job Queue to be restricted to only users with access to the service tier, then this option can be useful.

9. The NAS has not been set up correctly.

When setting us a NAS to run the Job Queue, there are a few options that must be used in order for this to work.

• The Service running the NAS will be running under a specific User ID. This user must be set up in NAV and should have administrative/super user rights. In this example there is a Service account to run the NAS. This has been set up in NAV as a Super user.

job queue 9
• You can check the user running the Service either from the Job Queues (shown above) or from the Service tier by opening the Dynamics NAV 2016 Administration console, selecting the service on the left-hand side and selecting “Login Account” on the right.


job queue 10


Within the Setup of the service you will need to ensure that, within the NAS Services fasttab, the Startup Argument is set to JOBQUEUE and the Startup Codeunit is set to 450.


job queue 11

These settings are vital to ensuring that the NAS is able to access the NAV codeunit responsible for running the Job Queue from the NAS.

7. All of the setup previously mentioned is correct and as you would like it. However, the Job Queue still appears to not run/the service is running but the NAS is not running the Job Queue.

This can be because there is a Password Policy applied in the Active Directory that is preventing the Service Account running the service from working or the Service Account has been locked.

It is important to remember that, if you require passwords to be changed regularly and this applies to the user running a service then you will need to ensure that the login credentials are updated when a password is changed. This can be done from the Service Tier in Services.

job queue 12

Similarly to the password needing changed, a Service can be set up to make multiple attempts at restarting automatically. If a Service Account password has expired (and not updated in the service setup) then the multiple attempts to restart can cause the account to become locked in the Active Directory.

This can be tested simply by trying to log into an account or a server as the Service Account, if you don’t have access to the Active Directory to check this.

Setting Up Permissions – NAV 2016

Setting up Permissions within NAV is a process of trial and error. Below are a few steps that should demonstrate how’s best to begin building Permission Sets for users who carry out specific roles within your organisation.

The first step is to have two users logged into NAV. The first should have a Super Permission Set shown below.

permissions 1

The second user should be an end user who will be carrying out the task of their role on a day-to-day basis, in this example we will be using a Sales Order Processor. This user should begin with the most basic Permission Setups, ADCS ALL, ADCS SETUP and BASIC. This gives the user enough permission to log into NAV.

permissions 2

N.B. It is or course possible to have both functions performed by the same person logged in with two separate user accounts (Shift + Right-Click on the NAV Desktop Icon and select Run as Different User to log in as another User).

Once the end user is setup and can open the NAV client, it is then possible to being building their Permissions.

This can be done in a couple of ways. Either you can apply Permissions to the User based on what Permission Sets appear application. i.e. we would expect our Sales Order Processor to require access to Read Customer information and Customer Entries. We should therefore click on the drop-down in the Permission Set field and select the Role ID that is applicable – in this case S&R-CUSTOMER.

permissions 3

It is possible to build the user permissions out of standard NAV Permission Sets, however, many users choose to construct specific Permission Sets for their Company.

You can construct a Permission Set by getting the end user to start trying to carry out their day-to-day functions, in the example below the Sales Order Processor has navigated to the Sales Orders list and received this error.

permissions 4

The error indicates that the User needs to be able to Read the TableData from the Cust. Ledger Entry table.

You can therefore start to build a Permission Set for your Sales Order Processors from this point. This is done by the SUPER user navigating to Permission Sets and selecting New.

permissions 5

You will then be prompted to enter a name for the Permission Set, here is it CRONUS-SOP and enter a Description of the Permission Set. To start building the set, highlight the line you’re going to add permissions to and select Permissions from the ribbon.

permissions 6

This will open the screen below where you can select the object that you would like to give permission to.
There are a number of fields to be aware of on this screen:
Object Type

– Table Data: this gives users access to read and write data in a table, though not access the table specifically.
– Table: this gives access to a specified table and may need to be used in conjunction with the Table Data.
– Report: allows a user access to run a certain report, this can be a document that needs to be printed or a process (i.e. creating a Pick utilises a report).

– CodeUnit: controls certain functionality within NAV and doesn’t relate to data.
– XMLport: users can import and export XML information via NAV through a number of pre-designed XML Ports.
– MenuSuite: gives access to menus in NAV such as the Navigation Pane.
– Page: this is where a user will see table information displayed in NAV.
– Query: query objects allows users to directly query data within the database.
– System: these are standard system functions inherent to NAV.

Each NAV object has a specific ID No. and this should be populated in the Object ID field to which you’d like to provide permission.
Read, Insert, Modify, Delete and Execute Permissions are all actions that a user may be able to carry out on an object. For example a user can Read and Insert data into a table.

These settings can be a way of restricting user access to certain objects. In our example the user needs to be able to Read the Cust. Ledger Entry Table Data, so the Read Permission field would show YES. We may, however, decide that they shouldn’t be able to Delete from this table and so we would leave the Delete Permission field blank.

For certain objects, such as Code Units and Tables, the option to Read and Insert is not relevant and so the only option NAV will give you is Execute Permission – similarly the Table Data Object Type doesn’t require the Option to Execute and so this won’t be available to add.

permissions 7

To Select the Object ID, if you don’t know the specific number, it is possible to select the drop-down shown below and click on Advanced.

permissions 8

This will give you the option to filter the objects based on the permission error message that you received previously.

permissions 9

Once you have added the Object to the Permission Set, you can then add the Permission Set to the user Role.

permissions 10

The user will need to log out of the system and back in to allow this change to take effect.

Our Sales Order Processor should then try to create an order of carry out the next step in their process. You can add permissions as and when errors occur.
If you continue in this way you can build a company specific Permission Set that can be applied to any user carrying out the same role.

Obviously this can be a time consuming process and so many people will choose to start out with a few standard roles and add anything to them that is not already available as a part of the standard Permission Set.

Nav 2016 CRM Connector Authentication Error

“The Dynamics Nav CRM user that is specificed in the crm connection setup does not exist”

crm connector error

If setting up the Nav 2016 CRM Connector and struggling with authentication error.

1. Make sure the user set up in “Microsoft Dynamics CRM Connection Setup” exists in CRM

2. Make sure account hasn’t locked out in AD if on-premise, check password

3. Make sure CRM certificate is installed on NST if required for authentication without credentials prompt

4. Make sure that the “Primary Email Address” for the user in CRM matches the “